Is that the default? I thought that was controlled by "host_down_disable_service_checks", but I guess I mistakenly under the impression that was off by default.
Am I right in thinking then that setting this to "0" will start notifying?
Search found 13 matches
- Tue May 07, 2019 12:36 pm
- Forum: Open Source Nagios Projects
- Topic: [4.4.3] check stale, host crit, doesn't notify service crits
- Replies: 3
- Views: 927
- Tue May 07, 2019 12:25 pm
- Forum: Open Source Nagios Projects
- Topic: [4.4.3] check stale, host crit, doesn't notify service crits
- Replies: 3
- Views: 927
[4.4.3] check stale, host crit, doesn't notify service crits
I can't find what the missing piece is that is preventing ones like this to notify. Presenting all information on one host/check to simplify. This one is in hard critical, but current_notification_number=0 (along with last/next notification, etc). From my attempt to pore over all of this, I don't se...
- Fri May 03, 2019 1:43 pm
- Forum: Open Source Nagios Projects
- Topic: Old (3.5.1) nagios server sometimes not notifying
- Replies: 3
- Views: 879
Re: Old (3.5.1) nagios server sometimes not notifying
SMH, sorry. Looking at too many things, totally missed that. Thank you much!
- Fri May 03, 2019 12:42 pm
- Forum: Open Source Nagios Projects
- Topic: Old (3.5.1) nagios server sometimes not notifying
- Replies: 3
- Views: 879
Old (3.5.1) nagios server sometimes not notifying
Sorry in advance if being too verbose (just want to avoid a lot of back and forth asking for config/state/etc). Basically I have an old nagios server that we're trying to get people off of, but in the mean time trying to keep going. It works well for the most part but I have some services that seem ...
- Thu Jan 26, 2017 2:33 pm
- Forum: Open Source Nagios Projects
- Topic: Warning: Return code of 127 for check of service...
- Replies: 14
- Views: 6466
Re: Warning: Return code of 127 for check of service...
Just to close the loop, that was indeed the case.
Disabling enable_environment_macros worked to resolve the failing checks. And it looks like we have no checks that were relying on environment variables (which was as I expected).
Disabling enable_environment_macros worked to resolve the failing checks. And it looks like we have no checks that were relying on environment variables (which was as I expected).
- Wed Jan 25, 2017 8:46 pm
- Forum: Open Source Nagios Projects
- Topic: Warning: Return code of 127 for check of service...
- Replies: 14
- Views: 6466
Re: Warning: Return code of 127 for check of service...
I think I may have found the issue, though I ran out of time before validating a fix. I had missed that in the "define service" from objects.cache it did not list servicegroups. That is the key difference. It seems that between expanding hostgroups and servicegroups I was overloading the e...
- Wed Jan 25, 2017 3:57 pm
- Forum: Open Source Nagios Projects
- Topic: Warning: Return code of 127 for check of service...
- Replies: 14
- Views: 6466
Re: Warning: Return code of 127 for check of service...
I feel like I'm not being clear, and I think it is due to overload of logging. My working and failing services are on the same server. I will narrow the scope. Given exactly 1 Nagios instance. On exactly 1 client host. There are 2 services. They are exactly the same except service_description From t...
- Tue Jan 24, 2017 5:52 pm
- Forum: Open Source Nagios Projects
- Topic: Warning: Return code of 127 for check of service...
- Replies: 14
- Views: 6466
Re: Warning: Return code of 127 for check of service...
Here is the nrpe config you requested
Note that both the working and non-working service I configured to use the same check.
(Looking at that section of docs now)
Code: Select all
command[check_nrpe_alive]=/usr/lib/nagios/plugins/check_nrpe_alive.sh(Looking at that section of docs now)
- Tue Jan 24, 2017 4:30 pm
- Forum: Open Source Nagios Projects
- Topic: Warning: Return code of 127 for check of service...
- Replies: 14
- Views: 6466
Re: Warning: Return code of 127 for check of service...
The thing that is baffling is that from the debug logs in previous posts the Nagios host seems to be doing the EXACT same thing for both checks. Both debug logs were from the same Nagios host, just forcing a check of two different services against the same client in succession, no restarts or anythi...
- Tue Jan 24, 2017 4:25 pm
- Forum: Open Source Nagios Projects
- Topic: Warning: Return code of 127 for check of service...
- Replies: 14
- Views: 6466
Re: Warning: Return code of 127 for check of service...
OK, please don't laugh. I inherited this, and the modern nagios host I have built are CentOS 7 with 4.1.1 on them. However the one causing me problems is: ~$ cat /etc/*-release CentOS release 5.6 (Final) ~$ We are running 3.5.0 on the older generation. We have ~10 nagios hosts due to inherited archi...