I experienced a problem that may be similar. In my case, Zenoss was passing the url and it was being interpreted slightly differently by the target server than when a browser would pass the same url. In my case, the check_apache.py returned a 301 error.
For example, I watched the access log for apache like this: tail access_log -f |grep server-status When a browser accessed the page: [22/Oct/2008:19:43:08 -0400] "GET /server-status/ HTTP/1.0" 200 42262 HTTP/1.0" 200 means successful When Zenoss called for the url: [22/Oct/2008:19:58:23 -0400] "GET /server-status?auto HTTP/1.1" 301 247 HTTP/1.0" 301 means permanently moved So, I modified the template datasource apache status url >From -> /server-status?auto To -> /server-status/?auto <-note the extra / (it only took hours to figure this out) -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=26718#26718 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
