fping.monitor output problems
the fping.monitor included with mon-1.0.0pre5 doesn't semm to parse the output of fping correctly. (Extra info: Depending of the fping, the combination of default options used in fping.monitor works in 1.5s for the old version an 16s for the recent version.) This happens both with SUSE with fping-2.2b1-270 and Debian with fping 2.4b2-to-ipv6- # fping -e -r 3 -t 2000 -b 56 192.168.140.3 ICMP Host Unreachable from 192.168.140.2 for ICMP Echo sent to 192.168.140.3 ICMP Host Unreachable from 192.168.140.2 for ICMP Echo sent to 192.168.140.3 ICMP Host Unreachable from 192.168.140.2 for ICMP Echo sent to 192.168.140.3 ICMP Host Unreachable from 192.168.140.2 for ICMP Echo sent to 192.168.140.3 192.168.140.3 is unreachable # ./fping.monitor 192.168.140.3 192.168.140.3 ICMP ICMP ICMP ICMP start time: Thu Jul 7 12:10:51 2005 end time : Thu Jul 7 12:11:07 2005 duration : 16 seconds fping args: fping -e -r 3 -t 2000 -b 56 -- unreachable hosts -- ICMP ICMP ICMP ICMP 192.168.140.3 # Kevin -- _ | Kevin Ivory | Tel: +49-551-370 |_ |\ || Service Network GmbH | Fax: +49-551-379 ._|ER | \|ET | Bahnhofsallee 1b | mailto:[EMAIL PROTECTED] Service Network | 37081 Goettingen |http://www.SerNet.de/ ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: fping.monitor output problems
On 2005-07-07 13:00, Kevin Ivory wrote: the fping.monitor included with mon-1.0.0pre5 doesn't semm to parse the output of fping correctly. ... # ./fping.monitor 192.168.140.3 192.168.140.3 ICMP ICMP ICMP ICMP some more extra information: the problematic code must have went in between pre3 and pre4: pre3's output looks fine. Kevin -- _ | Kevin Ivory | Tel: +49-551-370 |_ |\ || Service Network GmbH | Fax: +49-551-379 ._|ER | \|ET | Bahnhofsallee 1b | mailto:[EMAIL PROTECTED] Service Network | 37081 Goettingen |http://www.SerNet.de/ ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: mon.cf features like redistribute ?
--On Tuesday, July 05, 2005 3:16 PM +0200 Jacques Klein [EMAIL PROTECTED] wrote: Hello, I downloaded mon-1.1.0pre1.tar.gz, made some experiments with it and now I am looking for an up-to-date documentation of this version, essentially a good description of the mon.cf syntax and the maybe new feature redistribute. The lack of documentation is why its 1.1pre instead of 1.1. :) I'll try to work on the documentation this weekend. For starters, I'll add this section: redistribute alert [arg...] A service may have one redistribute option, which is a special form of an an alert definition. This alert will be called on every service status update, even sequential success status updates. This can be used to integrate Mon with another monitoring system, or to link together multiple Mon servers via an alert script that generates Mon traps. See the ALERT PROGRAMS section above for a list of the parameters mon will pass automatically to alert programs. -David David Nolan*[EMAIL PROTECTED] curses: May you be forced to grep the termcap of an unclean yacc while a herd of rogue emacs fsck your troff and vgrind your pathalias! ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Help !!!
--On Wednesday, July 06, 2005 10:04 AM +0800 D K [EMAIL PROTECTED] wrote: hi, I am a Chinese, my english is poor, so I hope you can understand this letter. Yesterday I use Mon to monitor a server, I hope Mon can alert via xmpp protocol, so I wrote a alert file, but mon seem not work. If I execute alert file, it canalert to my jabber. Now I hope mon can monitor a services is down, it can alert to my jabber. Please Help me! I wait your reply! Thanks!!! A Helper 2005.7.6 Your english isn't too bad, but your problem reporting skills definitely need some work. In order to be able to help you, we need to know in what way mon isn't working. What did you do, what behavior did you expect, and what behavior did mon show? Is mon detecting your failure and not calling the alert, or calling the alert but it fails to behave as desired? Or is mon not detecting the failure at all. If your script works when you run it but not when Mon runs it, the most likely causes are: - $PATH differences (i.e. your script is running some program that appears in your PATH but not in the PATH that mon provides to the alert script) - privilege difference. i.e you ran your test as root but Mon is running as nobody, or similar. We need more information in order to provide any better guidance for solving your problem. -David David Nolan*[EMAIL PROTECTED] curses: May you be forced to grep the termcap of an unclean yacc while a herd of rogue emacs fsck your troff and vgrind your pathalias! ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
