Thanks for you continued effort. I will try the things described in the FAQ. But most likely on Monday.scottwilkerson wrote:It is possible that this is the cause, the bug referenced in the link I sent will make the database (that the web page reads out of) update at an extremely slow pace...
check_http is stuck in pending.
Re: check_http is stuck in pending.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_http is stuck in pending.
let us know if this resolves the issue.
Re: check_http is stuck in pending.
Hi Scott,scottwilkerson wrote:let us know if this resolves the issue.
Unfortunatly, It did not resolve the issues. I verified the settings in the file, and they are exactly the same as they are in the FAQ. Even though the Nagios XI interface shows the service as pending. The notifications and alerts work perfectly fine in the background(Nagios Core?) in some weird way.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_http is stuck in pending.
The values are likely already updated but you need to run the following for the changes to take affect
From the wiki:
Code: Select all
sysctl -pAfter these settings are saved to the file, run:
To apply the new settings. If the system still appears to be working improperly, reboot the machine.Code: Select all
sysctl -p
Re: check_http is stuck in pending.
Did both those things. No dice.scottwilkerson wrote:The values are likely already updated but you need to run the following for the changes to take affectFrom the wiki:Code: Select all
sysctl -pAfter these settings are saved to the file, run:
To apply the new settings. If the system still appears to be working improperly, reboot the machine.Code: Select all
sysctl -p
Thanks.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_http is stuck in pending.
Can you tail the syslog to see if any errors are showing up
Also have a loog at the nagios log to see if any errors are showing up
Code: Select all
tail -f /var/log/messagesCode: Select all
tail -f /usr/local/nagios/var/nagios.logRe: check_http is stuck in pending.
Been monitoring both for a while, no errors what so ever. The interface does seem to live a life off its own. Adding the pending service to every host we have... Even though we did not configure it (weird behavior. I hope the next update will fix the issues)scottwilkerson wrote:Can you tail the syslog to see if any errors are showing upAlso have a loog at the nagios log to see if any errors are showing upCode: Select all
tail -f /var/log/messagesCode: Select all
tail -f /usr/local/nagios/var/nagios.log
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_http is stuck in pending.
Actually this seems like a configuration error, can you send your config snapshot to me via PM, and state the name of the service in question.s.dehaan wrote: Been monitoring both for a while, no errors what so ever. The interface does seem to live a life off its own. Adding the pending service to every host we have... Even though we did not configure it (weird behavior. I hope the next update will fix the issues)
Thanks.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: check_http is stuck in pending.
I have to ask, are the other services updating in the web interface normally?
Also, if you access the core interface, does the service show correct info
Also, if you access the core interface, does the service show correct info
Code: Select all
http://<NAGIOS_IP>/nagios/Re: check_http is stuck in pending.
Yes. All other services are updating perfectly except for when I create a new check_http service. That one then goes into pending mode as well.scottwilkerson wrote:I have to ask, are the other services updating in the web interface normally?
Also, if you access the core interface, does the service show correct infoCode: Select all
http://<NAGIOS_IP>/nagios/
When I go to the core interface everything, including the malfunctioning service, works perfectly.
Thanks