Nagios Support Forum

Manage to resolve it by removing all the existing configuration and manually deleting the 550.cfg file in the server. Readded back server and tested again, notification is being sent out. Possible human error during the deployment for specific services.

Hi, below is the requested output Is nagios.cmd being created as a pipe? Run the following command and show the output: CODE: SELECT ALL ls -la /usr/local/nagios/var/rw/nagios.cmd root@hk1pnag1[~] # ls -la /usr/local/nagios/var/rw/nagios.cmd prw-rw---- 1 nagios nagcmd 0 Jan 30 04:07 /usr/local/nagio...

Hi Support Team, We have setup a template in our Nagios XI for predefined default monitoring, and servers will be added under the template. All the inteval, notification are already tied to the template. For any newly added server, we just have to include in the existing Host Group, and the host gro...

Hi Team, Lately we have been facing issue where we keep getting this error when our L1 team tries to set scheduled downtime and applying the configuration from Nagios XI console. As workaround, we have run reset_config_perms.sh and reconfigure_nagios.sh as temporary workaround when issue happen. But...