Separate NAG from Web Interface

[Alexander Schreiber]

On Wed, May 14, 2003 at 11:52:43PM -0700, Chris Robertson wrote:
> One other possiblity would be to store all your service information in a
> MySQL database and replicate that to your webserver.  Natively that probably

This does not sound like a good idea to me. The database backend of the
current release of Nagios looks seriously broken to me. I initially set
up my Nagios server with a PostgreSQL database as backend storage for
all objects where this was supported and quickly (at around 20 hosts and
60 services) found duplicate object entries. Upon examing the source I
concluded that the database backends are best avoided, switched to file
based backend storage (which AFAIR is the default anyway) and that was
the end of the trouble.

> wouldn't be a whole lot more secure than NFS but with a little work you
> should be able to pipe it across SSH and only have MySQL listening on
> localhost.

One approach would be to replicate the Nagios log- and datafiles in
regular intervals (every minute or so, needs testing) from the Nagios
server to your webserver using rsync over ssh. Not exactly elegant in my
eyes, but it might just work.

> -----Original Message-----
> From: Carroll, Jim P [Contractor] [mailto:jcarro10 at sprintspectrum.com]
> Sent: Wednesday, May 14, 2003 1:56 PM
> To: Anthony Brock; nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Separate NAG from Web Interface
> 
> 
> NSCA could possibly do this.  However, this means that you
> will also need to set up Nagios on your webserver.
> 
> If you do *not* want to set up Nagios on your webserver,
> then you'll have to somehow make the cgi's and so on available
> to the webserver.  One way would be to use rsync, but that would
> have to hit it pretty frequently.  Another way would be to use
> NFS.  But you've stated that your webserver is already hardened;
> I'm sure you understand the implications of enabling NFS on a
> secure host.
> 
> Are you sure you don't want to set up a new webserver?
> 
> > -----Original Message-----
> > From: Anthony Brock [mailto:Anthony_Brock at ous.edu]
> > Sent: Wednesday, May 14, 2003 1:22 PM
> > To: nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] Separate NAG from Web Interface
> > 
> > 
> > Okay, I have Nagios 1.0 up and running on a test system. So far, I am
> > very impressed with this as compared to Big Brother (the system I was
> > previously using).
> > 
> > However, how do you separate the web interface from the monitoring
> > server? I have a machine to house the Nagios software, however I don't
> > want to run an web server on this machine. Ideally, I would like to
> > have a web interface with much (if not all) of the current
> > functionality that is located on an existing (hardened and watched)
> > web server. Is this possible? Does anyone know how to do this?
> > 

Regards,
      Alex.
-- 
"Opportunity is missed by most people because it is dressed in overalls and
 looks like work."                                      -- Thomas A. Edison


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

_______________________________________________
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