|
|
| Subject: | Updating PythonCollector ZenPack 1.6.0 - 1.7.3 seems to break things |
| Author: | Jane Curry |
| Posted: | 2015-12-09 14:33 |
Just got around to updating my PythonCollector from 1.6.0 to 1.7.3 and I now have 2 different events, one from one of my ZPs and one from the AWS ZP saying "EC2VPCSubnet/IPAddressesCount datasource has been disabled". Anyone else seen this or know what's going on
Cheers,
Jane
Email: jane.curry@skills-1st.co.uk Web: https://www.skills-1st.co.uk
| Subject: | The "datasource has been |
| Author: | Jane Curry |
| Posted: | 2015-12-11 04:16 |
The "datasource has been disabled" events come from new warchdog functionality being introduced with 1.7.1/2/3. It is documented under the blockingtimeout parameter above but I think this needs to be made much more obvious. Basically if there is no response within "blockingtimeout", default 5s, then the plugin is PERMANENTLY disabled. It also fills up zenpython.log and zenhub.log with messages. Once a plugin is blocked, it will remain permanently blocked until its name is removed from either /var/zenoss/zenpython.blocked on Zenoss 5, or /opt/zenoss/var/zenpython.blocked on Zenoss 4.
Cheers,
Jane
Email: jane.curry@skills-1st.co.uk Web: https://www.skills-1st.co.uk
| Subject: | Whoa whoa... really? Have you |
| Author: | Jay Stanley |
| Posted: | 2015-12-17 08:00 |
Whoa whoa... really Have you found a way to disable this completely I was just about to test updating to the newer version in our lab
| Subject: | Nope. You can set |
| Author: | Jane Curry |
| Posted: | 2015-12-17 08:56 |
Nope. You can set blockingtimeout to something very big, I assume - but not tried it. I really think this update needs a very large, obvious notice, not a detail buried in what I initially thought was an irrelevant parameter.
Incidentally, this change has locked out a couple of the AWS ZenPack plugins, even when I have upped the timeout from 5 to 10s. I have raised a ticket for this - https://jira.zenoss.com/browse/ZEN-21308filter=10510 .
Cheers,
Jane
Email: jane.curry@skills-1st.co.uk Web: https://www.skills-1st.co.uk
| Subject: | I also find that when a |
| Author: | Jane Curry |
| Posted: | 2015-12-29 05:36 |
I also find that when a device becomes unavailable then the PythonCollector keeps trying to gather info, fails, and again disables the datasource - PERMANENTLY ( in /opt/zenoss/var/zenpython.blocked). This has to be a bug / design fault. I'll try and get a ticket in in the next day or two - if anyone beats me to it, please post here.
Cheers,
Jane
Email: jane.curry@skills-1st.co.uk Web: https://www.skills-1st.co.uk
| Subject: | For anyone else following |
| Author: | Chet Luther |
| Posted: | 2016-01-20 13:53 |
For anyone else following this thread, an explanation can be found in the following thread.
http://www.zenoss.org/forum/136876
| < |
Previous ZenPack Development Best Practice Documentation for Core 5 |
Next PrinterMIB error importing devices |
> |