TECHZEN Zenoss User Community ARCHIVE  

Notifications are delayed

Subject: Notifications are delayed
Author: [Not Specified]
Posted: 2014-09-08 21:13

Hi Zenoss support
The notifications are always 20 mins~30+ hours delayed than the event created time. Check the log in zenactiond , found below error.
Would you please check the error and advise how to check the problem Thanks

2014-09-06 15:11:10,483 INFO zen.maintenance: Performing periodic maintenance
2014-09-06 15:12:10,498 INFO zen.maintenance: Performing periodic maintenance
2014-09-06 15:12:32,960 WARNING zen.callhome: Callhome metrics gathering failed: stdout: , stderr: ERROR:ZODB.Connection:Couldn't load state for 0x48
Traceback (most recent call last):
File "/opt/zenoss/lib/python/ZODB/Connection.py", line 860, in setstate
self._setstate(obj)
File "/opt/zenoss/lib/python/ZODB/Connection.py", line 901, in _setstate
p, serial = self._storage.load(obj._p_oid, '')
File "/opt/zenoss/lib/python/relstorage/storage.py", line 462, in load
state, tid_int = cache.load(cursor, oid_int)
File "/opt/zenoss/lib/python/relstorage/cache.py", line 279, in load
state, tid_int = self.adapter.mover.load_current(cursor, oid_int)
File "/opt/zenoss/lib/python/relstorage/adapters/mover.py", line 130, in mysql_load_current
cursor.execute(stmt, (oid,))
File "/opt/zenoss/lib/python/MySQLdb/cursors.py", line 174, in execute
self.errorhandler(self, exc, value)
File "/opt/zenoss/lib/python/MySQLdb/connections.py", line 36, in defaulterrorhandler
raise errorclass, errorvalue
OperationalError: (2006, 'MySQL server has gone away')
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenCallHome/callhome.py", line 141, in
main.run()
File "/opt/zenoss/Products/ZenCallHome/callhome.py", line 106, in run
data = chd.getData()
File "/opt/zenoss/Products/ZenCallHome/callhome.py", line 91, in getData
chData = utilClass().generateData(self._dmd)
File "/opt/zenoss/Products/ZenCallHome/callhome.py", line 37, in generateData
for key, val in util.callHomeData(*args):
File "/opt/zenoss/Products/ZenCallHome/ZenossAppData.py", line 30, in callHomeData
self._catalog = ICatalogTool(self.dmd)
File "/opt/zenoss/lib/python/zope/component/hookable.py", line 33, in __call__
return self.__implementation(*args, **kw)
File "/opt/zenoss/lib/python/zope/component/hooks.py", line 115, in adapter_hook
return siteinfo.adapter_hook(interface, object, name, default)
File "/opt/zenoss/Products/Zuul/tree.py", line 231, in __init__
self.catalog._v_caches = getattr(self.catalog, "_v_caches", OOBTree())
File "/opt/zenoss/lib/python/ZODB/Connection.py", line 860, in setstate
self._setstate(obj)
File "/opt/zenoss/lib/python/ZODB/Connection.py", line 901, in _setstate
p, serial = self._storage.load(obj._p_oid, '')
File "/opt/zenoss/lib/python/relstorage/storage.py", line 462, in load
state, tid_int = cache.load(cursor, oid_int)
File "/opt/zenoss/lib/python/relstorage/cache.py", line 279, in load
state, tid_int = self.adapter.mover.load_current(cursor, oid_int)
File "/opt/zenoss/lib/python/relstorage/adapters/mover.py", line 130, in mysql_load_current
cursor.execute(stmt, (oid,))
File "/opt/zenoss/lib/python/MySQLdb/cursors.py", line 174, in execute
self.errorhandler(self, exc, value)
File "/opt/zenoss/lib/python/MySQLdb/connections.py", line 36, in defaulterrorhandler
raise errorclass, errorvalue
_mysql_exceptions.OperationalError: (2006, 'MySQL server has gone away')



Subject: MySQL server has gone away =
Author: Jan Garaj
Posted: 2014-09-09 15:57

MySQL server has gone away = your MySQL server was not available for Zenoss - check network connection and availability of your MySQL server from Zenoss master/collector.

MySQL server has gone away was my standard problem, when my app server was in different location than DB server (2 different data centers); standard ping 100ms, but sometimes it was >500ms - unreliable connection.

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch



< Previous
UTF-8 / international chars in Locations
  Next
Enterprise OID for sysName
>