---

Subject:	RE: Multiple Issues with Zenpython on Zenoss 6.2.1
Author:	Michael Rogers
Posted:	2020-02-03 11:13

Larry,

The best way to find out what zenpython is up to will be to check its logs directly.  You can attach to the container and tail its log with the following:

serviced service attach zenpython
su - zenoss
cd /opt/zenoss/log/
tail -f zenpython.log​

If a collection daemon is slow to return to work after a restart, it could come down to an issue with zenhub.  There are numerous factors that can affect performance (number of collection daemons you're running, number of devices they're monitoring, CPU cores in the pool, available zenhub workers, etc.), so checking logs is a decent place to start.  If the zenpython.log points to zenhub as a culprit, you can get to its log by altering the commands above.

Check the zenhub.log for messages like "all workers busy" or "available workers []".  If you see messages along those lines, you may need to scale up your available workers.  Please note that prior to 6.3, zenhub workers are controlled via the zenhub.cnf file; after 6.3, zenhub workers were spun out into their own service which can be scaled directly in Control Center.

Let us know what you find?

------------------------------
Michael Rogers
Senior Instructor
Zenoss
Austin TX
------------------------------