Archived community.zenoss.org | full text search
Skip navigation
Up to Discussions in zenoss-cloud
3876 Views 3 Replies Latest reply: Mar 12, 2012 5:19 PM by dpetzel RSS
Kali Nguyen Newbie
Kali Nguyen
4 posts since
Feb 21, 2012
Currently Being Moderated

Feb 22, 2012 1:37 PM

Unable to link EC2Manager with my Instances

Hello all,

   I got 80 instances in the Amazon EC2 cloud environment. I have setup Zenoss Core, SSH Monitor, RemoteCollector and AWS ZenPacks in the system. I am still unable to get my instances loaded into the Infrastructure part of the system. I also contacted Amazon EC2 and got my EC2 API throttle rate doubled which apparently can give me up to 120 instances that I can manage in Zenoss. So while modeling my EC2Manager, I get the following response and it does not work.

 

Hello Simon,

   I've gotten Amazon to double our throttle rate with EC2 API requests but I still get this error, any ideas as to what is going on?

 

 

2012-02-21 13:13:44,421 INFO zen.ZenModeler: Connecting to localhost:8789

 

2012-02-21 13:13:44,436 INFO zen.ZenModeler: Connected to ZenHub

2012-02-21 13:13:44,506 INFO zen.ZenModeler: Collecting for device EC2Manager

2012-02-21 13:13:44,526 INFO zen.ZenModeler: No WMI plugins found for EC2Manager

2012-02-21 13:13:44,531 INFO zen.ZenModeler: Python collection device EC2Manager

2012-02-21 13:13:44,532 INFO zen.ZenModeler: plugins: zenoss.aws.EC2InstanceMap

2012-02-21 13:13:44,532 INFO zen.PythonClient: running zenec2modeler plugin

2012-02-21 13:13:44,543 INFO zen.ZenModeler: No command plugins found for EC2Manager

2012-02-21 13:13:44,544 INFO zen.ZenModeler: SNMP monitoring off for EC2Manager

2012-02-21 13:13:44,545 INFO zen.ZenModeler: No portscan plugins found for EC2Manager

2012-02-21 13:13:53,694 INFO zen.PythonClient: Python client finished collection for EC2Manager

2012-02-21 13:13:53,853 ERROR zen.ZenModeler: Traceback (most recent call last):

File "/usr/local/zenoss/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner

return callable(*args, **kw)

File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 121, in remote_applyDataMaps

result = inner(map)

File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 114, in inner

if adm._applyDataMap(device, map):

File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 200, in _applyDataMap

changed = self._updateObject(tobj, datamap)

File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject

setter(*args)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/EC2Manager.py", line 110, in setInstances

self._setInstances(instances)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/EC2Manager.py", line 152, in _setInstances

background=True).id

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.DistributedCollectors-1.6.egg/ZenPacks/community/DistributedCollectors/__init__.py", line 241, in _executeZenDiscCommand

result = self.dmd.JobManager.addJob(ShellCommandJob,

NameError: global name 'ShellCommandJob' is not defined

Traceback (most recent call last):

File "/usr/local/zenoss/zenoss/Products/DataCollector/zenmodeler.py", line 668, in processClient

if driver.next():

File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result

raise ex

RemoteException: Traceback (most recent call last):

File "/usr/local/zenoss/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner

return callable(*args, **kw)

File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 121, in remote_applyDataMaps

result = inner(map)

File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 114, in inner

if adm._applyDataMap(device, map):

File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 200, in _applyDataMap

changed = self._updateObject(tobj, datamap)

File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject

setter(*args)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/EC2Manager.py", line 110, in setInstances

self._setInstances(instances)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/EC2Manager.py", line 152, in _setInstances

background=True).id

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.DistributedCollectors-1.6.egg/ZenPacks/community/DistributedCollectors/__init__.py", line 241, in _executeZenDiscCommand

result = self.dmd.JobManager.addJob(ShellCommandJob,

NameError: global name 'ShellCommandJob' is not defined

2012-02-21 13:13:53,855 ERROR zen.ZenModeler: Client EC2Manager finished with message: [Failure instance: Traceback (failure with no frames): : Traceback (most recent call last):

File "/usr/local/zenoss/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner

return callable(*args, **kw)

File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 121, in remote_applyDataMaps

result = inner(map)

File "/usr/local/zenoss/zenoss/Products/ZenHub/services/ModelerService.py", line 114, in inner

if adm._applyDataMap(device, map):

File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 200, in _applyDataMap

changed = self._updateObject(tobj, datamap)

File "/usr/local/zenoss/zenoss/Products/DataCollector/ApplyDataMap.py", line 370, in _updateObject

setter(*args)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/EC2Manager.py", line 110, in setInstances

self._setInstances(instances)

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/EC2Manager.py", line 152, in _setInstances

background=True).id

File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.community.DistributedCollectors-1.6.egg/ZenPacks/community/DistributedCollectors/__init__.py", line 241, in _executeZenDiscCommand

result = self.dmd.JobManager.addJob(ShellCommandJob,

NameError: global name 'ShellCommandJob' is not defined

]

2012-02-21 13:13:53,855 INFO zen.ZenModeler: Scan time: 9.35 seconds

2012-02-21 13:13:53,893 INFO zen.ZenModeler: Daemon ZenModeler shutting down

 

I'd appreciate any help I can get with this. Thank you.

 

Kali Nguyen

  • dpetzel Rank: Brown Belt
    dpetzel
    1,141 posts since
    Oct 17, 2010
    Currently Being Moderated
    1. Feb 22, 2012 8:15 PM (in response to Kali Nguyen)
    Re: Unable to link EC2Manager with my Instances

    Any chance you manually installed the AWS pack, as opposed to having installed it using the RPM Bundle? The downloaded egg seems to be an "older" version, despite having the same build number: message/63852#63852

  • Kali Nguyen Newbie
    Kali Nguyen
    4 posts since
    Feb 21, 2012
    Currently Being Moderated
    2. Mar 12, 2012 11:59 AM (in response to dpetzel)
    Re: Unable to link EC2Manager with my Instances

    Yes, that's actually what happened. I am using a CentOS 5 OS, installed the base zenoss with RPM and then installed the AWS pack because the ZenPack RPM did not work. Mentioned soemthing about the versions of Zenoss being different or a dependency file. What packages should I be using and maybe there is a certain AMI of CentOS 5 that you could recommend. Thanks.

     

    Solaris

  • dpetzel Rank: Brown Belt
    dpetzel
    1,141 posts since
    Oct 17, 2010
    Currently Being Moderated
    3. Mar 12, 2012 5:19 PM (in response to Kali Nguyen)
    Re: Unable to link EC2Manager with my Instances

    I've only played with the pack a little but, but the version I used was the one from the RPM. I can't speak to the version that is available for download, aside from the previous thread I posted.

     

    My suggestion would be get back to that latest version (which I attached the egg for in that other thread), and then start troubleshooting from there.

     

    As far as the AMI, I'm not sure. When I did my testing, I was testing against the Amazon Linux AMI, however that shouldnt matter for your EC2manager, it would only come into play if you were monitoring the individual VMs themselves (which is also good to do).

     

    The Actualy AMI's shouldn't matter for the purposes of EC2Manager listing your instances and such.

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points