I upgraded from 2.1.1 to 2.1.2 today and everything appeared to have gone well. 
 I received no errors during the upgrade process and can access the URL just 
fine.  The problem is when I try to start the daemons it appears that they are 
started and receive a PID but then they revert to a status of stopped.  When I 
start from the commend line everything looks fine also (no errors.)  When I 
view the logs I see the following message repeated a number of times:

*************

OperationalError: (1045, "Access denied for user 'zenoss'@'localhost' (using 
password: YES)")
2008-03-10 17:02:53 ERROR zen.Events: (1045, "Access denied for user 
'zenoss'@'localhost' (using password: YES)")
Traceback (most recent call last):
  File "/usr/local/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 98, in 
sendEvent
    evid = self.doSendEvent(event)
  File "/usr/local/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 111, in 
doSendEvent
    conn = self.connect()
  File "/usr/local/zenoss/Products/ZenEvents/DbAccessBase.py", line 34, in 
connect
    database=self.database)
  File "/usr/local/zenoss/Products/ZenEvents/DbConnectionPool.py", line 70, in 
get
    database=database)
  File "/usr/local/zenoss/Products/ZenEvents/DbConnectionPool.py", line 103, in 
_createConnection
    db=database, conv=mysqlconv, reconnect=1)
  File "usr/local/zenoss/lib/python/MySQLdb/__init__.py", line 66, in Connect
    return Connection(*args, **kwargs)
  File "usr/local/zenoss/lib/python/MySQLdb/connections.py", line 134, in 
__init__
    super(Connection, self).__init__(*args, **kwargs2)
OperationalError: (1045, "Access denied for user 'zenoss'@'localhost' (using 
password: YES)")


*****************

Thank you,

John




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

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

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



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

Reply via email to