Our test emails are going OK but the zenactions log is showing the following 
errors when trying to send an email when an incident occurs triggering the 
alert:

2009-06-29 18:07:40 INFO zen.ZenActions: processed 1 rules in 0.06 secs
2009-06-29 18:08:40 INFO zen.ZenActions: Processed 0 commands in 0.000024
2009-06-29 18:08:40 WARNING zen.ZenActions: SELECT 
firstTime,device)s+Component:+%(component)s+Severity+%(severityString)s+Message:+%(message,component,summary,device,message,severity,summary,
 evid FROM status WHERE (prodState = 1000) and (eventState = 0) and (severity 
>= 4) and firstTime + 2 < UNIX_TIMESTAMP() AND evid NOT IN  (SELECT evid FROM 
alert_state   WHERE userid='admin' AND rule='test' )
2009-06-29 18:08:40 ERROR zen.ZenActions: action:test
Traceback (most recent call last):
  File "/opt/zenoss/Products/ZenEvents/zenactions.py", line 237, in processRules
    self.processEvent(zem, ar, actfunc)
  File "/opt/zenoss/Products/ZenEvents/zenactions.py", line 263, in processEvent
    for result in self.query(q):
  File "/opt/zenoss/Products/ZenEvents/zenactions.py", line 199, in query
    curs.execute(stmt)
  File "/opt/zenoss/lib/python/MySQLdb/cursors.py", line 137, in execute
    self.errorhandler(self, exc, value)
  File "/opt/zenoss/lib/python/MySQLdb/connections.py", line 33, in 
defaulterrorhandler
    raise errorclass, errorvalue
ProgrammingError: (1064, "You have an error in your SQL syntax; check the 
manual that corresponds to your MySQL server version for the right syntax to 
use near 
')s+Component:+%(component)s+Severity+%(severityString)s+Message:+%(message,compo'
 at line 1")
2009-06-29 18:08:40 INFO zen.ZenActions: processed 1 rules in 0.06 secs

This is on 2.4.2 - Any Ideas?




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=36427#36427

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to