Nagios Support Forum

Hello Team,

In our environment we have enabled auto ticket in nagios and also its working fine but for one of the windows server we have scheduled the server from 2018-10-01 16:00:00 to 2018-10-05 15:30:00 so in a particular time there was a alert triggered for one of the service post which auto ticket created but still it is scheduled down time and still downtime not yet ended for the host, so kindly look in to this and provide your assistance. PFA SS

Nagios version: Nagios XI 5.4.12
OS: Red Hat Enterprise Linux Server release 7.1 (Maipo)

Check settings for Y Drive 5,1,5
host check settings 3,1,3

Hello,

If it had been working correctly, it's possible there are multiple Nagios processes running. You can stop all the processes and restart the system with the following:
If that does not resolve the issue, please send over a System Profile so we can review it.

To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and upload it to a cloud storage of your choice. You can share a link with me in a personal message.
After you upload the profile please post something in this thread to bring it up in the support queue.

Thank you.

benjaminsmith wrote:Hello,

If it had been working correctly, it's possible there are multiple Nagios processes running. You can stop all the processes and restart the system with the following:

Code: Select all

service nagios stop
killall -9 nagios
service nagios start

If that does not resolve the issue, please send over a System Profile so we can review it.

To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and upload it to a cloud storage of your choice. You can share a link with me in a personal message.
After you upload the profile please post something in this thread to bring it up in the support queue.

Thank you.

Hi Benjaminsmith,

I have attached the System Profile.

When we check the Nagios processes is running fine so we didn't killed the process, PFB info

[root@xxxxxxxx ~]# ps -ef | head -1 && ps -ef | grep bin/nagios
UID PID PPID C STIME TTY TIME CMD
root 813 23305 0 14:43 pts/0 00:00:00 grep --color=auto bin/nagios
nagios 16277 1 5 12:16 ? 00:07:38 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios 16279 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16280 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16281 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16282 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16284 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16285 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16286 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16287 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16288 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16289 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16290 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16291 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16292 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16293 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16294 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16295 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16296 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16297 16277 0 12:16 ? 00:00:08 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios 16681 16277 0 12:17 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

[root@xxxxxxxxxx ~]# ps -ef |grep -i nagios.cfg
root 5413 23305 0 14:44 pts/0 00:00:00 grep --color=auto -i nagios.cfg
nagios 16277 1 5 12:16 ? 00:07:38 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios 16681 16277 0 12:17 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

I have attached the System Profile.

Did you PM the profile.zip to anyone on the Nagios Support team? We haven't received it yet.

Run the following command and show the output: We need to see what is the version of Nagios Core that you are currently running.

Update. Thank you for sending over your profile. We're reviewing it right now.

Your running a larger system, what host is this service for (Disk Y: Drive Usage). That will help us locate it in the configs.

lmiltchev wrote:

I have attached the System Profile.

Did you PM the profile.zip to anyone on the Nagios Support team? We haven't received it yet.

Run the following command and show the output:

Code: Select all

/usr/local/nagios/bin/nagios

We need to see what is the version of Nagios Core that you are currently running.

Hi Lmiltchev,
PFB command output for Nagios Core version.
[root@xxxxxxxxx ~]# /usr/local/nagios/bin/nagios

Nagios Core 4.2.4
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 12-07-2016
License: GPL

Website: https://www.nagios.org
Usage: /usr/local/nagios/bin/nagios [options] <main_config_file>

Options:

-v, --verify-config Verify all configuration data (-v -v for more info)
-s, --test-scheduling Shows projected/recommended check scheduling and other
diagnostic info based on the current configuration files.
-T, --enable-timing-point Enable timed commentary on initialization
-x, --dont-verify-paths Deprecated (Don't check for circular object paths)
-p, --precache-objects Precache object configuration
-u, --use-precached-objects Use precached object config file
-d, --daemon Starts Nagios in daemon mode, instead of as a foreground process
-W, --worker /path/to/socket Act as a worker for an already running daemon

Visit the Nagios website at https://www.nagios.org/ for bug fixes, new
releases, online documentation, FAQs, information on subscribing to
the mailing lists, and commercial support options for Nagios.

vignesha wrote:In our environment we have enabled auto ticket in nagios and also its working fine but for one of the windows server we have scheduled the server from 2018-10-01 16:00:00 to 2018-10-05 15:30:00 so in a particular time there was a alert triggered for one of the service post which auto ticket created but still it is scheduled down time and still downtime not yet ended for the host, so kindly look in to this and provide your assistance. PFA SS

What are you using the create auto tickets?

In the image you provided, I see a downtime notification on 10/1 before even the listed scheduled downtime.
Additionally you show the state history showing a state on 10/3, however if a service is in downtime that doesn't prevent the State history report from showing the current states, it only suppresses notifications.