Hello.

There is a double meaning to the word execution in the Subject: of this
email.

The summary of the problem is as follows:
An alert is triggered an my alert executed, whereas it really isn't

Let me be more specific to justify writing here.

mon.cf is set up as:
----------------------------------------------------------
hostgroup servers hi hekla victoria 10.213.0.200 localhost

watch servers
        service ping
                interval 1m
                monitor fping.monitor
                period wd {Mon-Sun}
                        alert sms.alert 92884492
                        alertevery 1m
----------------------------------------------------------

The high alert frequency is for debug purposes. Now if I execute
sms.alert as ``./sms.alert 92XXXX92'' I receive my SMS. If I rename it,
mon croaks that it can't find sms.alert. SO: mon knows where to find
sms.alert and sms.alert works fine from the command line.

Whats even more peculiar are these entries from syslog:
-------------------------------------------------------
Feb 20 12:08:32 sol mon[5516]: failure for servers ping 1014206912
victoria 
Feb 20 12:08:32 sol mon[5516]: calling alert sms.alert for servers/ping
(/usr/lib/mon/alert.d/sms.alert,92XXXX92) victoria 
Feb 20 12:09:32 sol mon[5516]: failure for servers ping 1014206972
victoria 
Feb 20 12:09:32 sol mon[5516]: calling alert sms.alert for servers/ping
(/usr/lib/mon/alert.d/sms.alert,92XXXX92) victoria 
Feb 20 12:10:32 sol mon[5516]: failure for servers ping 1014207032
victoria 
Feb 20 12:10:32 sol mon[5516]: calling alert sms.alert for servers/ping
(/usr/lib/mon/alert.d/sms.alert,92XXXX92) victoria 

-------------------------------------------------------

For additional debug purposes I have the first lines of code in the
script like this:
--------------------------------------------------------
system ("echo `date` >> /tmp/sms.alert.log");
system ("echo 'DEBUG STATEMENT' >> /tmp/sms.alert.log");
--------------------------------------------------------

So, even if there are problems with parameters, something should be
written to a log. Again, this works from the commandline.

However, when called from mon nothing happens. The script doesn't seem
to be called, but mon reports it to have been called.

Any ideas?
-- 
Lars Bahner,
http://lars.bahner.com/

Nihil est sine ratione cur potius sit, quam non sit.

Attachment: msg00337/pgp00000.pgp
Description: PGP signature

Reply via email to