Page 1 of 1
Scheduled downtime page not showing after upgrade 2.3->2.7
Posted: Mon Jan 13, 2014 4:06 am
by fogier
CentOS 6 x64 VM (clean install) on vsphere 5.0 Update 2 (1vCPU and 4GB RAM).
This morning we've upgraded our Nagios XI 2012v2.3 to v2.7. After the upgrade the page "Scheduled down time" isn't available. Screen remains blank.
In the apache errorlog this error occurs:
Code: Select all
[Mon Jan 13 10:00:54 2014] [error] [client 145.32.229.244] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 36885192 bytes) in /usr/local/nagiosxi/html/includes/components/nagioscore/coreuiproxy.inc.php on line 157, referer: http://ssc-nagios/nagiosxi/
This wasn't there before the upgrade.
Re: Scheduled downtime page not showing after upgrade 2.3->2
Posted: Mon Jan 13, 2014 9:16 am
by fogier
Update: Our test server doesn't have the problem. However, there are only 3 hosts in there. The production server has 281 hosts (+/- 1000 service checks).
Re: Scheduled downtime page not showing after upgrade 2.3->2
Posted: Mon Jan 13, 2014 11:15 am
by slansing
Please share the output of:
You may need to increase the limit and restart apache.
Re: Scheduled downtime page not showing after upgrade 2.3->2
Posted: Wed Jan 15, 2014 1:30 am
by fogier
output
Code: Select all
; Maximum amount of memory a script may consume (128MB)
; http://www.php.net/manual/en/ini.core.php#ini.memory-limit
memory_limit = 128M
; If this parameter is set to Off, then memory leaks will not be shown (on
; enabled, registering these variables consumes CPU cycles and memory each time
; A default size of the shared memory segment
We've removed some recurring downtime for a servicegroup so that or status.dat could shrink from 36MB to 11MB. We've changed the timeperiod for that service. Now the scheduled downtime webpage is available.
However, the recurring downtime setting for a servicegroup that I removed is still present in this screen.
Re: Scheduled downtime page not showing after upgrade 2.3->2
Posted: Wed Jan 15, 2014 4:55 am
by fogier
It looks like we found the root of the problem. The status.dat file was 36MB and this file is used to build the screen.
We've removed the scheduled downtime entries for a servicegroup and our file is now 1,8MB.
I've seen this probleem before on the forum but can't seem to find it.
When a downtime is scheduled on a servicegroup not 1 but a lot of (unnecessary duplicate) comments are being made for that service. That service runs on a lot of hosts so service * comments * hosts = large status.dat
Re: Scheduled downtime page not showing after upgrade 2.3->2
Posted: Wed Jan 15, 2014 9:56 am
by tmcdonald
Yea, that would make sense. Is this working now? Can I lock the topic?
Re: Scheduled downtime page not showing after upgrade 2.3->2
Posted: Thu Jan 16, 2014 1:31 am
by fogier
yes, you can lock it.
however, I hope dat this bug will be fixed though.
Re: Scheduled downtime page not showing after upgrade 2.3->2
Posted: Thu Jan 16, 2014 10:21 am
by tmcdonald
fogier wrote:yes, you can lock it.
however, I hope dat this bug will be fixed though.
Not sure if this is a bug, but you can always file a bug report
here.