Hi All
I'm trying to run two instances of Nagios on the same machine using virtual hosts, but I'm having trouble. Has anyone succeeded at this? I've checked over some old posts with suggestions but the CGIs just don't seem to work with two instances. The specifics -- We are monitoring a large network and have 24/7 operators watching the console and pager and e-mail. Nagios is great for alerting them so they can notify the right department/technician. The operators are not allowed to change the status, such as disabling notifications, acknowledgements... This is strictly a read-only interface. Hence, their web login is via a privledged account which allows them to view all hosts and services, but can't change anything. Their e-mail comes from a different account. Now we have developers who want to monitor their test/development machines and I don't want these failures to reach the operators' web interface. Since the operators are viewing a privledged screen, there's no way to prevent them from seeing the test boxes. My current attempt uses a single Nagios install with separate test directories, many linked back to the installed ones. Running the CGI in the test directory shows all the hosts from the production instance. If two instances isn't the best way to solve this, are there any other suggestions? Thanks, - David Schlecht (dschl) ----------------------- The mailing list archive is found here: http://www.nagiosexchange.org/nagios-users.34.0.html ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Nagios-users mailing list Nagios-users@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