Hello,
I have recently upgraded to 5.5. and have some weird behaviour. If I disable a service or a host in CCM, nagios is still performing checks for that service/server. It happens even if I delete the service/server from CCM. Nagios still does the checks.
I have tried to:
1. set server to active=no in CCM
2. apply config
3. poweroff server
4. still getting notifications about host down.
Tired the same on single service, still happens.
Best reagards,
Denis
Nagios 5.5 problem
Re: Nagios 5.5 problem
What is the name of the "problem" service/host? Can you show us the actual email notification that you received about your host being down? We will need to look into your configs and logs, so please PM me your profile.
Admin > System Profile > Download Profile
Admin > System Profile > Download Profile
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Nagios 5.5 problem
I'm unable to send you a PM. I have: "We are sorry, but you are not authorised to use this feature. You may have just registered here and may need to participate more to be able to use this feature."
The actual mail alert is this:
***** Nagios XI Alert *****
Nagios has detected a problem with this service.
Notification Type: PROBLEM
Service: ArchiveWorker Daemon
Host: syd-arch-prod-01
Address: 172.17.39.133
State: CRITICAL
Info:
*** archiveworker: Nok ***
Date/Time: 2018-07-09 05:23:52
The actual mail alert is this:
***** Nagios XI Alert *****
Nagios has detected a problem with this service.
Notification Type: PROBLEM
Service: ArchiveWorker Daemon
Host: syd-arch-prod-01
Address: 172.17.39.133
State: CRITICAL
Info:
*** archiveworker: Nok ***
Date/Time: 2018-07-09 05:23:52
Last edited by denisd on Mon Jul 09, 2018 8:14 am, edited 1 time in total.
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Nagios 5.5 problem
please post the output of
Code: Select all
ps -ef|grep nagios.cfgRe: Nagios 5.5 problem
ps -ef|grep nagios.cfg
Code: Select all
root 17372 21784 0 13:13 pts/0 00:00:00 grep nagios.cfg
nagios 21409 1 0 Jul03 ? 00:14:13 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios 21429 21409 0 Jul03 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios 25265 1 0 05:58 ? 00:00:42 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios 25283 25265 0 05:58 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Nagios 5.5 problem
Ok, there's the problen, run the following
That should resolve the issue
Code: Select all
service nagios stop
killall -9 nagios
service nagios startRe: Nagios 5.5 problem
Worked like a charm, thank you.
Re: Nagios 5.5 problem
Excellent! Did you have further (related) questions or are we good to lock this up?
Former Nagios employee
Re: Nagios 5.5 problem
All good for now, lock it up.