Nagios Support Forum

Hi, I am familiar with the guide, unfortunately I am not able to build the agent from source, my company has a policy that no build tools can be installed on qa, uat, prod, dr, etc so I have to use the packages in the repo. The agent is running as a stand alone daemon. the oddity is that only some o...

Hi, i am trying to roll out nrpe across our fleet of Linux servers. I am installing the packages from the EPEL repos (4.x, 5.x, 6.x, 7.x) on a few servers so far I have noticed different behavior when it comes to connecting, even locally with check_nrpe. On some of the servers, just installing nrpe ...

that does get the information from the log, but the issue as I posted before is that it only detects is own runs because every time it runs the check, the system logs the run to /var/log/secure (1) < Nov 16 11:12:09 vmlshbobj1d sudo: nagios : TTY=unknown : PWD=/ : USER=root : COMMAND=/usr/lib64/nagi...

Apologies, missed your response changed the sudoers file to: ... %monitoring ALL=(ALL) NOPASSWD: ALL ... nagios ALL=(root) /usr/lib64/nagios/plugins/check_log nagios groups groups nagios nagios : nagios monitoring still works on the server that uses systemd, still doesn't work with the same error on...

The other servers are running with init scripts and exhibiting the same behavior, Log check error: Log file /var/log/secure is not readable! example on a 5.11 Redhat server: the nrpe.cfg file specified the nagios user and it is running as the nagios user: nagios 30647 1 0 16:02 ? 00:00:00 /usr/sbin/...

good idea, its running as the nrpe user! nrpe 28399 1 0 10:03 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d this gave me an idea, this was installed from the EPEL repo, not from source. Maybe a little background would explain: I am rolling out nagios monitoring to the entire company, this box...

beat you to it ;) , but there is another error sudo: no tty present and no askpass program specified EDIT: updated command in nrpe.cfg to: command[diff_log]=sudo -n /usr/lib64/nagios/plugins/check_log -F $ARG1$ -O $ARG2$ -q $ARG3$ 2>&1 new error: sudo: a password is required in /var/log/secure I...

tried this anyway just to see and it failes with "NRPE: Unable to read output" nrpe.cfg snippet: command[diff_log]=sudo /usr/lib64/nagios/plugins/check_log -F $ARG1$ -O $ARG2$ -q $ARG3$ nagios is now in sudoers file Defaults:nagios !requiretty nagios ALL=NOPASSWD: /usr/lib64/nagios/plugins...

Hi yes I did see that thread however, in that case the nagios user was not able to locally run the check_log command without getting the same error. In my original post you can see, my shell is explicitly logged in as nagios the user and it is able to execute the command and return a result. [[b]nag...

difference is from calling nrpe and paramaterizing the input. You have to call -F -O and -q, so I don't want to put it in each service def

snippet of nrpe.cfg: