Strange issue after upgrade to 5.5.1

[JohnFLi]

Ok, I can't figure this one out, maybe you can see the issue.
After I update to Nagios XI 5.5.1

Code: Select all

Latest Available Version:	5.5.1
Installed Version:	5.5.1
Last Update Check:	07/19/2018 11:24:02

my checks for the Dell Openmange stopped working and was giving a 'permission denied' error

I found the issue with the file, the properties removed the (allow executing file as a program) attribute. So I set that back, all was good.....for a little while (hour or two). I'd start getting the error again, and that attribute reset itself. The file in question was located here:

Code: Select all

/usr/local/nagios/etc/check_openmanage/check_openmanage

So I relocated it to here:

Code: Select all

/usr/local/nagios/libexec/check_openmanage

and I changed the command to reflect the change

Code: Select all

define command {
                                 command_name   check_openmanage
                                 command_line      /usr/local/nagios/libexec/check_openmanage -H $HOSTADDRESS$ -C
}

After that, I go to either Nagios Core, or XI and manually tell it to check now. It works, and life is good.

but now, they are all failing again

Code: Select all

(No output on stdout) stderr: execvp(/usr/local/nagios/etc/check_openmanage/check_openmanage, ...) failed. errno is 2: No such file or directory 

That is where the file USE to be, but as you can see above, the command should not be looking there anymore.

any thoughts as to why a file attribute would get changed for whatever reason?
and/or
any thoughts as to why it doesn't want to run a file at the location i told it to?

[scottwilkerson]

any thoughts as to why a file attribute would get changed for whatever reason?
and/or
any thoughts as to why it doesn't want to run a file at the location i told it to?

Depends on when you moved it.

Can you verify you do not have multiple nagios parent processes

Code: Select all

ps -ef|grep nagios.cfg

[JohnFLi]

I moved it after I did the update due to the issue starting (file being marked as no longer executible)

as for your request:

Code: Select all

# ps -ef|grep nagios.cfg
nagios    5473     1  0 Jul17 ?        00:16:19 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios    5505  5473  0 Jul17 ?        00:00:07 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios   15768     1  0 11:48 ?        00:01:22 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios   15826 15768  0 11:48 ?        00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
root     26318 25959  0 15:41 pts/0    00:00:00 grep nagios.cfg

[JohnFLi]

after seeing how many line items is in after running that line,
I restarted the nagios machine.
upon coming back up, it currently looks good

[scottwilkerson]

after seeing how many line items is in after running that line,
I restarted the nagios machine.
upon coming back up, it currently looks good

Yes there were 2 parent processes, your restart likely solved the issue

[JohnFLi]

It's been several hours, and it's still good.

You can close this item.

[scottwilkerson]

It's been several hours, and it's still good.

You can close this item.

Excellent Locking