Recurring Downtime

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
jkinning
Posts: 747
Joined: Wed Oct 09, 2013 2:54 pm

Recurring Downtime

Post by jkinning »

I setup recurring downtime to reflect our different maintenance windows so users wouldn't need to worry bout disabling notifications. This worked out well during the Server maintenance we had last weekend. But, I noticed today that these hosts are showing downtime again for next weekend but shouldn't.

First image is my schedule and the second is from a non-production hosts. We have maintenance every third Sunday which was yesterday so I don't understand why this is saying 7-26 is scheduled too.
You do not have the required permissions to view the files attached to this post.
Top
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Recurring Downtime

Post by lmiltchev »

If this is not a bug, the only reasonable explanation would be that you (or somebody else, who used your login) scheduled a regular (non-recurring) downtime for 07/26/2015... Can you click on both links - "Scheduled Downtime" and "Recurring Downtime" under "Home", and show us screenshots of both pages?
Be sure to check out our Knowledgebase for helpful articles and solutions!
Top
jkinning
Posts: 747
Joined: Wed Oct 09, 2013 2:54 pm

Re: Recurring Downtime

Post by jkinning »

There is too much information for a simple screenshot so I can capture all the information for the Scheduled Downtime link. The Recurring Downtime I included again. I also tried to copy and paste but everything is not allowed, PDF, DOCX. So I tried to zip it and the file is too large - The file is too big, maximum allowed size is 1 MiB.

Here it top portion of the Scheduled Downtime.
You do not have the required permissions to view the files attached to this post.
Top
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Recurring Downtime

Post by lmiltchev »

What is the name of the "problem" host? You have many hosts scheduled for downtime on 26th. Are they members of the "win_nonprod_hg" hostgroup only or they are also members of the "mainframe_hg"?

Do you have any errors in the mysqld.log?

Code: Select all

tail -100 /var/log/mysqld.log
Is opening a ticket in our email ticketing system is an option for you?
Be sure to check out our Knowledgebase for helpful articles and solutions!
Top
jkinning
Posts: 747
Joined: Wed Oct 09, 2013 2:54 pm

Re: Recurring Downtime

Post by jkinning »

Code: Select all

tail -100 /var/log/mysqld.log 
140807  4:49:54 [Note] /usr/libexec/mysqld: Shutdown complete

140807 04:49:54 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140807 04:50:56 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140807  4:50:56  InnoDB: Initializing buffer pool, size = 8.0M
140807  4:50:56  InnoDB: Completed initialization of buffer pool
140807  4:50:57  InnoDB: Started; log sequence number 0 44233
140807  4:50:57 [Note] Event Scheduler: Loaded 0 events
140807  4:50:57 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
141125 10:42:22 [Note] /usr/libexec/mysqld: Normal shutdown

141125 10:42:22 [Note] Event Scheduler: Purging the queue. 0 events
141125 10:42:24  InnoDB: Starting shutdown...
141125 10:42:28  InnoDB: Shutdown completed; log sequence number 0 44233
141125 10:42:28 [Note] /usr/libexec/mysqld: Shutdown complete

141125 10:42:28 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
141125 10:43:29 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141125 10:43:32  InnoDB: Initializing buffer pool, size = 8.0M
141125 10:43:32  InnoDB: Completed initialization of buffer pool
141125 10:43:37  InnoDB: Started; log sequence number 0 44233
141125 10:43:37 [Note] Event Scheduler: Loaded 0 events
141125 10:43:37 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
141212  8:59:44 [Note] /usr/libexec/mysqld: Normal shutdown

141212  8:59:44 [Note] Event Scheduler: Purging the queue. 0 events
141212  8:59:46  InnoDB: Starting shutdown...
141212  8:59:47  InnoDB: Shutdown completed; log sequence number 0 44233
141212  8:59:47 [Note] /usr/libexec/mysqld: Shutdown complete

141212 08:59:47 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
141212 09:00:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
141212  9:00:47  InnoDB: Initializing buffer pool, size = 8.0M
141212  9:00:47  InnoDB: Completed initialization of buffer pool
141212  9:00:47  InnoDB: Started; log sequence number 0 44233
141212  9:00:47 [Note] Event Scheduler: Loaded 0 events
141212  9:00:47 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
150102 10:16:58 [Note] /usr/libexec/mysqld: Normal shutdown

150102 10:16:58 [Note] Event Scheduler: Purging the queue. 0 events
150102 10:17:00  InnoDB: Starting shutdown...
150102 10:17:05  InnoDB: Shutdown completed; log sequence number 0 44233
150102 10:17:05 [Note] /usr/libexec/mysqld: Shutdown complete

150102 10:17:05 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150102 10:18:04 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150102 10:18:05  InnoDB: Initializing buffer pool, size = 8.0M
150102 10:18:05  InnoDB: Completed initialization of buffer pool
150102 10:18:05  InnoDB: Started; log sequence number 0 44233
150102 10:18:05 [Note] Event Scheduler: Loaded 0 events
150102 10:18:05 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
150130  9:25:12 [Note] /usr/libexec/mysqld: Normal shutdown

150130  9:25:12 [Note] Event Scheduler: Purging the queue. 0 events
150130  9:25:14  InnoDB: Starting shutdown...
150130  9:25:19  InnoDB: Shutdown completed; log sequence number 0 44233
150130  9:25:19 [Note] /usr/libexec/mysqld: Shutdown complete

150130 09:25:19 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150130 09:26:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150130  9:26:19  InnoDB: Initializing buffer pool, size = 8.0M
150130  9:26:19  InnoDB: Completed initialization of buffer pool
150130  9:26:19  InnoDB: Started; log sequence number 0 44233
150130  9:26:19 [Note] Event Scheduler: Loaded 0 events
150130  9:26:19 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
150402 12:59:38 [Note] /usr/libexec/mysqld: Normal shutdown

150402 12:59:38 [Note] Event Scheduler: Purging the queue. 0 events
150402 12:59:40  InnoDB: Starting shutdown...
150402 12:59:42  InnoDB: Shutdown completed; log sequence number 0 44233
150402 12:59:42 [Note] /usr/libexec/mysqld: Shutdown complete

150402 12:59:42 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150402 13:00:22 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150402 13:00:23  InnoDB: Initializing buffer pool, size = 8.0M
150402 13:00:23  InnoDB: Completed initialization of buffer pool
150402 13:00:23  InnoDB: Started; log sequence number 0 44233
150402 13:00:23 [Note] Event Scheduler: Loaded 0 events
150402 13:00:23 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
150402 13:06:15 [Note] /usr/libexec/mysqld: Normal shutdown

150402 13:06:15 [Note] Event Scheduler: Purging the queue. 0 events
150402 13:06:17  InnoDB: Starting shutdown...
150402 13:06:19  InnoDB: Shutdown completed; log sequence number 0 44233
150402 13:06:19 [Note] /usr/libexec/mysqld: Shutdown complete

150402 13:06:19 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
150402 13:08:41 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150402 13:08:41  InnoDB: Initializing buffer pool, size = 8.0M
150402 13:08:41  InnoDB: Completed initialization of buffer pool
150402 13:08:42  InnoDB: Started; log sequence number 0 44233
150402 13:08:42 [Note] Event Scheduler: Loaded 0 events
150402 13:08:42 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution
There are two groups: win_prod_hg and win_nonprod_hg which are the 3rd Sunday of each month just different times. My problem is they shouldn't be scheduled for downtime on the 26th, it should have been last Sunday the 20th which worked but I noticed they all are scheduled for this Sunday as well and should be.

I am open to opening a ticket in your email system? How or what do I need to do?
Top
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Recurring Downtime

Post by lmiltchev »

I am open to opening a ticket in your email system? How or what do I need to do?
Go to Admin->System Profile->Download Profile, save and email "profile.zip" to [email protected]. Type "Recurring Downtime" in the email's subject field, and paste a link to this forum post in the email's body. Thanks!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Top
jkinning
Posts: 747
Joined: Wed Oct 09, 2013 2:54 pm

Re: Recurring Downtime

Post by jkinning »

In route...
Top
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: Recurring Downtime

Post by tmcdonald »

Locking the thread for now, handling this in the ticket.
Former Nagios employee
Top
Locked

Return to “Nagios XI”