Scheduled Downtime not displaying in version 2.7

[QS1]

NagiosXI 2.7
centos 5.4 (final) VM
GUI KDE

The Scheduled Downtime web page is not displaying (/nagiosxi/includes/components/nagioscore/ui/extinfo.php?type=6)

I noticed this same instance in version 1.7 and ignored it hoping it would be fixed in 2.7..I verified the page did display correctly right after the upgrade to 2.7 but now its gone again? Help.

[slansing]

Seems like something must have gotten goofed up on your system. Can you run the following when trying to access the page?:

Code: Select all

tail -f /var/log/httpd/error_log

Please share the captured output in a reply here. Also, are you accessing this through XI or through the core front end?

[QS1]

I am acessing the page through XI.

The following output shows after tail -f /var/log/httpd/error_log


[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined index: servicestate in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 392, referer: http://nagios/nagiosxi/config/monitoringwizard.php
[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined index: servicestate in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 392, referer: http://nagios/nagiosxi/config/monitoringwizard.php
[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined index: servicestate in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 392, referer: http://nagios/nagiosxi/config/monitoringwizard.php
[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined index: servicestate in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 392, referer: http://nagios/nagiosxi/config/monitoringwizard.php
[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined offset: 1 in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 410, referer: http://nagios/nagiosxi/config/monitoringwizard.php
[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined offset: 2 in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 410, referer: http://nagios/nagiosxi/config/monitoringwizard.php
[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined offset: 3 in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 410, referer: http://nagios/nagiosxi/config/monitoringwizard.php
[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined offset: 3 in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 431, referer: http://nagios/nagiosxi/config/monitoringwizard.php
[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined offset: 4 in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 431, referer: http://nagios/nagiosxi/config/monitoringwizard.php
[Wed Jan 08 15:16:50 2014] [error] [client 10.0.130.203] PHP Notice: Undefined offset: 5 in /usr/local/nagiosxi/html/includes/configwizards/windowsserver/windowsserver.inc.php on line 431, referer: http://nagios/nagiosxi/config/monitoringwizard.php

[lmiltchev]

Are you having issues with accessing this page only or you have similar issues, while trying to access other pages as well? Do you see this behavior in all browsers?

Can you show us a little bit more of the apache error log? Run the following command and post the output in code wraps:

Code: Select all

tail -100 /var/log/httpd/error_log

Note: You have KDE on this system. This may be part of the issue. I am not a 100% sure, but we recommend installing XI on a "clean" system, minimal install - no gnome, kde, etc.

Important: Nagios Enterprises highly recommends and will only support installing Nagios XI on a newly installed, "clean" system. Attempting to install Nagios XI on a pre-existing system with other applications already installed can cause the Nagios XI installation process to fail, critical system components and settings (e.g. database servers) to be modified in a way that negatively affects other applications, and previously installed applications to be automatically upgraded or removed. While installing XI on a system with other applications is possible, it is not recommended due to the possible interactions and complexity of multiple components that are required for Nagios XI to function. If you choose to ignore these warnings, you do so at your own risk.

[QS1]

The following output shows after tail -100 /var/log/httpd/error_log

[Sun Jan 12 04:03:48 2014] [notice] Digest: generating secret for digest authentication ...
[Sun Jan 12 04:03:48 2014] [notice] Digest: done
[Sun Jan 12 04:03:48 2014] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Sun Jan 12 04:03:49 2014] [notice] SSL FIPS mode disabled
[Sun Jan 12 04:03:49 2014] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
[Mon Jan 13 08:36:24 2014] [error] [client 10.6.60.150] File does not exist: /usr/local/nagiosxi/html/includes/components/nagioscore/ui/images/logos/windowsserver.png, referer: http://10.0.50.59/nagiosxi/includes/com ... tustypes=0
[Mon Jan 13 08:36:56 2014] [error] [client 10.6.60.150] File does not exist: /usr/local/nagiosxi/html/includes/components/nagioscore/ui/images/logos/windowsserver.png, referer: http://10.0.50.59/nagiosxi/includes/com ... tustypes=0
[Mon Jan 13 09:31:45 2014] [error] [client 10.6.60.150] File does not exist: /usr/local/nagiosxi/html/includes/components/nagioscore/ui/images/logos/windowsserver.png, referer: http://10.0.50.59/nagiosxi/includes/com ... tustypes=0
[Mon Jan 13 09:32:16 2014] [error] [client 10.6.60.150] File does not exist: /usr/local/nagiosxi/html/includes/components/nagioscore/ui/images/logos/windowsserver.png, referer: http://10.0.50.59/nagiosxi/includes/com ... tustypes=0
[Mon Jan 13 11:15:08 2014] [warn] child process 32734 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 3481 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 11256 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 6381 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 12874 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 10646 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 16748 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 30338 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 6361 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 7576 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 4785 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 7439 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:08 2014] [warn] child process 26642 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 32734 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 3481 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 11256 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 6381 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 12874 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 10646 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 16748 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 30338 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 6361 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 7576 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 4785 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 7439 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:11 2014] [warn] child process 26642 still did not exit, sending a SIGTERM
[Mon Jan 13 11:15:12 2014] [notice] caught SIGTERM, shutting down
[Mon Jan 13 11:17:10 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Jan 13 11:17:10 2014] [notice] SSL FIPS mode disabled
[Mon Jan 13 11:17:10 2014] [notice] Digest: generating secret for digest authentication ...
[Mon Jan 13 11:17:10 2014] [notice] Digest: done
[Mon Jan 13 11:17:11 2014] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Mon Jan 13 11:17:11 2014] [notice] SSL FIPS mode disabled
[Mon Jan 13 11:17:11 2014] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations
[Mon Jan 13 11:17:14 2014] [error] [client 10.6.60.150] PHP Warning: pg_pconnect() [<a href='function.pg-pconnect'>function.pg-pconnect</a>]: Unable to connect to PostgreSQL server: could not connect to server: Connection refused\n\tIs the server running on host "localhost" and accepting\n\tTCP/IP connections on port 5432? in /usr/local/nagiosxi/html/db/adodb/drivers/adodb-postgres64.inc.php on line 682, referer: http://10.0.50.59/nagiosxi/
[Mon Jan 13 11:17:14 2014] [error] [client 10.6.60.150] PHP Warning: pg_pconnect() [<a href='function.pg-pconnect'>function.pg-pconnect</a>]: Unable to connect to PostgreSQL server: could not connect to server: Connection refused\n\tIs the server running on host "localhost" and accepting\n\tTCP/IP connections on port 5432? in /usr/local/nagiosxi/html/db/adodb/drivers/adodb-postgres64.inc.php on line 682, referer: http://10.0.50.59/nagiosxi/
[Mon Jan 13 11:17:14 2014] [error] [client 10.6.60.150] PHP Warning: pg_pconnect() [<a href='function.pg-pconnect'>function.pg-pconnect</a>]: Unable to connect to PostgreSQL server: could not connect to server: Connection refused\n\tIs the server running on host "localhost" and accepting\n\tTCP/IP connections on port 5432? in /usr/local/nagiosxi/html/db/adodb/drivers/adodb-postgres64.inc.php on line 682, referer: http://10.0.50.59/nagiosxi/
[Mon Jan 13 11:17:14 2014] [error] [client 10.6.60.150] PHP Warning: pg_pconnect() [<a href='function.pg-pconnect'>function.pg-pconnect</a>]: Unable to connect to PostgreSQL server: could not connect to server: Connection refused\n\tIs the server running on host "localhost" and accepting\n\tTCP/IP connections on port 5432? in /usr/local/nagiosxi/html/db/adodb/drivers/adodb-postgres64.inc.php on line 682, referer: http://10.0.50.59/nagiosxi/
[Mon Jan 13 11:17:14 2014] [error] [client 10.6.60.150] PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/nagiosim/nagiosim.inc.php on line 384, referer: http://10.0.50.59/nagiosxi/
[Mon Jan 13 11:17:14 2014] [error] [client 10.6.60.150] PHP Warning: Invalid argument supplied for foreach() in /usr/local/nagiosxi/html/includes/components/nagiosim/nagiosim.inc.php on line 384, referer: http://10.0.50.59/nagiosxi/
[root@nagiosxi ~]#

[sreinhardt]

Well, let's start by making sure the postgres daemon is running, and if not restart it.

Code: Select all

service postgresql status
service postgresql restart

[QS1]

Restarting the service does not display the scheduled downtime page..Restarting the VM does not display the scheduled downtime page

[root@nagiosxi ~]# service postgresql status
postmaster (pid 32269 32232 32207 32180 32179 31394 31257 29384 28277 27834 27754 27747 27738 27736 27721 22582 22219 22135 9943 9438 8461 8283 8087 8081 5241 4694 3833 3832 3831 3829 3623) is running...
[root@nagiosxi ~]# service postgresql restart
Stopping postgresql service: [ OK ]
Starting postgresql service: [ OK ]
[root@nagiosxi ~]#

[slansing]

After restarting postgresql do you still have a large number of PID's associated with it?:

Code: Select all

service postgresql status

[QS1]

Yes there appear to still be large pids

[root@nagiosxi ~]# service postgresql status
postmaster (pid 18195 17242 17227 17224 17221 15630 14692 14010 13081 12401 12195 12184 12164 12089 12084 12083 12082 12081 12080 12079 11551 11544 11543 11542 11541 11540 11539 11538 11494 11380) is running...
[root@nagiosxi ~]#

[QS1]

It appears we are getting too large for the 32 Bit environment (memory restrictions) and plan to update to a 64 Bit OS VM. The downtime page is more than likely a side effect of our resource limitation. IThank you for you assistance..this ticket can be closed