Nagios Support Forum

The thread can be closed. Thanks.

Actually, I just tried it again in XI and all three functions look like they are working. Maybe it had something to do with some kind of startup processing that it is doing:

[root@KALNAGIOS01 problemoverview]# chage -l nagios Last password change : Oct 14, 2013 Password expires : never Password inactive : never Account expires : never Minimum number of days between password change : 0 Maximum number of days between password change : 99999 Number of days of warning befo...

[root@KALNAGIOS01 html]# grep "date.timezone" /etc/php.ini ; http://www.php.net/manual/en/datetime.configuration.php#ini.date.timezone date.timezone = America/New_York [root@KALNAGIOS01 html]# ls -l /etc/localtime -rw-r--r-- 1 root root 3519 May 4 2010 /etc/localtime [root@KALNAGIOS01 htm...

[root@KALNAGIOS01 ~]# grep "date.timezone" /etc/php.ini ; http://www.php.net/manual/en/datetime.configuration.php#ini.date.timezone date.timezone = America/New_York [root@KALNAGIOS01 ~]# ls -l /etc/localtime -rw-r--r-- 1 root root 3519 May 4 2010 /etc/localtime [root@KALNAGIOS01 ~]# php -...

I just upgraded from XI 2014R1.4 to XI 5.2.9, and I am having problems with command processing. For example, scheduling a downtime on the Host Status Detail Advanced tab does nothing, not even the green command processing popup (that I can see anyway). “Force an immediate check” pops up the green co...

Yes, I made that config inactive in CCM and reran the upgrade. Looks like it will work this time.

I am upgrading from Nagios XI 2012R2.5 and I am receiving nearly the same error, just on a different config file. The log has: Nagios Core 4.0.7 Copyright (c) 2009-present Nagios Core Development Team and Community Contributors Copyright (c) 1999-2009 Ethan Galstad Last Modified: 06-03-2014 License:...

I have come up with a solution for resolving this problem (host name definitions must exactly match the case that comes from SNMP traps). Rather than asking for an enhancement (to Nagios Core) that would make the external command processing of a host name be case-insentive, I have updated the snmptr...

Okay, I can see that for the AVERAGE value, but why would it be averaging or aggregating for the LAST and MAX values? Shouldn't they be the last value that was reported and the maximum value that has been reported? Is there any way to tell it to report in whole numbers?