Page 1 of 1
post-upgrade service comments, force immediate check
Posted: Mon Dec 08, 2014 6:42 am
by iivanyi
Hello,
I've just upgraded to Nagios XI 2014R2.0 and one issue I'm having is Acknowledge/Schedule immediate check/Disable Notifications on services does not seem to be working.
I can clearly see the service I've asked to disable in /usr/local/nagios/var/rw/nagios.cmd
[1418038780] DISABLE_SVC_NOTIFICATIONS;mia0lxpxy01;Linux SSH Server
However, it does not seem to take effect (at least in GUI)
Service notifications that were disable pre-upgrade are still in effect though.
Re: post-upgrade service comments, force immediate check
Posted: Mon Dec 08, 2014 7:05 am
by iivanyi
I've tried to have a look at my account and now notice that I can't access it and notice the following in httpd logs
PHP Notice: Undefined variable: ad_password in /usr/local/nagiosxi/html/includes/components/active_directory/active_directory.php on line 431, referer:
https://nagios.citco.com/nagiosxi/admin/
we're using
Active Directory Integration
Uses Active Directory as a user authentication source. Experimental.
Version: 0.4 Author: Nagios Enterprises, LLC
Re: post-upgrade service comments, force immediate check
Posted: Mon Dec 08, 2014 5:21 pm
by sreinhardt
Those are likely completely separate issues. Let's start with the nagios.cmd issue. Let's list current permissions, remove it, and let nagios recreate it properly. All of the issues you mentioned, excluding AD would be related to this file.
Code: Select all
ls -lat /usr/local/nagios/var/rw/nagios.cmd
service nagios stop
rm -f /usr/local/nagios/var/rw/nagios.cmd
service nagios start
ls -lat /usr/local/nagios/var/rw/nagios.cmd
Re: post-upgrade service comments, force immediate check
Posted: Tue Dec 09, 2014 3:31 am
by iivanyi
apologies, I may have been a bit quick about that AD issue, it may just be (aside from the httpd error log message) my clicking in the wrong spot
a little bit muddled due to command copy/paste
Code: Select all
$ls -lat /usr/local/nagios/var/rw/nagios.cmd
service nagios stop
rm -f /usr/local/nagios/var/rw/nagios.cmd
-rw-rw-rw- 1 nagios nagcmd 548864 Dec 9 09:25 /usr/local/nagios/var/rw/nagios.cmd
service$service nagios stop
nagios start
ls -lat /usr/local/nagios/var/rw/nagios.cmdStopping nagios: .
done.
$rm -f /usr/local/nagios/var/rw/nagios.cmd
$service nagios start
Starting nagios: done.
$ls -lat /usr/local/nagios/var/rw/nagios.cmd
ls: cannot access /usr/local/nagios/var/rw/nagios.cmd: No such file or directory
$ls -lat /usr/local/nagios/var/rw/nagios.cmd
-rw-rw-rw- 1 nagios nagcmd 0 Dec 9 09:25 /usr/local/nagios/var/rw/nagios.cmd
however, this hasn't resolved anything
Re: post-upgrade service comments, force immediate check
Posted: Tue Dec 09, 2014 4:50 am
by iivanyi
ok, you can close this.
There is another process we use that is launched during nagios restart that is creating the .cmd file before nagios does. So I've added in a while/test -e nagios.cmd/sleep before starting that process.
The mystery here to me is why our test system is functioning fine and the nagios.cmd file is not created as a pipe.
Performance seems to be suffering since the upgrade, is there an updated 2014 performance guide yet?
Regards
Re: post-upgrade service comments, force immediate check
Posted: Tue Dec 09, 2014 12:43 pm
by sreinhardt
There has not been an updated performance guide, as most of the same statements apply. Immediate actions cannot operate properly without the cmd file being a pipe, there are no exceptions to this, as your linux operating system would not allow data to be sent to the process. I would suggest removing anything that creates a different nagios.cmd, that sounds rather troublesome.