| Just to let you know that the imminent Opsview 3.0.4 will have that service check re-written using check_tcp instead of check_procs. The reason we have this problem is that we tried to use a check_procs which is consistent across different platforms, but it turns out that due to underlying ps differences, it is not possible to get a single check_procs command to give the same results on all systems.
So we've changed the approach to use check_tcp against the command pipe that opsviewd uses instead, which more accurately reflects the availability of the opsviewd process.
If you upgrade your systems, you'll need to manually change your existing Opsview Daemon service check (because our upgrades do not touch existing service check definitions), but this will be documented for the release. On 5 May 2009, at 22:38, Joseph Filla wrote: James, I got it to work with your '-C' suggestion. Thanks a lot! Joe P.S. It's good to realize you're not going insane and that you've followed the instructions correctly. I appreciate it. On May 5, 2009, at 1:29 PM, James Whittington wrote: Okay as luck would have it I was just installing 2 master servers
today
so I got to see the same issue you are describing.
I am a long time nagios user and been using opsview for about 6 months
so I personally would recommend the product.
It appears they changed the service definition slightly from what it
used to be.
These steps fixed it for me..
Editing Service Check: Opsview Daemon
Edit argument
From this:
-H $HOSTADDRESS$ -c check_procs -a '-a opsviewd -w 1:2 -c 1:2'
To this:
-H $HOSTADDRESS$ -c check_procs -a '-C opsviewd -w 1:2 -c 1:2'
Apply the config and things should be good.
Based on check_procs looks like they were trying to match any string
in
a process with opsviewd..
-a, --argument-array=STRING
Only scan for processes with args that contain STRING.
--ereg-argument-array=STRING
Only scan for processes with args that contain the regex STRING.
-C, --command=COMMAND
Only scan for exact matches of COMMAND (without path).
Hope that works for you.
James Whittington
VC3, Inc.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Joseph
Filla
Sent: Tuesday, May 05, 2009 3:57 PM
To: Opsview Users
Subject: [opsview-users] Still having basic problems with opsviewd
servicecheck
Good day,
I'm sorry if it sounds like I'm nagging, but fixing this issue
reflects on Opsview3 in its entirety. If Opsview cannot properly check
how many of its own processes are running, it will be hard to justify
to my boss the value proposition of Opsview over base nagios 3.
I continue to have a Critical alert that 'PROCS CRITICAL: 4 processes
with args 'opsviewd' for the service check.
I changed the service check from the default
"check_nrpe -H $HOSTADDRESS$ -c check_procs -a '-a opsviewd -w 1:10 -c
1:12'"
to the plugin 'check_procs' with the arguments "-a opsviewd -w 1:10 -c
1:12"
Either way, I'm still getting Critical even though only one opsviewd
process are running.
Something is broken, I'm afraid and I sincerely appreciate any/all
assistance.
--
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
_______________________________________________
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
Ton Voon
Product Architect 
Opsera Limited | Unit 69 Suttons Business Park
Reading | Berkshire | RG6 1AZ | UK
Phone: +44 (0) 845 057 7887
Mobile: +44 (0) 7931 365796
Skype: tonvoon Email: [email protected]
www.opsera.comThis e-mail is confidential, intended only for the named recipient(s) above and may contain information that is privileged and confidential. If you receive this message in error, or are not the named recipient(s), please notify the sender at the phone number above, do not copy this message, do not disclose its contents to anyone, and delete this e-mail message from your computer. Although Opsera routinely screens for viruses, addressees should scan this e-mail and any attachments for viruses. Opsera makes no representation or warranty as to the absence of viruses in this e-mail or any attachments. Opsera Limited is registered in the UK under Company Number 5396532. Our registered office is Gorse View, Horsell Rise, Woking, Surrey, GU21 4RB. |
