I plan to do a Yum Update on my Nagios XI production server, as I read in some other post on this forum this shouldn't cause any issues. So today I started doing the yum update on my Nagios XI test server. Everyhting seemed to update fine except the update update udev.x86_64 0:147-2.46.el6
Where someone told me someone used chattr to mark that file as immutable so it cannot be overwritten. As I never heard of Chattr and certainly am not messing with any system or os related things I have no knowledge of, I thought maybe Nagios support knows what udev is and why it is locked from yum update.
udev is a device manager, though I'm not sure why anyone would be messing with it like that. chattr -i on the file should remove the immutable bit and let you update.
Kind of having the same issue, again with the udev package, on my Nagios QA system, as well as my PR system. I managed to solve it last time, still need to try same solution this time, but I wanted to put it on the forum, because I do suspect it has something to do with Nagios..
As my QA system is almost clean, I'm wondering what could cause this update to fail again...
WillemDH wrote:I'll let you know if the previous solutions works again.
Alright, let us know
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Please keep this thread open. I'm pretty sur I'll have the same issue next update. Still strange I'm the only one having this issue on Nagios forum. I can't be the only one.
I highly doubt this is nagios specific. We really don't do anything at all with udev. I have definitely seen this issue or similar on my own cent systems(nagios and non) and other distros that stay way ahead of Cent\RHEL a few months ago. I believe it's just more to do with udev changes for systemctl and systemd, but I could be wrong. (it's happened before)
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.