I was wondering if I could get another set of eyes on this.

/usr/lib/nagios/plugins/check_procs -w 1:3 -c 1:3 -u root -C
systemd-udevd -a '/lib/systemd/systemd-udevd'
PROCS CRITICAL: 0 processes with UID = 0 (root), command name 'systemd-udevd',
args '/lib/systemd/systemd-udevd' | procs=0;1:3;1:3;0;
[status 2]

Here is what is actually running:

~$ ps aux|egrep 'rsyslogd|udevd'
root 385 0.0 0.0 41308 3224 ? Ss Apr01 0:00 udevd --daemon
root 2477 0.0 0.0 258672 3128 ? Ssl Apr01 0:06 /usr/sbin/rsyslogd

With the "-C" you're telling it to look for process command "systemd-udevd".

It correctly tells you that no such command exists. Your ps aux output confirms that as it also doesn't list "systemd-udevd".

You'd either need to test "-C" for what you do see which is only "udevd" and its argument "--daemon":
-OR-
If systemd-udevd is supposed to be running, figure out why it isn't.

I don't have Debian but I do see on my RHEL7 server it is running systemd-udevd but doesn't have the arguments you specified:
root 588 0.0 0.0 44572 2312 ? Ss Jan19 0:00 /usr/lib/systemd/systemd-udevd

However, on a RHEL6 system I instead see:
root 6151 1 0 2017 ? 00:00:24 /sbin/udevd -d
root 10034 6151 0 04:46 ? 00:00:00 /sbin/udevd -d
root 10037 6151 0 04:46 ? 00:00:00 /sbin/udevd -d

For RHEL systemd was introduced in RHEL7. I suspect your Debian version is one that doesn't have systemd so "udevd --daemon" is appropriate for it.

1 members found this post helpful.

Thank you for the reply.

This is a Debian 8 server that is having the errors. I ran the same commands on another one of their Debian 8 servers, and they worked. We have a combination of Debian 7,8, and 9 running. It seems that the other Debian 8 machines running these same services work fine. The server giving this error happens to be a server that I don't have ssh access. Maybe they can grant me access so I can have a local look at the server. In any event, I will post a fix, if it should come, and I will close the thread.


Thanks,
Ron

If you don't have shell access how did you confirm it is Debian 8? Is it possible the admins told you the wrong version for this particular system? Also how did you run "ps aux" without shell access?

By the way my post didn't say it SHOULDN'T be running systemd-udevd. It said it ISN'T running systemd-udevd. Your ps aux output confirmed it ISN'T running systemd-udevd so the check_procs syntax that listed it as CRITICAL was correct.

After saying you could modify check_procs to monitor just the "udevd" that IS running (based on your ps aux output) I did say:

The point in check_procs is report on processes that should be running. It will of course give errors if not as many (and/or not as few) processes you defined are running. This is the case on your system - systemd-udevd ISN'T running.

I handle the Nagios server. I have access to a lot of others, but not this particular one. I was sent an email with the ps aux information in it, asking my why the monitoring is not working. We've been having our fair share of issues with Nagios given that we are monitoring very few systemd. There seems to be a bit of a learning curve switching between these. I'll email him back telling him that the service on that machine is not running, and it is not a Nagios issue. He will have to look at it on his own. Thanks again. I'll mark it closed.

1 members found this post helpful.