Splitting web interface from the rest of nagios: Possible?

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Guy Waugh
> Sent: Wednesday, March 02, 2005 9:23 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Splitting web interface from the rest of
nagios:
> Possible?
> 
[snip]


>  From my reading about nagios thus far, it appears that I would have
to
> have the nagios CGI scripts available on both web servers, and that
the
> CGI scripts would have to have access to the configuration and state
> information used by nagios. As far as I can see, I can set this up
fine
> through NFS sharing.
> 
> I'm wondering if this will work, however... can anyone see why it
> wouldn't work? Does the nagios daemon have to be running on the same
> host that's serving the web interface? Any problems with file locking
> if, for example, the same CGI script running on both web servers wants
> to access the same file at the same time? Any other problems?

I'm doing something similar: I nfs export /usr/local/nagios from one
machine and mount it on another. You won't be able to issue external
commands from the web interface though if the command file is on an NFS
mount as nagios uses a named pipe. In my case that means I have two
servers that can be used to view the cgis, but I can only issue external
commands (acknowledgements, etc) with one of them.

--
Marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
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