BLANK PAGE

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
matt.lilek
Posts: 137
Joined: Wed Aug 07, 2013 11:53 am

Re: BLANK PAGE

Post by matt.lilek »

That was one of the first things i tried before coming on to the support forum when i try to write the config i get a white screen in the area it should tell me the details of writing the config and when i hit verify it tells me everything is ok.
Last edited by slansing on Wed Oct 16, 2013 10:50 am, edited 1 time in total.
Reason: Please edit your previous post to add information/questions if you are the last poster.
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: BLANK PAGE

Post by abrist »

A couple of things:
1. Are you still noticing crashed table errors in your logs?
2. Is cron running?

Code: Select all

service crond status
ps -aef | grep cron
3. Do the following steps on the FAQ and post reconfig.txt and cmd.txt here:
http://support.nagios.com/wiki/index.ph ... n_Problems
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.
matt.lilek
Posts: 137
Joined: Wed Aug 07, 2013 11:53 am

Re: BLANK PAGE

Post by matt.lilek »

[root@localhost ~]# service crond status
crond (pid 1408) is running...
[root@localhost ~]# ps -aef | grep cron
root 1408 1 0 10:49 ? 00:00:00 crond
nagios 3869 3856 0 12:19 ? 00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php > /usr/local/nagiosxi/var/feedproc.log 2>&1
nagios 3886 3869 0 12:19 ? 00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php
nagios 5078 5073 0 12:20 ? 00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php > /usr/local/nagiosxi/var/perfdataproc.log 2>&1
nagios 5079 5076 0 12:20 ? 00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php > /usr/local/nagiosxi/var/cmdsubsys.log 2>&1
nagios 5085 5074 0 12:20 ? 00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php > /usr/local/nagiosxi/var/feedproc.log 2>&1
nagios 5086 5077 0 12:20 ? 00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php > /usr/local/nagiosxi/var/sysstat.log 2>&1
nagios 5088 5079 1 12:20 ? 00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php
nagios 5089 5075 0 12:20 ? 00:00:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php > /usr/local/nagiosxi/var/eventman.log 2>&1
nagios 5090 5078 1 12:20 ? 00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php
nagios 5095 5086 1 12:20 ? 00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php
nagios 5096 5085 1 12:20 ? 00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php
nagios 5099 5089 2 12:20 ? 00:00:00 /usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php
root 5406 4638 0 12:20 pts/1 00:00:00 grep cron
sreinhardt
-fno-stack-protector
Posts: 4366
Joined: Mon Nov 19, 2012 12:10 pm

Re: BLANK PAGE

Post by sreinhardt »

Are the dates on your configs updating after hitting write on the write config tool page? Also as abrist mentioned, did you follow the directions here?
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
toleolu
Posts: 294
Joined: Fri Jul 19, 2013 7:02 pm
Location: Honolulu Hawaii

Re: BLANK PAGE

Post by toleolu »

Being a noob, I'm hesitant to jump in at this point, but I had the same issue when I was importing config files. Hit Write and the screen would go blank. I think it's one of those buggy things in CCM, I switched to using the Legacy CCM and it worked fine.

Hope that helps, sorry if I misunderstood the problem.
Charles Masteller
Information Systems Specialist
Hawaii Health Systems Corp.
"No one will ever need more than 640K RAM". Bill Gates
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: BLANK PAGE

Post by abrist »

I would suggest performing a running tail on the httpd log and then try to write the files. Afterwards, kill the running tail and post the output here:

Code: Select all

tail -f /var/log/httpd/error_log
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.
Locked