Nagios Support Forum

It does look like the server responds, as code 200 is "OK". Were there any upgrades to either the nagios box or the remote host before this started happening? (especially apache updates?)

This smells like an apache problem . . . .

Nope, I run all these servers on VMware and on a bridged connection. The way the network is set up is you cant access the internet on bridged, only on NAT.

So the servers have had no connection to the internet in order to update.

Funny thing is, the requests check is still working, is it not? That means the plugin is working fine, it is just the traffic portion is not parsing the status page information correctly. Maybe download the plugin again and run a diff between that and your current plugin to make sure you don't have a larger issue(corruption etc).

abrist wrote:Funny thing is, the requests check is still working, is it not? That means the plugin is working fine, it is just the traffic portion is not parsing the status page information correctly. Maybe download the plugin again and run a diff between that and your current plugin to make sure you don't have a larger issue(corruption etc).

Correct, Number of requests is still working.

Am I ok renaming the new "check_apache_status" file before uploading it? In order to stop a conflict?

Otherwise, just to verify that windows apache and linux are not different, can you send us the top output from the server status page that looks like below:

http://192.168.19.136/server-status

Current Time: Wednesday, 06-Mar-2013 13:44:10 CST
Restart Time: Sunday, 03-Mar-2013 03:31:04 CST
Parent Server Generation: 1
Server uptime: 3 days 10 hours 13 minutes 5 seconds
Total accesses: 65919 - Total Traffic: 87.8 MB
CPU Usage: u1999.68 s146.16 cu1.59 cs0 - .726% CPU load
.223 requests/sec - 310 B/second - 1395 B/request
1 requests currently being processed, 11 idle workers

sreinhardt wrote:Otherwise, just to verify that windows apache and linux are not different, can you send us the top output from the server status page that looks like below:

http://192.168.19.136/server-status

Current Time: Wednesday, 06-Mar-2013 13:44:10 CST
Restart Time: Sunday, 03-Mar-2013 03:31:04 CST
Parent Server Generation: 1
Server uptime: 3 days 10 hours 13 minutes 5 seconds
Total accesses: 65919 - Total Traffic: 87.8 MB
CPU Usage: u1999.68 s146.16 cu1.59 cs0 - .726% CPU load
.223 requests/sec - 310 B/second - 1395 B/request
1 requests currently being processed, 11 idle workers

Current Time: Wednesday, 06-Mar-2013 20:54:44 GMT Standard Time
Restart Time: Wednesday, 06-Mar-2013 20:14:00 GMT Standard Time
Parent Server Generation: 0
Server uptime: 40 minutes 44 seconds
Total accesses: 453 - Total Traffic: 664 kB
.185 requests/sec - 278 B/second - 1500 B/request
1 requests currently being processed, 63 idle workers

abrist wrote:Funny thing is, the requests check is still working, is it not? That means the plugin is working fine, it is just the traffic portion is not parsing the status page information correctly. Maybe download the plugin again and run a diff between that and your current plugin to make sure you don't have a larger issue(corruption etc).

Installed "check_apache_status" as "check_apache_traffic" and set it up to monitor traffic. Still receive the same error.

I believe that is our answer right there, the script per line 169 is specifically looking for MB at the end of the line. I would believe this regex will fail for kB per your current output.

Total accesses: 453 - Total Traffic: 664 kB

Maybe host a few image files and download them so that you can get that status up. While I can't agree with the way this was written, I can understand as very few if any apache servers would be expected to only have kB.

sreinhardt wrote:I believe that is our answer right there, the script per line 169 is specifically looking for MB at the end of the line. I would believe this regex will fail for kB per your current output.

Total accesses: 453 - Total Traffic: 664 kB

Maybe host a few image files and download them so that you can get that status up. While I can't agree with the way this was written, I can understand as very few if any apache servers would be expected to only have kB.

Yeah I agree that a serer would never really receive such a small ammount of traffic.

One user has commented on the "check_apache_status" page with "I fix the problem with measure in KB, MB and GB from traffic.".

Would this edited script resolve my issue? I cant quite make sense of what he's said.

Ok so I tried the users new script and my error is now
SO i think the new script has rsolved the kB/MB issue