![]() |
![]() |
Subject: | Zenpython Daemon Crashing Frequently after upgrade to Windows 2.2.0 |
Author: | [Not Specified] |
Posted: | 2015-01-02 08:28 |
Since I upgraded to the Windows 2.2.0 Zenpack, I have been getting frequent Zenpython daemon crashes. Data collection/graphing will stop and I have to start the daemon back up. It happens every 3-4 days.
I'm seeing the following error in the Zenpython log, it happens roughly around the same time that graphing stops.
2015-01-02 06:06:01,863 ERROR zen.MicrosoftWindows: Failed collection [Failure instance: Traceback:
Subject: | [Errno 12] Cannot allocate |
Author: | Jan Garaj |
Posted: | 2015-01-02 10:41 |
[Errno 12] Cannot allocate memory => you have a problem with a memory. Analyze memory usage per process on your Zenoss server and then you should to see who is responsible for your problems.
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
Subject: | Thanks, I will look into the |
Author: | [Not Specified] |
Posted: | 2015-01-07 12:14 |
Thanks, I will look into the per process memory usage.
It is interesting to note that the entire zenoss server is only using around 50% of the available ram (50% is not used, buffered, or cached). Something must be artificially limiting processes from grabbing more memory.
Subject: | Also having issues with Zenpython crashing |
Author: | [Not Specified] |
Posted: | 2015-02-17 11:20 |
I too upgraded my Microsoft Pack to 2.2.0 and have been experiencing the same crashes and graphs stop graphing. The WMI collectors work just fine. I blame the software, because it started to fail after the update.
< |
Previous custom zenpython datasource issue |
Next MSSQL queries in ZenOss 4.2.5 |
> |