Search found 10 matches
- Fri Aug 10, 2018 3:55 am
- Forum: Nagios XI
- Topic: Global Event Handler Continuing to alert on service down
- Replies: 8
- Views: 292
Re: Global Event Handler Continuing to alert on service down
I believe I found the cause in Core and is fixed in the maint branch on Github https://github.com/NagiosEnterprises/nagioscore/tree/maint wget https://github.com/NagiosEnterprises/nagioscore/archive/maint.tar.gz tar xzf maint.tar.gz cd nagioscore-maint configureflags="--with-command-group...
- Mon Aug 06, 2018 5:39 am
- Forum: Nagios XI
- Topic: Global Event Handler Continuing to alert on service down
- Replies: 8
- Views: 292
Re: Global Event Handler Continuing to alert on service down
I've tried the latest maint patch again. Still no joy.
I think I can see the issue though. After 5 or 5 checks, the state is still set to soft, it doesn't seem to get set to hard
I think I can see the issue though. After 5 or 5 checks, the state is still set to soft, it doesn't seem to get set to hard
- Fri Aug 03, 2018 2:33 am
- Forum: Nagios XI
- Topic: Global Event Handler Continuing to alert on service down
- Replies: 8
- Views: 292
Re: Global Event Handler Continuing to alert on service down
I have compiled and installed the maint branch with no joy. I think the issue I am seeing is different. The service is not failing to stop notifying when it returns to an OK state. The issue is that it keeps notifying, despite reaching the Max Checks of 5 Out global event handler calls this for serv...
- Tue Jul 31, 2018 8:00 am
- Forum: Nagios XI
- Topic: Global Event Handler Continuing to alert on service down
- Replies: 8
- Views: 292
Global Event Handler Continuing to alert on service down
Since upgrading to NagiosXI 5.5.2, we are seeing some strange things. We use the Global Event Handlers to send HOST and SERVICE changes to a script that interfaces with an in-house alerting system. This has been working fine for ages. Since upgrading, when a node goes down, we receive an alert for t...
- Mon Dec 14, 2015 4:05 am
- Forum: Nagios XI
- Topic: Auto Discovery Issue in 5.2.3
- Replies: 4
- Views: 182
Re: Auto Discovery Issue in 5.2.3
Ignore that. I just created a new auto discovery job and the files are indeed owned by apache. I can only assume that the wizard used to create the files as nagios:nagios.
I will change the owner to apache and change the permissions back to 644
Regards
Kev
I will change the owner to apache and change the permissions back to 644
Regards
Kev
- Mon Dec 14, 2015 4:02 am
- Forum: Nagios XI
- Topic: Auto Discovery Issue in 5.2.3
- Replies: 4
- Views: 182
Re: Auto Discovery Issue in 5.2.3
Unfortunately this machine doesn't have internet access. The version of the autodiscovery component is 2.2.3
Regards
Kev
Regards
Kev
- Fri Dec 11, 2015 5:34 am
- Forum: Nagios XI
- Topic: Auto Discovery Issue in 5.2.3
- Replies: 4
- Views: 182
Auto Discovery Issue in 5.2.3
After installing NagiosXI 5.2.3, my autodiscovery jobs were not running. Either on their scheduled times or using the play icon on the job, from the autodiscovery wizard webpage. The problem appears to be a permissions issue. All the files in /usr/local/nagiosxi/html/includes/components/autodiscover...
- Wed Oct 28, 2015 6:24 am
- Forum: Nagios XI
- Topic: Auto Discovery Issue
- Replies: 4
- Views: 1074
Re: Auto Discovery Issue
Just upgraded nmap to latest version and now everything is working just fine.
Regards
Kevin
Regards
Kevin
- Wed Oct 28, 2015 6:01 am
- Forum: Nagios XI
- Topic: Auto Discovery Issue
- Replies: 4
- Views: 1074
Re: Auto Discovery Issue
Sorry for the delay
Auto-Discovery component is version 2.2.1
Auto-Discovery wizard is version 1.4.0
Nmap version is version 5.51
Auto-Discovery component is version 2.2.1
Auto-Discovery wizard is version 1.4.0
Nmap version is version 5.51
- Fri Oct 23, 2015 3:57 am
- Forum: Nagios XI
- Topic: Auto Discovery Issue
- Replies: 4
- Views: 1074
Auto Discovery Issue
OS : RHEL 6.5 X86_64 Nagios Version : Nagios 5.2.0 (Manual Install) The auto-discovery wizard is no longer detecting services when new hosts are discovered, if excluded IPs are used This is due to the nmap command having two -exclude options set Example Scanning range 192.168.1.0/24 and excluding th...