Thats the error that corrupted my install of Zenoss 2.0.2.. I am guessing that you are going to also see that there is a cache file error as well, at least that is what I was seeing. For some reason if the mySQL daemon restarts, it does evil things to zenhub and really messes it up. I asked for suggestions in a different thread about fixing this issue, but since nobody responded, I ended up having to wipe the install and go from scratch. Looks like you might be stuck doing the same.
csuarez wrote: > zenhub.log > > 2007-07-27 09:53:50 ERROR log: (2006, 'MySQL server has gone away') > Traceback (most recent call last): > File "/opt/zenoss/Products/ZenHub/services/EventService.py", line 26, in > remote_sendEvent > return self.zem.sendEvent(evt) > File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 52, in > sendEvent > return self._sendHeartbeat(event) > File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 227, in > _sendHeartbeat > raise ZenBackendFailure(str(e)) > ZenBackendFailure: (2006, 'MySQL server has gone away') ------------------------ Christopher Hubbard -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=9252#9252 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
