Page 1 of 1
apache error
Posted: Tue Feb 05, 2013 3:56 pm
by jbennett
In checking the health of a new system, I found the following over and over and over again in my error_log for httpd:
Code: Select all
[Tue Feb 05 14:43:51 2013] [error] [client xxx.xxx.xxx.xxx] PHP Notice: Undefined variable: class in /usr/local/nagiosxi/html/includes/components/opscreen/merlin.php on line 275, referer: http://lnttavmnag1/nagiosxi/includes/components/opscreen/opscreen.php
Line 275 of /usr/local/nagiosxi/html/includes/components/opscreen/merlin.php
Code: Select all
<tr class="<?php print $class ?>">
Not being a programmer, I'm not sure what steps would be necessary to help resolve this?
Re: apache error
Posted: Tue Feb 05, 2013 4:11 pm
by sreinhardt
Which version of XI is this for? I see that we have some line changes with the newest one, and would like to be sure that it is resolved correctly.
Re: apache error
Posted: Tue Feb 05, 2013 4:18 pm
by jbennett
ahh, this is on 1.4.
Should I assume that it is resolved in 1.5b?
We run behind a proxy and I have to jump through hoops to open it back up and let someone else run the update. Thus the reason I don't have the ability to see when a new update is present via the Nagios interface.
Re: apache error
Posted: Tue Feb 05, 2013 4:19 pm
by jbennett
I should note that the issue came about when I started to notice that the 'Whoops!' screen when I click on Tactical Overview, but when I click on Home (where I have Tactical Overview set as my home screen), it will display just fine.
Re: apache error
Posted: Tue Feb 05, 2013 5:03 pm
by sreinhardt
I see where the issue is coming from. You can modify after line 277
Code: Select all
while ($row = mysql_fetch_array($result)) {
to
Code: Select all
while ($row = mysql_fetch_array($result)) {
$class = "";
Or you can wait for revision 1.6, I would not suggest upgrading to 1.5b as it has a few bugs that are nice if you can avoid them.
edit: 277 compared to my current revision. It would probably be 270ish for you.
Re: apache error
Posted: Wed Feb 06, 2013 8:57 am
by jbennett
This appears to have resolved the issues with the error log.
Many thanks!