Nagios Support Forum

We are experiencing an issue where an email contact we have setup is receiving 'ok' or 'up' status notifications, but we not receiving 'down' status alerts. I assume we have misconfigured the settings, but not sure how to resolve this. Attached is a screenshot of the alert settings for this contact....

Success!!! Not sure why, but removing 'sudo' from the command in nrpe.cfg resolved the issue.

Locally I need to use sudo from a non-root user to get a correct response.

Update: I tried substituting the exact syntax for the parameter $ARG1$ in the check_init_service command in nrpe.cfg.... command[check_init_service]=sudo /usr/lib64/nagios/plugins/check_init_service crond Then forcing a check in the Nagiosxi gui. Unfortunately, I get the same error. I also recreated...

but is it possible that you have the same command defined twice? Do you have a file called "common.cfg". If you used our "official" Linux agent installer, you should have it. Thanks, the install was performed using the package manager (Yum) as the linux-agent installer does not ...

Yes, blame is set to '1' in nrpe.cfg, and the permissions plugin permission is root:root 755, which matches the other plugins that are running successfully. The command is prefaced with 'sudo' in nrpe.cfg, and I'm logged in as ec2-user when run locally but use 'sudo'- ex. 'sudo ./check_init_service ...

Thanks, I was able to resolve it for most services but am getting warning + NRPE: Unable to read output errors for the 'check_init_service' check we use for crod (crond) and ssh (sshd). This error only happens when the command is run from the nagiosxi server. The command is successful when run local...

We are experiencing the case where nrpe installs (using either Ubuntu based or Amazon Linux) fail to report correctly. The installs themselves on the clients are successful, the nrpe has the allowed host set correctly, and the plugin directory is present. The errors we see in the NagiosXi server for...