Nagios Looking Glass problem

[Andy Shellam]

Hi Joe,

Have you tried NLG 1.0.3?  That is the latest version and includes, 
amongst others, the fix in the config file as you mentioned.

These errors appear at first glance to be typically permissions, 
particularly with the client accessing s3_download.php.
A typical test would be to enable debugging in server/s3_config.inc.php, 
then try and access:

http://yourserver/nagios/share/server/s3_download.php?filename=s3_config.inc.php&action=check

If you get an MD5 hash back, then the server side is working OK, and 
it's a problem with the client script connecting to s3_download.php 
(perhaps invalid username/password for HTTP authentication, no 
username/password supplied when required, invalid URL etc.)
If not, it's a web server configuration error (or invalid/denied URL.)

One thing I have just noticed while writing this, your client script is 
at http://myservername/nagios/client, yet your server is trying to 
connect to http://myservername/nagios/share/server (should the "share" 
directory really be there?)  If your "server" directory is at the same 
level as "client" in the file-system, then it looks like your server 
feed URL should be http://myservername/nagios/server.

HTH

Andy.

joe.stringfellow at liverpool.com wrote:
>
> I had installed Nagios Looking Glass 1.2 and Nagios 2.5 on a computer 
> running Fedora Core 5 with PHP v 5.2 but couldn’t get any results 
> unfortunatley. Therefore I amended the S3_config.inc.php file to 
> include the $NLG_LineEnding = “/”; that I read somewhere was included 
> in the latest update.
>
>
> When I try to connect to the nagios server 
> (_http://myservername/nagios/client/?debug=yes_ I get the following 
> error. Even on the same machine if I try 
> http://127.0.0.1/nagios/client/ I still get the following result.
>
> Attempting to download files from 
> http://xxx:xxx@nagiosserver/nagios/share/server/s3_download.php
>
> Synchronising s3_class.inc.php with server ...  failed sync'ing with 
> server
> Synchronising s3_config.inc.php with server ...  failed sync'ing with 
> server
> Etc,etc
>
> *** Download Stub -> DownloadFiles() finished ***
>
> *** S3 Client -> CheckSyncFiles() running ***
> Checking s3_class.inc.php ... FILE NOT FOUND or FILE IS EMPTY
> Checking s3_config.inc.php ... FILE NOT FOUND or FILE IS EMPTY
> Etc,etc
>
> I checked to ensure that permissions for all files under 
> usr/local/nagios/share/client and usr/local/nagios/share/server are 
> all owned by apache (the account running httpd) and have read/write 
> access.
>
> The apache user has read/write access to /usr/local/nagios/var and all 
> its files. I’ve made the apache account the owner of all files apart 
> from the status.dat file as this is owned by the nagios user and I 
> cannot seem to change it. (The apache account is in the same group as 
> the nagios user has read/write access through this group account though.)
>
> Any assistance that anyone can provide would be greatly appreciated.
>
> Thanks,
>
> Joe
>
>
> ******************** IMPORTANT NOTICE This email (including any 
> attachments) is meant only for the intended recipient. It may also 
> contain confidential and privileged information. If you are not the 
> intended recipient, any reliance on, use, disclosure, distribution or 
> copying of this email or attachments is strictly prohibited. Please 
> notify the sender immediately by email if you have received this 
> message by mistake and delete the email and all attachments. Any views 
> or opinions in this email are solely those of the author and do not 
> necessarily represent those of Trinity Mirror PLC or its associated 
> group companies (hereinafter referred to as "TM Group"). TM Group 
> accept no liability for the content of this email, or for the 
> consequences of any actions taken on the basis of the information 
> provided, unless that information is subsequently confirmed in 
> writing. Although every reasonable effort is made to keep its network 
> free from viruses, TM Group accept no liability for any virus 
> transmitted by this email or any attachments and the recipient should 
> use up-to-date virus checking software. Email to or from this address 
> may be subject to interception or monitoring for operational reasons 
> or for lawful business practices. Trinity Mirror PLC is the parent 
> company of the Trinity Mirror group of companies and is registered in 
> England No 82548, with its address at One Canada Square, Canary Wharf, 
> London E14 5AP. ******************** !DSPAM:37,46015a72103002435764642!
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> !DSPAM:37,46015a72103002435764642!
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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
>
> !DSPAM:37,46015a72103002435764642!
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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