Plug-In check_apache_status, traffic
Re: Plug-In check_apache_status, traffic
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 . . . .
This smells like an apache problem . . . .
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: Plug-In check_apache_status, traffic
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.
So the servers have had no connection to the internet in order to update.
Re: Plug-In check_apache_status, traffic
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).
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: Plug-In check_apache_status, traffic
Correct, Number of requests is still working.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).
Am I ok renaming the new "check_apache_status" file before uploading it? In order to stop a conflict?
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: Plug-In check_apache_status, traffic
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
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
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: Plug-In check_apache_status, traffic
Current Time: Wednesday, 06-Mar-2013 20:54:44 GMT Standard Timesreinhardt 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
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
Re: Plug-In check_apache_status, traffic
Installed "check_apache_status" as "check_apache_traffic" and set it up to monitor traffic. Still receive the same error.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).
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: Plug-In check_apache_status, traffic
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.
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.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: Plug-In check_apache_status, traffic
Yeah I agree that a serer would never really receive such a small ammount of traffic.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.
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.
Re: Plug-In check_apache_status, traffic
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
Code: Select all
(Return code of 126 is out of bounds - plugin may not be executable)