Hello,

meanwhile I'm running zenoss 0.22.2 on

suse 10.1
mysql 5.0.24 (from mysql)
python 2.4.3 (from python.org)

All daemons seem to start properly (status running for all daemons within 
zenoss). I can connect to the dashboard and any page. I can add devices and get 
hardware and software infos via snmp.

But the dashboard says "Lost connection to zenoss" and I can see no events 
("Events unavailable" on the events page).

Since there are hints in the logs and in the mailing list archive that there 
might be a problem with the connection to mysql I tried to connect to mysql on 
the zenoss machine via mysql administrator tool - and got the error message "to 
many connections".

Stoping zenoss, starting mysl administrator tool and then starting zenoss again 
shows the following:
- The start of zenoss opens some connections to the mysql server.
- Every access of the dashboard, the events page etc. via web browser opens 
again some (up to 10 or 15) connections to the events db on the mysql server.
- Mysql admin tells me for all these connections the "command" is "sleep" 
(whatever that meens).
- The connections are never closed.

zenoss event.log says (many many times):

2006-09-01T12:01:47 ERROR zen.Events status failed for device x
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenEvents/EventManagerBase.py", line 532, in 
getDeviceStatus
    curs.execute(select)
  File "/usr/local/zenoss/lib/python/MySQLdb/cursors.py", line 137, in execute
    self.errorhandler(self, exc, value)
  File "/usr/local/zenoss/lib/python/MySQLdb/connections.py", line 33, in 
defaulterrorhandler
    raise errorclass, errorvalue
InterfaceError: (0, '')


or on dashboard access:
2006-09-01T12:02:14 ERROR Zope.SiteErrorLog 
http://n.n.n.n:8080/zport/dmd/ZenEventManager/getDashboardInfo
Traceback (most recent call last):
  File "/usr/local/zenoss/lib/python/ZPublisher/Publish.py", line 114, in 
publish
    request, bind=1)
  File "/usr/local/zenoss/lib/python/ZPublisher/mapply.py", line 88, in mapply
    if debug is not None: return debug(object,args,context)
  File "/usr/local/zenoss/lib/python/ZPublisher/Publish.py", line 40, in 
call_object
    result=apply(object,args) # Type s<cr> to step into published object.
  File "/usr/local/zenoss/Products/ZenEvents/EventManagerBase.py", line 690, in 
getDashboardInfo
    devices = [d[0] for d in self.getDeviceIssues(
  File "/usr/local/zenoss/Products/ZenEvents/EventManagerBase.py", line 502, in 
getDeviceIssues
    curs.execute(select)
  File "/usr/local/zenoss/lib/python/MySQLdb/cursors.py", line 137, in execute
    self.errorhandler(self, exc, value)
  File "/usr/local/zenoss/lib/python/MySQLdb/connections.py", line 33, in 
defaulterrorhandler
    raise errorclass, errorvalue
InterfaceError: (0, '')

Maybe these errors are responsible for the opened and unclosed connections?
Is there any fix for these errors (if they are known already)?

Bernd


PS:
There are more mysql-related errors in other logs, e.g. in zenxevent.log:

2006-08-31 12:04:49 ERROR zen.Events: (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 'deletedTime=null,evid='0a373ded344f8dc1fffffff'' at 
line 1")
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 19, in 
execute
    result = cursor.execute(statement)
  File "/usr/local/zenoss/lib/python/MySQLdb/cursors.py", line 137, in execute
    self.errorhandler(self, exc, value)
  File "/usr/local/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 'deletedTime=null,evid='0a373ded344f8dc1fffffff'' at line 1")
2006-08-31 12:04:53 ERROR zen.Events: (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 'deletedTime=null,evid='0a373ded344f8dc5ffffffe'' at 
line 1")
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 87, in 
sendEvent
    self.doSendEvent(event, db)
  File "/usr/local/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 109, in 
doSendEvent
    rescount = execute(curs, stmt)
  File "/usr/local/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 24, in 
execute
    raise ex
=========================================================
Diese Nachricht ist ausschliesslich fuer die adressierte Person bzw. den 
adressierten 
Personenkreis oder die Organisation bestimmt. Sie koennte vertrauliche und/oder 
privilegierte Informationen enthalten. Wenn Sie diese Mail irrtuemlich erhalten 
haben, 
benachrichtigen Sie uns sofort durch Antwort-Mail und loeschen Sie diese Mail 
nebst 
etwaigen Anlagen von Ihrem System. Ebenso duerfen Sie diese Nachricht oder 
Anlagen nicht kopieren oder an Dritte weitergeben.   Vielen Dank.

This message is intended only for use by the addressee. It may contain 
confidential or 
privileged information. If you have received this message unintentionally, 
please 
contact the sender by reply and delete it from your computer; you should not 
copy this 
message or disclose its contents to anyone.
=========================================================

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

Reply via email to