It is hard to say why Nagios didn't send notifications after the fact. I would recommend that you go through all steps, outline in the DB article below:Regarding "JCA WAN IP" might be there is nothing wrong in configuration. This is our WAN IP and last week due to some reason there was lots of packet lost for 2/3 days on this IP but Nagios did not sent any notification to us whereas there was notification setup for this. That's why I am confused why it did not send any notification, it should send us notification if there are lots of packet lost in any IP.
https://support.nagios.com/kb/article/n ... ms-36.html
You can also enable phpmailer debugging in order to further troubleshoot the issue:
https://support.nagios.com/kb/article/p ... g-820.html
If this happens again, take a screenshot of the State History report, showing the "problem" host/service in a HARD Non-OK state, and a screenshot of the Notifications report for the same timeperiod.
When you added the Ping service, you used a different config name (Ping_155_113 instead of 192.168.155.113), which is not an issue per se, but a service definition, located in the host directory is.I did not add anything from command line. Regarding 192.168.155.113 can you remember when we added this agent first time Nagios did not discover the ping service for this agent and later we added it manually "Ping_155_113" for ping service. Might be this is the reason you see it same configuration in two locations.
Let's try to remove the these objects, and re-add them via a wizard.
1. Go to the CCM > Services, find the Ping_155_113 service, and delete it.
2. Go to the CCM > Host, find the 192.168.155.113 host, and delete it.
3. Apply Configuration
4. If you don't have any config errors, proceed with running the Generic Network Device wizard against 192.168.155.113
Configure > Configuration Wizards > Generic Network Device > 192.168.155.113 > Next > Leave the Ping check-box selected (don't clear it!) > Next > Next > Next > Finish
Note: You can modify any of the "default" values in steps 3 through 5 if needed.
5. Check the newly created host & service in the GUI. Make sure it works as expected.