Skip to main content

Patching Notes .

If plymouth is NOT disabled during boot time, it may create issue working on the console, we need to disable it during patching window.


cat /proc/cmdline | grep -i plymouth :


to check if the plymouth is disabled or not. if no output then no if any output then YES. 

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Before patching :

history    

systemctl status scsm     :   check the status of scsm .

systemctl status cloud-init     :  check the status of cloud init .

df  -h  /   : check the available space in /  . 

cd  /home/homedir  :   Go to the directory . 

*********************************************************

lsblk >> lsblk ; df  -hT>> df-ht  ;  free  -tm >> swap  ;  cat /etc/fstab >> etcfstab     #compulsary    


cat  /etc/mail/sendmail.cf   |  grep   DS  |  grep    -iv  "#"   >>  sendmail
uptrack   -uname   -a  >> uname       #oracle linux
uname   -a        >>   uname                # redhat  and suse                                   
hostname  >> hostname 
timedatectl   >> timedatectl 


****************************************************


clear  :  clear the screen 


cat  df-ht  swap  etcfstab  lsblk  sendmail   uname  hostname  timedatectl  :   view the content of all the 8 files and copy it and paste it in notepad outside the server . 



>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

During the Patching : 

***********************

Oracle servers :  

uptrack-upgrade   -y  :  (Mar- Apr)
yum   update   --security    -y   : (sept- oct)

***********************

Redhat servers : 

yum   update   --security    -y   : (Mar- apr)
yum   update   --security    -y   : (sept- oct)


**********************

Suse Linux Servers : 

Apply  Bug  Fix update  -zypper  patch   -g  bugfix

Apply  Security  update  -zypper  patch   -g  security


***********************

Use this when server is not taking patches  : 


systemcti status salt-minion

systemctl restart salt-minion

systemctl status salt-minion

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>



After Patching : 



history

***********************************

Kdump enablement --on All Systems                          #optional

#yast2 kdump >>> Enable Kdump >> OK > Reboot


systemctl status kdump                ....(should be running)

cat /etc/sysconfig/kdump | grep KDUMP_IMMEDIATE_REBOOT (should be YES)


*********************************

systemctl status scsm

systemctl status cloud-init

cd /home/homedir
ll

*********************************

lsblk >> newlsblk  ;  df  -hT >> newdf-ht   ;  free-tm >> newswap   ;  cat /etc/fstab >> newetcfstab

cat  /etc/mail/sendmail.cf   |  grep   DS  |  grep    -iv  "#"   >>  newsendmail
uptrack   -uname   -a  >> newuname       #oracle linux
uname   -a        >>   newuname                # redhat  and suse                                   
hostname  >> newhostname 
timedatectl   >> newtimedatectl 

ll

clear


***************************************************


diff   df-ht   newdf-ht
or  
cat   df-ht  |  grep  -v  tmpfs   ;  cat   newdf-ht  | grep  -v  tmpfs             #compare the output




diff   swap    newswap

or 

cat  swap  |  grep  -i  swap  ;  cat   newswap  | grep   -i  swap          #compare the output



diff     sendmail  newsendmail

or

cat sendmail   ;  cat newsendmail                               #compare the output




diff  uname newuname                         

or

cat uname   ;  cat newuname                             #compare the output 





diff  timedatectl    newtimedatectl                      

or

cat timedatectl   ;  cat newtimedatectl                   #compare the output







diff  hostname   newhostname                         

or

cat hostname   ;  cat newhostname                 #optional 








diff etcfstab newetcfstab 

or

cat etcfstab  ;  cat newetcfstab                     # optional 




diff  lsblk newlsblk                         

or

cat lsblk   ;  cat newlsblk                    #optional


 

********************************************************


Enable sysstat at boot time, All systems                       #optional


systemctl enable sysstat.service

systemctl restart sysstat.service

systemctl status sysstat.service

********************************************************

cat /proc/cmdline | grep -i plymouth      # check if plymouth is disabled or not 


Comments

Post a Comment

Popular posts from this blog

Linux basic commands

 Linux basic commands: du  -sh  *  |  sort  -h  -r   |  head  -n  40  :    list out first 40 files in the directory that are taking more space in the directory.  cd : change directory Is-l listing the items in long listing format  pwd : print working directory Is-I format: type :no of links:owner : group:size :month :day :time :name cd/: go to/directory whoami: tells us by which username we are logged in. touch jerry: creates the file named jerry in present working directory. cp jerry lex: copy the content of jerry file and paste it to lex file. vi text1: creates the file text1 and open it in vi editor mkdir superman: creates the directory called superman mkdir abc def  : creates 2 folder in one command. touch filename wont work in /etc/ folder if logged in by normal account. man cp: shows manual for cp command. echo "india is my country"> file1 puts the text in file1. rm filename: remove the filename  mv lex luther renames the file from lex to luther  mv luther /h
Post a Comment
Read more

patching tasks

 Patching a Linux system is a critical task to ensure that the system remains secure, stable, and up-to-date with the latest features and fixes. Here’s a comprehensive guide to the tasks involved in Linux patching: 1. Pre-Patching Preparation Backup System : Ensure you have a full system backup, including critical data, configuration files, and applications. Test the backup to verify its integrity. Check Disk Space : Verify that you have enough disk space, particularly on /var , /tmp , and /boot partitions. Review Current Patch Level : Determine the current patch level and installed packages using package management tools like yum , apt , dpkg , or rpm . Check System Logs : Review system logs to identify any issues that might affect the patching process. Test in a Staging Environment : If possible, apply patches in a staging environment that mirrors production to identify potential issues. Notify Stakeholders : Inform stakeholders about the scheduled maintenance window and expected do
Post a Comment
Read more