V5.3.0 - Scheduled Downtime - records dont appear?
V5.3.0 - Scheduled Downtime - records dont appear?
Hi
I'm trying to enter scheduled downtime for our customers network - in 2.5.3 it seems that I can schedule downtime for several hosts and their services all in one go - great! - except when I do that and enter it, no downtime records appear. The system says they have been created but they never appear - is this a bug?
Thanks
I'm trying to enter scheduled downtime for our customers network - in 2.5.3 it seems that I can schedule downtime for several hosts and their services all in one go - great! - except when I do that and enter it, no downtime records appear. The system says they have been created but they never appear - is this a bug?
Thanks
Last edited by srhart on Thu Oct 06, 2016 10:41 am, edited 1 time in total.
Re: V2.5.3 - Scheduled Downtime - records dont appear?
Can you please clarify the version? Do you mean 5.2.3? If so, the latest version is 5.3.0 - you might want to try upgrading and see if the issue persists:
https://assets.nagios.com/downloads/nag ... nstall.pdf
https://assets.nagios.com/downloads/nag ... nstall.pdf
Former Nagios employee
Re: V5.3.0 - Scheduled Downtime - records dont appear?
Apologies, it IS 5.3.0 that I'm having the problem with - don't know why that other version popped out of my head.
Re: V5.3.0 - Scheduled Downtime - records dont appear?
You can schedule downtime for several hosts in one go AND/OR schedule downtime for several services on one host in one go, but not both as far as I know... Can you describe in details all of the steps you took to schedule downtime for these hosts/services? Show some screenshots.... it seems that I can schedule downtime for several hosts and their services all in one go - great! - except when I do that and enter it, no downtime records appear.
What is the date format that you are using, i.e. DD/MM/YYYY? Are you scheduling downtime logged in as "nagiosadmin" or another user? Is it an admin or a "regular", AD/LDAP or "local" user?
What is the output of the following commands?
Code: Select all
locale
uname -a
cat /etc/*release
tail -100 /var/log/httpd/error_log
Be sure to check out our Knowledgebase for helpful articles and solutions!
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: V5.3.0 - Scheduled Downtime - records dont appear?
I'm seeing the same thing. This is how the downtime was scheduled:
And it doesn't show up when I view the scheduled downtime page. This was scheduled by a non admin user with the following permissions:
You do not have the required permissions to view the files attached to this post.
Re: V5.3.0 - Scheduled Downtime - records dont appear?
What do you see when you run the following command?
Can you make sure that your filter is set to "none" (all options cleared)? See below:
If host is scheduled in downtime along with its services, it will not show up when you use the "Host" only filter. Only "individual" hosts, scheduled in downtime will show up.
Code: Select all
grep -i 'service has entered\|host has entered' /usr/local/nagios/var/nagios.logIf host is scheduled in downtime along with its services, it will not show up when you use the "Host" only filter. Only "individual" hosts, scheduled in downtime will show up.
You do not have the required permissions to view the files attached to this post.
Be sure to check out our Knowledgebase for helpful articles and solutions!
- snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: V5.3.0 - Scheduled Downtime - records dont appear?
None of those hosts are showing in that log, and the downtime wasn't actually scheduled apparently as alerts went out for all of the hosts that were in maintenance.
Re: V5.3.0 - Scheduled Downtime - records dont appear?
Can you post a tail of the apache error log?
Code: Select all
tail -100 /var/log/httpd/error_logBe sure to check out our Knowledgebase for helpful articles and solutions!
Re: V5.3.0 - Scheduled Downtime - records dont appear?
Code: Select all
[Sun Oct 02 03:45:04.716653 2016] [auth_digest:notice] [pid 1285] AH01757: generating secret for digest authentication ...
[Sun Oct 02 03:45:04.742192 2016] [lbmethod_heartbeat:notice] [pid 1285] AH02282: No slotmem from mod_heartmonitor
[Sun Oct 02 03:45:04.809529 2016] [mpm_prefork:notice] [pid 1285] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16 configured -- resuming normal operations
[Sun Oct 02 03:45:04.809547 2016] [core:notice] [pid 1285] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Mon Oct 03 16:34:07.744695 2016] [core:error] [pid 25706] [client 208.64.253.251:58942] AH00126: Invalid URI in request GET HTTP/1.1 HTTP/1.1
[Thu Oct 06 09:54:37.210722 2016] [suexec:notice] [pid 1226] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using icnms.l3n-nms.co.uk. Set the 'ServerName' directive globally to suppress this message
[Thu Oct 06 09:54:37.253028 2016] [auth_digest:notice] [pid 1226] AH01757: generating secret for digest authentication ...
[Thu Oct 06 09:54:37.253562 2016] [lbmethod_heartbeat:notice] [pid 1226] AH02282: No slotmem from mod_heartmonitor
[Thu Oct 06 09:54:38.522102 2016] [mpm_prefork:notice] [pid 1226] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16 configured -- resuming normal operations
[Thu Oct 06 09:54:38.522128 2016] [core:notice] [pid 1226] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Thu Oct 06 09:59:36.689737 2016] [mpm_prefork:notice] [pid 1226] AH00170: caught SIGWINCH, shutting down gracefully
[Thu Oct 06 09:59:38.048021 2016] [suexec:notice] [pid 6554] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using icnms.l3n-nms.co.uk. Set the 'ServerName' directive globally to suppress this message
[Thu Oct 06 09:59:38.070263 2016] [auth_digest:notice] [pid 6554] AH01757: generating secret for digest authentication ...
[Thu Oct 06 09:59:38.070715 2016] [lbmethod_heartbeat:notice] [pid 6554] AH02282: No slotmem from mod_heartmonitor
[Thu Oct 06 09:59:38.110968 2016] [mpm_prefork:notice] [pid 6554] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16 configured -- resuming normal operations
[Thu Oct 06 09:59:38.110989 2016] [core:notice] [pid 6554] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Thu Oct 06 10:21:19.151318 2016] [mpm_prefork:notice] [pid 6554] AH00170: caught SIGWINCH, shutting down gracefully
[Thu Oct 06 10:21:45.327379 2016] [suexec:notice] [pid 1255] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using icnms.l3n-nms.co.uk. Set the 'ServerName' directive globally to suppress this message
[Thu Oct 06 10:21:45.361327 2016] [auth_digest:notice] [pid 1255] AH01757: generating secret for digest authentication ...
[Thu Oct 06 10:21:45.361868 2016] [lbmethod_heartbeat:notice] [pid 1255] AH02282: No slotmem from mod_heartmonitor
[Thu Oct 06 10:21:46.620322 2016] [mpm_prefork:notice] [pid 1255] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16 configured -- resuming normal operations
[Thu Oct 06 10:21:46.620348 2016] [core:notice] [pid 1255] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'Re: V5.3.0 - Scheduled Downtime - records dont appear?
Doesn't look like it's erroring out - it sends the downtime scheduling through core. What times were you scheduling them for?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.