System status Issue

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
rdhall01
Posts: 87
Joined: Wed Nov 09, 2011 9:53 am

System status Issue

Post by rdhall01 »

After upgrading to the latest version Nagios XI 2012R2.3 The system status componenet has a spinning icon no status displayed! I tried to restatrt nagios from the command line to reolve, but no luck any ideas of how to resolve it!

Information and alerts at the bottom of the gui also just spinning!
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: System status Issue

Post by abrist »

Is cron running?

Code: Select all

service crond status
If not, start it:

Code: Select all

service crond start
If so, restart it:

Code: Select all

service crond stop
ps -aef|grep cron
service crond start
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
rdhall01
Posts: 87
Joined: Wed Nov 09, 2011 9:53 am

Re: System status Issue

Post by rdhall01 »

I dont thin that resolved it but I think the other symptoms i believe to be red herring / false alarm after looking closer to the issue the applying configuration
waiting for configuration verification...........
was taking more than 5 mins to fail then I get

Applying Configuration

Command submitted for processing...
Waiting for configuration verification........................................
Configurations failed to write to file.
An error occurred while attempting to apply your configuration to Nagios Core. Monitoring engine configuration files have been rolled back to their last known good checkpoint.

View a snapshot of this configuration error

I go to

Monitoring Configuration Snapshots

The latest configuration snapshots of the XI monitoring engine are shown below. Download the most recent snapshots as backups, or get vital information for troubleshooting configuration errors.

Date Snapshot Result File Actions
2013-09-10 15:32:53 Config Ok 1378841573.tar.gz Download View OutputRestore
2013-09-10 15:32:44 Config Ok 1378841564.tar.gz Download View OutputRestore
2013-09-10 14:14:48 Config Ok 1378836888.tar.gz Download View OutputRestore
2013-09-10 14:06:25 Config Ok 1378836385.tar.gz Download View OutputRestore
2013-09-10 12:36:59 Config Ok 1378831019.tar.gz Download View OutputRestore
2013-09-10 11:20:59 Config Ok 1378826459.tar.gz Download View OutputRestore
2013-09-10 10:35:17 Config Ok 1378823717.tar.gz Download View OutputRestore
2013-09-10 10:32:15 Config Ok 1378823535.tar.gz Download View OutputRestore
2013-09-10 10:30:00 Config Ok 1378823400.tar.gz Download View OutputRestore
2013-09-09 20:11:02 Config Ok 1378771862.tar.gz Download View OutputRestore

if I look at the latest config no errors or warnings included is tthe output
You do not have the required permissions to view the files attached to this post.
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: System status Issue

Post by abrist »

The verification you attached is clean. You may be hitting the limits set in you php.ini file. Lets check the current settings, please post the output of:

Code: Select all

grep "memory_limit\|max_execution\|max_input" /etc/php.ini
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
rdhall01
Posts: 87
Joined: Wed Nov 09, 2011 9:53 am

Re: System status Issue

Post by rdhall01 »

grep "memory_limit\|max_execution\|max_input" /etc/php.ini
max_execution_time = 30 ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 128M ; Maximum amount of memory a script may consume
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: System status Issue

Post by abrist »

Lets increase these values. Change them to:

Code: Select all

max_execution_time = 60 ; Maximum execution time of each script, in seconds
max_input_time = 90 ; Maximum amount of time each script may spend parsing request data
memory_limit = 512M ; Maximum amount of memory a script may consume
Then restart apache:

Code: Select all

service httpd restart
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
rdhall01
Posts: 87
Joined: Wed Nov 09, 2011 9:53 am

Re: System status Issue

Post by rdhall01 »

values changes and httpd restarted

grep "memory_limit\|max_execution\|max_input" /etc/php.ini
max_execution_time = 60 ; Maximum execution time of each script, in seconds
max_input_time = 90 ; Maximum amount of time each script may spend parsing request data
memory_limit = 512M ; Maximum amount of memory a script may consume
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: System status Issue

Post by abrist »

Go ahead and try to apply config once again.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
rdhall01
Posts: 87
Joined: Wed Nov 09, 2011 9:53 am

Re: System status Issue

Post by rdhall01 »

winner that resolved the issue thx
Locked