So our data center decided to update our servers

[disrael]

Could updating mysqld cause the problem?

[scottwilkerson]

Could updating mysqld cause the problem?

It shouldn't but there would be no way for us to replicate what you are doing on a test environment because of the special setup you have there.

I have upgraded mysql through yum many times without problem, but wasn't doing so through some unknown tunnel...

[disrael]

Does nagios supposed to use automount? I see all of these on both server after patching:

Feb 19 11:23:01 usa0300lv886 automount[5564]: key "nagios" not found in map source(s).
Feb 19 11:25:01 usa0300lv886 automount[5564]: key "nagios" not found in map source(s).
Feb 19 11:27:01 usa0300lv886 automount[5564]: key "nagios" not found in map source(s).

[disrael]

This is what our datacenter stated:

Code: Select all

We  have to enable the ssh port forwarding  for EPN servers to connect them to the local repository server and then in yum.conf file we edit the proxy settings and add the port name by which we enable the ssh forwarding on the server .

Then from the jump-box we login into the server via the port from which we have enable for ssh forwarding.

Ex. ssh  -R 8060: <proxy>:8000 user@targetserver 

And then we patch the server.

[scottwilkerson]

Does nagios supposed to use automount? I see all of these on both server after patching:

Feb 19 11:23:01 usa0300lv886 automount[5564]: key "nagios" not found in map source(s).
Feb 19 11:25:01 usa0300lv886 automount[5564]: key "nagios" not found in map source(s).
Feb 19 11:27:01 usa0300lv886 automount[5564]: key "nagios" not found in map source(s).

I am not familiar with automount, it is not part of our install package... This was something that was added by your organization..

[disrael]

So the issue was resolved when they disabled autofs, thank you for your help.

[sreinhardt]

Thanks for letting us know!