To add to what Will is saying we are running Opsview 3.5 Our installation would be on the larger side with 955 hosts and 3300 services but those are checks are spread across 23 remote slave servers so the master server just runs the database and web portions of Opsview.
Just doing a 1 day availability reports on one service took 1.5 minutes. By comparison I help manage a customer system over twice as large (2400 hosts, 6000 services, 6 slaves) and the same report takes 1-2 secs.. Both the slow and fast systems run under ESX so I suspect disk access may be the culprit but any guidance would be appreciated. James Whittington VC3, Inc. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Will VanDuzer Sent: Tuesday, November 23, 2010 8:31 AM To: Opsview Users Subject: [opsview-users] Reports Error with HTTP 502 Hey all, About 95% of the reports we run end up getting an HTTP 502 error that says "Opsview Error" "The Opsview Web Server is not running or is not responding to requests!" Most of the time, smaller reports will run but anything over a few days errors out. When reports are run, the cgi process (avail.cgi or whatever) takes up one of the CPUs for a couple minutes before it times out. Any ideas? We are still on Opsview 3.5. Thanks, Will _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
