TECHZEN Zenoss User Community ARCHIVE  
FORUMS / Legacy Discussions / DISCUSSION

Repeating event.log error after upgrade to 4.2.5

Subject: Repeating event.log error after upgrade to 4.2.5
Author: [Not Specified]
Posted: 2014-09-26 10:21

Hello,

I just upgraded from core 4.2.4 to 4.2.5 SP203. After the upgrade, I noticed the following error appearing in $ZENHOME/log/event.log. It is generated at exact 60 second intervals if the web interface is being displayed, and at sporadic intervals otherwise.

ERROR ZServer uncaptured python exception, closing channel (:[Errno 32] Broken pipe [/opt/zenoss/lib/python2.7/asyncore.py|read|83] [/opt/zenoss/lib/python2.7/asyncore.py|handle_read_event|439] [/opt/zenoss/lib/python2.7/asyncore.py|handle_connect_event|447])

I haven't observed any errant behavior in any part of the web interface, and everything seems to be running fine. Does anyone have any suggestions on how to troubleshoot this issue further

Thanks!


Subject: Solved
Author: [Not Specified]
Posted: 2014-09-29 10:52

Tracked this down, it was being caused by the zenstatus daemon which was actively testing Zenoss' web server port (8080). I just disabled monitoring on that IP service for my Zenoss host server to get rid of the error.

In 4.2.5, either logging of that type of connection attempt to the web interface has been put into place, or the way zenstatus tests for active services has changed, as I don't see this error in my 4.2.4 event logs.



< Previous
zenrrdcached not running 		  Next
Massive n00b alert - how to add a device for monitoring? 		>