Zenoss ZenTech Community

Today after a restart of serviced and docker I encountered the below errors in the Zope container Event log whenever I login to the GUI.

2016-08-23T17:34:46 WARNING urllib3.connectionpool HttpConnectionPool is full, discarding connection: 127.0.0.1

2016-08-23T17:35:04 ERROR Zope.SiteErrorLog 1471973704.990.793103257733 https://zenoss5x.zenossmaster/zport/dmd/jobs_router
Traceback (innermost last):
Module ZPublisher.Publish, line 134, in publish
Module Zope2.App.startup, line 301, in commit
Module transaction._manager, line 89, in commit
Module transaction._transaction, line 329, in commit
Module transaction._transaction, line 443, in _commitResources
Module ZODB.Connection, line 562, in commit
Module ZODB.Connection, line 1159, in _commit_savepoint
Module relstorage.storage, line 374, in getSize
Module relstorage.adapters.stats, line 56, in get_db_size
TypeError: unsupported operand type(s) for +: 'NoneType' and 'NoneType'

2016-08-23T17:35:16 ERROR ZODB.ConflictResolution Unexpected error
Traceback (most recent call last):
File "/opt/zenoss/lib/python2.7/site-packages/ZODB/ConflictResolution.py", line 243, in tryToResolveConflict
oldData = self.loadSerial(oid, oldSerial)
File "/opt/zenoss/lib/python2.7/site-packages/relstorage/storage.py", line 513, in loadSerial
raise POSKeyError(oid)
POSKeyError: 0x08

Subject:	I found this link:
Author:	[Not Specified]
Posted:	2016-08-23 16:18

I found this link:

https://github.com/zenoss/zenoss.toolbox

I'll give some of these a try starting with zodb scan

Subject:	zenoss toolbox scripts ran - issue remians
Author:	[Not Specified]
Posted:	2016-08-24 04:04

As per :

https://support.zenoss.com/hc/en-us/articles/203118175

I ran the zodb scan:

[zenoss@a864e23eaad0 toolbox]$ python ./zodbscan.py

[2016-08-24 08:24:37] Initializing zodbscan v2.0.0 (detailed log at /opt/zenoss/log/toolbox/zodbscan.log)
[2016-08-24 08:24:42] Examining 5739769 items in the 'zodb' database:
[2016-08-24 08:26:05]  Verified  [==================================================] 100%
** 96.80% of zodb objects not reachable - examine your zenossdbpack settings **

[2016-08-24 08:26:05] Execution finished in 0:01:28

Subject:
Author:	[Not Specified]
Posted:	2016-08-24 04:04

And after I ran findposkeyerror.py

[zenoss@a864e23eaad0 toolbox]$ python ./findposkeyerror.py --debug -f

[2016-08-24 08:38:21] Initializing findposkeyerror v2.0.0 (detailed log at /opt/zenoss/log/toolbox/findposkeyerror.log)
0:00:00.001780     INFO util.config [-] load config from: /qualitymonitor/ZenPacks.TNF.QualityMonitor/ZenPacks/TNF/QualityMonitor/util/config/../../etc/qm.conf
[2016-08-24 08:38:23] Examining items under the '/' path ():

[2016-08-24 08:39:17]  Cycle 1  | Items Scanned:       101836 | Errors:       0 | Repairs:      0 |

[2016-08-24 08:39:17] Execution finished in 0:00:56

logfile:

WARNING: terminal is not fully functional
2016-08-24 08:37:45,383 INFO findposkeyerror: ############################################################
2016-08-24 08:37:45,383 INFO findposkeyerror: Initializing findposkeyerror (version 2.0.0)
2016-08-24 08:37:45,383 INFO findposkeyerror: Command line options: {'unlimitedram': False, 'fix': True, 'skipEvents': False, 'debug': True, 'path': '/', 'cycles': 2, 'tmpdir': '/tmp'}
2016-08-24 08:37:45,384 DEBUG findposkeyerror: Acquired 'zenoss.toolbox' execution lock
2016-08-24 08:38:21,196 INFO findposkeyerror: ############################################################
2016-08-24 08:38:21,196 INFO findposkeyerror: Initializing findposkeyerror (version 2.0.0)
2016-08-24 08:38:21,196 INFO findposkeyerror: Command line options: {'unlimitedram': False, 'fix': True, 'skipEvents': False, 'debug': True, 'path': '/', 'cycles': 2, 'tmpdir': '/tmp'}
2016-08-24 08:38:21,197 DEBUG findposkeyerror: Acquired 'zenoss.toolbox' execution lock
2016-08-24 08:38:23,703 DEBUG findposkeyerror: ZenScriptBase connection obtained
2016-08-24 08:38:23,709 INFO findposkeyerror: Examining items under the '/' path ()
2016-08-24 08:38:23,710 INFO findposkeyerror: ## Beginning cycle 1 of 2 (potential)
2016-08-24 08:39:17,536 INFO findposkeyerror: findposkeyerror cycle 1: examined 101836 objects, encountered 0 errors, and attempted 0 repairs
2016-08-24 08:39:17,537 INFO findposkeyerror: findposkeyerror completed in 56.34 seconds
2016-08-24 08:39:17,537 INFO findposkeyerror: ############################################################

Subject:	Finally I ran zenrelationscan
Author:	[Not Specified]
Posted:	2016-08-24 04:05

Finally I ran zenrelationscan.py

[zenoss@a864e23eaad0 toolbox]$ python ./zenrelationscan.py -f

[2016-08-24 08:41:25] Initializing zenrelationscan v2.0.0 (detailed log at /opt/zenoss/log/toolbox/zenrelationscan.log)
0:00:00.002726     INFO util.config [-] load config from: /qualitymonitor/ZenPacks.TNF.QualityMonitor/ZenPacks/TNF/QualityMonitor/util/config/../../etc/qm.conf
[2016-08-24 08:41:28] Examining ZenRelations...

[2016-08-24 08:42:29]  | Items Scanned:        16207 | Errors:       0 | Repairs:      0 |

[2016-08-24 08:42:29] Execution finished in 0:01:04

logfile:

[zenoss@a864e23eaad0 ~]$ cat  /opt/zenoss/log/toolbox/zenrelationscan.log
2016-08-24 08:41:25,707 INFO zenrelationscan: ############################################################
2016-08-24 08:41:25,707 INFO zenrelationscan: Initializing zenrelationscan (version 2.0.0)
2016-08-24 08:41:25,707 INFO zenrelationscan: Command line options: {'unlimitedram': False, 'fix': True, 'skipEvents': False, 'debug': False, 'cycles': 2, 'tmpdir': '/tmp'}
2016-08-24 08:41:28,854 INFO zenrelationscan: Examining ZenRelations...
2016-08-24 08:41:28,854 INFO zenrelationscan: Beginning cycle 1
2016-08-24 08:42:29,825 INFO zenrelationscan: zenrelationscan examined 16207 objects, encountered 0 errors, and attempted 0 repairs
2016-08-24 08:42:29,825 INFO zenrelationscan: zenrelationscan completed in 64.12 seconds
2016-08-24 08:42:29,825 INFO zenrelationscan: ############################################################

Any idea what could be wrong here

John

Subject:	I also ran zencatalong scan
Author:	[Not Specified]
Posted:	2016-08-24 08:45

I also ran zencatalong scan and everything seemed ok

Subject:	I fixed this issue by re
Author:	[Not Specified]
Posted:	2016-08-29 04:51

I fixed this issue by re-creating the ZODB Session database.

Subject:	Zope Container Event Log Errors - Getting logged out of Zenoss GUI after 10 seconds
Author:	[Not Specified]
Posted:	2016-08-23 14:42

Zope Container Event Log Errors - Getting logged out of Zenoss GUI after 10 seco ...