Hey Matt, Thanks for the assistance. I did in fact do such a test and I noted it in my original email. Sorry if I wasn't clear. What I have done now is to change the service check (via the GUI) from check_nrpe with an argument list of "check_nrpe -H $HOSTADDRESS$ -c check_procs -a '-a opsviewd -w 1:10 -c 1:12'" to check_procs with an argument of -a opsviewd -w 1:10 -c 1:12. When I run this on the command line:
./check_procs -a opsviewd -w 1:2 -c 1:2 PROCS OK: 1 process with args 'opsviewd' It is fine. However, It is still showing up in the GUI as: 'PROCS CRITICAL: 4 processes with args 'opsviewd' I'm starting to think either something is totally misconfigured, or something is broken in Opsview. Can I rely on any of the results in the GUI? Joe On May 2, 2009, at 9:14 AM, Matt White wrote: > Hi Joseph, > > I had this as well. Change the check from check_nrpe to check_procs > and you should find that it returns OK instead of Critical. > > I think there should be a check_opsview_local that uses check_procs > and check_opsview_remote which uses check_nrpe > > Hope this helps > > Matt > > -----Original Message----- > From: [email protected] > [mailto:[email protected] > ] On Behalf Of Joseph Filla > Sent: 01 May 2009 22:51 > To: [email protected] > Subject: [opsview-users] Problem (bug?) with check_procs for Opsview > Daemon process on Ubuntu Hardy > > Good day, > > Running > > I've completed and initial Opsview3 setup and am testing it to > recommend/reject vs base Nagios. I've successfully gotten the setup > (via apt-get) and web site running, and I'm successfully monitoring a > remote MySQL server in addition to the master server. > > I'm perplexed with the one 'critical' warning I'm getting regarding > the service 'Opsview Daemon' on host 'Opsview Master Server' > > The warning consistently show "PROCS CRITICAL: 4 processes with args > 'opsviewd' However, when I run: > r...@monitor:/usr/local/nagios/libexec# ps ax | grep opsviewd > 4795 ? Ss 0:00 opsviewd > > there is only one process. Furthermore, if I run check_procs manually > from the command line: > > r...@monitor:/usr/local/nagios/libexec# ./check_procs -a opsviewd -w > 1:2 -c 1:2 > PROCS OK: 1 process with args 'opsviewd' > > all is fine. I even changed the service check to check with > check_procs (instead of the default -H $HOSTADDRESS$ -c check_procs -a > '-a opsviewd -w 1:2 -c 1:2') and it still shows a critical status. > > I can simply shut up this message, but I'd like to fix it if possible > > Thanks > > -- > Joseph Filla > Supervisor Systems Administrator > > > > > > > _______________________________________________ > Opsview-users mailing list > [email protected] > http://lists.opsview.org/listinfo/opsview-users > _______________________________________________ > Opsview-users mailing list > [email protected] > http://lists.opsview.org/listinfo/opsview-users -- Joseph Filla Supervisor Systems Administrator Pioneer Research Center USA, Inc. Tel: (408) 437-1800 ext #116 _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/listinfo/opsview-users
