cluther wrote:
> On Jun 26, 2008, at 7:41 AM, shakespear wrote:
>
> >
> > >
> > > > in the zenactions log infrequently for a command the message
> > > >
> > > > ERROR zen.ZenActions: Command alert_incharge timed out
> > > >
> > > > occurs.
> > > >
> > > > The command alert_incharge takes some arguments (Event details),
> > > > looks up an email address in a text file and generates / sends the
> > > > E-
> > > > Mail.
> > > >
> > > > In some cases the command timed out.
> > > >
> > > > For testing, the actual email sending is disabled currently - but
> > > > ths didn't change the behaviour.
> > > >
> > > > But in general the called script (perl-script) works. Do you have
> > > > any idea how to debaug this problem?
> > > >
> > >
> >
>
> Maybe it has something to do with the event details that are being
> passed. Could any of the fields you're passing to the command
> potentially have special characters in them that would need quoting or
> escaping on the shell?
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
Unfortunately not :).
CUrrently I stripped down the script to:
---
#!/bin/sh
#echo `date` >>/home/zenoss/var/log/zen_alert.log
---
(the great do definitly nothing script)
The call of the script is:
/home/zenoss/bin/zen_alert_incharge.pl -quiet -relayhost=localhost
-inchargecfg=/home/zenoss/import/automatically/files/config.txt
-subject="[MONITORING][INCHARGE] ${evt/device} ${evt/summary}"
-fromadr="MONITOR" -evdevice="${evt/device}:" --evip="${evt/ipAddress}:"
-evcomponent="${evt/component}:" -evseverity="${evt/severity}:"
-evsummary="${evt/summary}:" -evmessage="${evt/message}:"
-evfirsttime="${evt/firstTime}:" -domain="y.z"
-evurl="https://x.y.z/zport/dmd/ZenEventManager/eventFields?evid=${evt/evid}:";
Same effect:
2008-07-04 15:53:32 INFO zen.ZenActions: processed 21 rules in 0.08 secs
2008-07-04 15:54:33 INFO zen.ZenActions: Processed 1 commands in 0.007104
2008-07-04 15:54:33 INFO zen.ZenActions: processed 21 rules in 0.09 secs
2008-07-04 15:55:03 ERROR zen.ZenActions: Command zen_alert_incharge timed out
but not every time - those are running:
2008-07-04 15:41:13 INFO zen.ZenActions: processed 21 rules in 0.08 secs
2008-07-04 15:42:14 INFO zen.ZenActions: Running
/home/zenoss/bin/zen_alert_incharge.pl -quiet -relayhost=localhost
-inchargecfg=/home/zenoss/import/automatically/files/config.txt
-subject="[MONITORING][INCHARGE] r100.d5030.ams.or.at SNMP result error. Maybe
not a HP ProCurve switch?" -fromadr="MON-PROD" -evdevice="x.y.z:"
--evip="x.y.z:" -evcomponent="PowerSupply:" -evseverity="4:" -evsummary="SNMP
result error. Maybe not a HP ProCurve switch?:" -evmessage="SNMP result error.
Maybe not a HP ProCurve swit
ch?:" -evfirsttime="2008/07/04 15:41:38.000:" -domain="x.y.z"
-evurl="https://x.y.z/zport/dmd/ZenEventManager/eventF
ields?evid=c225e19c36f0c092e464f9b:"
2008-07-04 15:42:14 INFO zen.ZenActions: Running
/home/zenoss/bin/zen_alert_incharge.pl -quiet -relayhost=localhost
-inchargecfg=/home/zenoss/import/automatically/files/config.txt
-subject="[MONITORING][INCHARGE] x.y.z ERROR - ALTERNATIVE/BACKUP Route
to x.y.z ACTIVE (via: x.y.z)" -fromadr="MON-PROD" -evdevice="x.y.z:"
--evip="x.y.z:"
-evcomponent="Route:" -evseverity="4:" -evsummary="ERROR - ALTERNATIVE/BACKUP
Route to x.y.z ACTIVE (via: x.y.z):" -evmessage="ERROR - ALTERNATIVE/BACKUP
Route to x.y.z ACTIVE (via: x.y.z):" -evfirsttime="2008/
07/04 15:41:57.000:" -domain="y.z"
-evurl="https://x.y.z/zport/dmd/ZenEventManager/eventFields?evid=c225e19c36f0c0
a5e461f9b:"
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=22165#22165
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
