Scribd
Upload
70 views2 pages

RedHat Linux Patching Procedure

The document outlines the manual patching process for Red Hat Linux production servers, detailing prechecks, patching procedures, and post-checks. Key steps include raising a change request, performing system backups, applying updates via YUM, and validating system functionality post-patching. It emphasizes communication with application and database teams throughout the process to ensure minimal disruption.

Uploaded by

bharathbabu2022
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
70 views2 pages

RedHat Linux Patching Procedure

The document outlines the manual patching process for Red Hat Linux production servers, detailing prechecks, patching procedures, and post-checks. Key steps include raising a change request, performing system backups, applying updates via YUM, and validating system functionality post-patching. It emphasizes communication with application and database teams throughout the process to ensure minimal disruption.

Uploaded by

bharathbabu2022
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Red Hat Linux Patching: Prechecks,

Patching, and Post-checks for


Production Servers

We are doing manual patching

 First of all we will raise a change request to get approval for patching and we will
take patch list and server list.
 we will send a notification mails to application and database team for to take
window time
 Suppressing the alerts before window time.
 We inform to app and dB team to stop their services.

1. Pre-Patching Checks
- Take a full system backup or snapshot.
- Verify current kernel and package versions using `uname -r` and `rpm -qa`.
- Ensure there is enough disk space using `df -h`.
- Check memory and CPU usage with `free -m` and `top`.
- Review running services and note their status using `systemctl list-units --type=service`.
- Confirm server is registered with Red Hat Subscription Manager (`subscription-manager
status`).
- Check YUM repository availability and configuration.
-- Disable automated jobs or cron jobs if necessary.

2. Patching Procedure
- Clean YUM cache: `yum clean all`
- Update package lists: `yum check-update`
- Apply updates: `yum update -y`
- For kernel updates, verify new kernel installed: `rpm -q kernel`
- Reboot the system if required: `reboot`
- For non-reboot patching (security only): `yum update --security -y`

3. Post-Patching Validation
- Verify system is up and accessible (ping, SSH).
- Check system uptime and kernel version: `uptime`, `uname -r`
- Validate all critical services are running: `systemctl status <service>`
- Review logs for errors: `/var/log/messages`, `journalctl -xe`
- Check application functionality and health checks.
- Confirm with stakeholders the environment is functioning properly.
- Document changes and update patch logs.

firstly we will check :

1.uptime

2.df -hT

3.yum clean metadata

yum clean all

4.uname -n to check hostnames

5.we will reboot the servers.

we will take post checks:

compare with prechecks :

1.uptime

2.df -ht | wc -l

3.cat /etc/fstab.

4. netstat -nr

5.ifconfig or ip -a

6. hostname

we will inform to db and app team to start their services and will hand over the servers.

You might also like