NLG Errors

[Richard Luys]

Hi All,

We think NLG is for us (thanks Andy!) but we can't get it to work. Here's  
some details:
OS: SLES10 32 bits
NLG: 1.0.6 and 1.1.0b1
HTTPD: Apache2-2.2.3
PHP: PHP5-5.1.2
Browser: Firefox 1.5.0.6

Afaik all dependencies are solved. Server directory is copied to the  
Nagios server in /usr/local/nagios/share, and client dir is copied to the  
Webserver in /srv/www/htdocs. both are named 'nlg' which is reflected in  
the configfiles.

We followed the PDF document to configure everything, but we get garbled  
output on the web GUI, and some errors in the apache logs:

[Thu May 08 14:43:33 2008] [error] [client 10.10.10.10] PHP Notice:   
Undefined variable: NLG_Language in /srv/www/htdocs/nlg/s3_client.php on  
line 86 [Thu May 08 14:43:33 2008] [error] [client 10.10.10.10] PHP  
Warning:  require(sync-files/s3_lang_.inc.php) [<a  
href='function.require'>function.require</a>]: failed to open stream: No  
such file or directory in /srv/www/htdocs/nlg/s3_client.php on line 86  
[Thu May 08 14:43:33 2008] [error] [client 10.10.10.10] PHP Fatal error:   
require() [<a href='function.require'>function.require</a>]: Failed  
opening required 'sync-files/s3_lang_.inc.php'  
(include_path='.:/usr/share/php5:/usr/share/php5/PEAR') in  
/srv/www/htdocs/nlg/s3_client.php on line 86

Curious if anyone has any clues; googling didn't help much :(

Rgds and thanks in advance,
Richard

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null