VMware Cloud Community
stevarino
Contributor
Contributor

Incorrect Apache 2.0 availability

We are monitoring an Apache 2.0 server and the availability had been reliable until today. We've added mod_jk2 to Apache and another Tomcat 5.5 instance on the platform. The Hyperic HQ server is also running on this platform but the ports are configured to not overlap.

Now, the Apache 2.0 server is being flagged as unavailable although the /server-status information is available. Any idea what's causing the false reading?
0 Kudos
2 Replies
staceyeschneide
Hot Shot
Hot Shot

Any chance that the server times are offset? An easy way to check is to go into Administration and HQ Health, and if you check the tab for the agents it should have server offset. Sometimes if this is off, the availability is calculated as not available since the last report is stamped before the server time and the metrics are still reporting in.
0 Kudos
stevarino
Contributor
Contributor

I've seen this in other cases, but the server and agent are running on the same platform as the Apache httpd so I don't think there is any way for the time to be skewed.
0 Kudos