Patching issues for RHEL5 servers

Usage and Config Patch
1

Hi All,

We have done patching for RHEL5 Servers through IEM. Few of the servers having kernel patches.
The servers got rebooted after patching and we were
unable to access the servers. We got the below error while trying to
access the servers.

Pasted image754×151 74.8 KB

We found that there is a file created /etc/nologin and it
is not allowing any of the user to access the servers. We rebooted the
server one more time, go to the single user mode and deleted the file.

We rebooted the server and able to access the server. Kindly check and let us know is there any solution for this issue.

We need help to get rid of it as every time we are doing patching for RHEL 5 and then we are unable to login

2

If a shutdown is scheduled for the future, it will create the advisory file /etc/nologin which causes programs such as login not to allow new user logins.

As the warning says " is GOING down on ", it seems the system is in the middle of a shutdown.

May I know which fixlet is used to deploy this action 366562 ?

3

@ChuxinZhao Below are the list of fixlet which was applied to the Servers

Pasted image949×478 15.2 KB

In Post action we have mentioned that server should be restarted once the patches are deployed.Please see the below screen shot :thumbsdown:

Pasted image1004×169 5.19 KB

When ever we are doing patching for RHEL-5 Servers we are facing this problem.

4

Any input on above query

5

@Manish

I am not familiar with the logic used in the Post-Action for restart.

If you haven’t done so already, you may want open a PMR support case with the L2 Support team.

6

ok but Just now I saw the log file and I got the below finding.

Pasted image919×46 3.41 KB

And when I checked this fixlet “46” it was not included in the baseline which I took action.

7

Take a look at this solution:

https://bigfix.me/fixlet/details/3870

In the comments section is the author’s description of the fixlet:

This fixlet is used to fix the patching issue that we have had with RHEL 5 and reboots. When using the internal BigFix reboot in the action tabs it does not properly clear the /etc/nologin file. This fixlet will add a check to delete that file on boot.

Also, it looks like question as already answered on forum here

And, take a look at this APAR and consider upgrading your clients to BigFix version 9.2.7+

8

Thanks for your help.This is really helpful but I have few queries

  1. Fixlet “Fix /etc/nologin” I need to deploy once the patching for RHEL 5 is completed and reboot of server is done correct ?
  2. I have gone through the APAR link which you have mentioned and seems like this issue is fixed in 9.2.7 version of IEM Client. My question here is IEM Server which we are having it has console and Client of 9.2.6 version. Can we upgrade our Red Hat client to 9.2.7 version??
9
  1. Correct, after the patching for the RHEL 5 endpoint is complete. Use the fixlet to detect and re-mediate
  2. Yes, upgrade to BigFix client version 9.2.7 to prevent the issue from happening