I am having the same problem with zenoss v3.2.1 and zenpack version 1.0.3 on an ubuntu system.  Zenoss finds all of my ec2 instances, and succesfully runs the commands to contact EC2 at regular intervals, but no data is returned nor graphed.  All my instances are in the west coast.

Was there a solution to this problem I missed?

Here is the relevant excerpt from my zencommand.log with my aws access credentials removed:

2012-01-23 20:11:14,565 DEBUG zen.zencommand: Command: '/bin/sh -c exec /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300'

2012-01-23 20:11:14,565 DEBUG zen.zencommand: Output: ''

2012-01-23 20:11:14,565 DEBUG zen.zencommand: Process zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key> -r 300  stopped (0), 1.30 seconds elapsed

2012-01-23 20:11:14,566 DEBUG zen.zencommand: Dropping useless clear event {'manager': 'localhost', 'eventKey': 'zencw2', 'device': 'EC2Manager', 'eventClass': '/Cmd/Fail', 'summary': 'Cmd: /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300 - Code: 0 - Msg: Success', 'component': '', 'monitor': 'localhost', 'agent': 'zencommand', 'severity': 0}

2012-01-23 20:11:14,566 DEBUG zen.zencommand: The result of "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2Manager -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300" was "''"

2012-01-23 20:11:14,566 DEBUG zen.zencommand: Next command in 296 seconds

2012-01-23 20:11:15,537 DEBUG zen.zencommand: Received exit code: 0

2012-01-23 20:11:15,537 DEBUG zen.zencommand: Command: '/bin/sh -c exec /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2InstanceType -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300'

2012-01-23 20:11:15,537 DEBUG zen.zencommand: Output: ''

2012-01-23 20:11:15,537 DEBUG zen.zencommand: Process zencw2.py EC2InstanceType -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300  stopped (0), 1.25 seconds elapsed

2012-01-23 20:11:15,538 DEBUG zen.zencommand: Dropping useless clear event {'manager': 'localhost', 'eventKey': 'zencw2', 'device': 'EC2Manager', 'eventClass': '/Cmd/Fail', 'summary': 'Cmd: /usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2InstanceType -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300 - Code: 0 - Msg: Success', 'component': '', 'monitor': 'localhost', 'agent': 'zencommand', 'severity': 0}

2012-01-23 20:11:15,538 DEBUG zen.zencommand: The result of "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec/zencw2.py EC2InstanceType -u <aws_access_key> -p <aws_secret_key>+qeHP -r 300" was "''"

2012-01-23 20:11:15,538 DEBUG zen.ComponentCommandParser: ParsedResults

  events: []

  values: []}

2012-01-23 20:11:15,539 DEBUG zen.zencommand: Next command in 295 seconds

No, there is no option to increase the logging on the command line as in -v 10. It has already been set to debug level in the config.  And further, nothing is sent to stdout when I execute the command on the console.

For those same lines I show the following:

usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg/ZenPacks/zenoss/ZenAWS/libexec:

def getOpts():

    from optparse import OptionParser

    parser = OptionParser()

    parser.add_option("-r", "--range", dest="range",

        help="time range to poll in seconds ", default=300, type='int')

    parser.add_option("-c", "--consolidate",

        dest="consolidate", default='Average',

        help="Consolidation function (Average, Minimum, Maximum, Sum, Samples)")

    parser.add_option("--units", dest="units", default="",

        help="units in which data is returned ('Seconds', 'Percent', 'Bytes', "

         "'Bits', 'Count', 'Bytes/Second', 'Bits/Second', 'Count/Second')")

    parser.add_option("-u","--userkey", dest="userkey",

                      default=os.environ.get('AWS_ACCESS_KEY_ID', None))

    parser.add_option("-p","--privatekey", dest="privatekey",

                      default=os.environ.get('AWS_SECRET_ACCESS_KEY', None))

    return parser.parse_args()

It appears that the advanced logging option was added after the latest stable release? Is there another stable release I should try installing?

This is the latest egg release of ZenAWS that I could find:

servlet/JiveServlet/download/4423-4-3171/ZenPacks.zenoss.ZenAWS-1.0.3-py2.6.egg.zip

I found it at

docs/DOC-4423

Since an egg is just a standard zip file. I just unzipped it and pulled out the zencw2.py file and it's the version without the logging parameter.  Did you install from source or from the distributed egg above, from source, or from another egg?

Thanks!

Oh boy, the good folks at Zenoss released different code in the RPM than

they did in the EGG for the same version (1.0.3)?  Tell me it's not true!

:).  My next question is, has anyone who installed the EGG ZenAWS(1.0.3)

with Zenoss 3.2.1 been successful?  I installed my ZenOss with apt-get and

the egg by downloading in the link earlier in the thread.

I was able to install the zenpack above using the zenoss GUI.

Once I configure the account I am able to get the, instances and instancetype.

but I am not able to get see data of CPU or MEM nor the graph is getting populated.

I also am having the very same problem.  My configuration:

Zenoss 4.2.0

ZenAWS 1.1.0

Any ideas on how to fix this problem?  Note, the Zenoss server is in a different time zone from the Amazon Instances.