Closed ToddHebert closed 12 years ago
Which Zenoss package did you install, the stack or native RPM? To be specific, if your service is called zenoss-stack you have the stack. If your service is called zenoss you have the native RPM.
I've had one other report of a symlink not being created properly on the stack installer that might be the cause of this.
It looks like I installed the stack (/etc/init.d/zenoss-stack is the init script.)
--Todd
-----Original Message----- From: Chet Luther [mailto:reply+i-2854858-c5ea13a8ec4b2dee946a62fe90f3bd6726fd1a57-1333806 @reply.github.com] Sent: 16 January 2012 17:55 To: Todd Hebert Subject: Re: [ZenPacks.zenoss.CloudStack] Cloudstack monitor unable to parse returned output (#4)
Which Zenoss package did you install, the stack or native RPM? To be specific, if your service is called zenoss-stack you have the stack. If your service is called zenoss you have the native RPM.
I've had one other report of a symlink not being created properly on the stack installer that might be the cause of this.
Reply to this email directly or view it on GitHub: https://github.com/zenoss/ZenPacks.zenoss.CloudStack/issues/4#issuecomme nt-3515255
Can you take a look at Jason's workaround in issue #2 and see if that works for you too?
I just fixed the issue in issue #2. The fix in in version of 0.7.6 of the ZenPack which I have just uploaded.
I believe this is the same issue you're facing. You can either grab version 0.7.6 of the ZenPack and install it, or follow the steps outlined in #2 to get monitoring working.
I've just installed the 0.7.6 version of the Zenpack, and it now appears to be gathering statistics properly. =D
I am getting the following detailed error:
error parsing command results: No JSON object could be decoded
This has been going on since the webinar where the Cloudstack plugin to Zenoss was announced quite some time ago, but this is the first chance I've had to address it.
Zenoss version is 3.2.0 running on CentOS 5.7 Python version is 2.6.5 Cloudstack plugin 0.7.4 Linux monitor 1.1.5 XenMonitor 1.0.3 VirtualHostMonitor 2.3.6
The only thing I can think of that might be unusual, is that our system has an SSL certificate in front of it, so even the monitoring bit must go through https.. if the Zenpack is in some place not using the supplied "https://" prefix and is trying to use http, the lookup would fail.