Skip navigation
4612 Views 4 Replies Latest reply: May 9, 2011 7:55 AM by jmp242 RSS
brogers Newbie 3 posts since
May 6, 2011
Currently Being Moderated

May 6, 2011 3:30 PM

zencommand for Linux/Ubuntu times out (uptime, stat, and meminfo)

I've created a Zenoss Core 3.1 machine as an EC2 instance, and am trying to get the Linux, Linux Addon, and Ubuntu zenpacks working for monitoring.  The issue I'm having is with zencommand timing out when trying to gather data.  Specifically, it times out on the uptime, /proc/stat, and /proc/meminfo commands (although I don't really see any data whatsoever in the reports). This happens both when trying to monitor the Zenoss machine itself as well as a separate dev EC2 instance.


Things I've done:

  • specified the zCommandUserName ('ubuntu') for the device class
  • verified that ssh from the zenoss machine to itself and to the dev machine works without a password (the key is stored in ~/.ssh)
  • restarted using zopectl restart
  • running 'zencommand run' as the zenoss user - same result
  • increasing the zCommandCommandTimeout from 15s to 45s - this just makes it take 45s to fail


The output I'm seeing:


zenoss:~/Downloads/zenpacks$ zencommand run
2011-05-06 19:03:23,714 INFO zen.zencommand: Connecting to localhost:8789
2011-05-06 19:03:23,737 INFO zen.zencommand: Connected to ZenHub
2011-05-06 19:03:23,895 INFO zen.CmdClient: command client finished collection for <ip removed>
2011-05-06 19:03:38,794 WARNING zen.zencommand: Command timed out on device <ip removed>: '/bin/cat /proc/stat'
2011-05-06 19:03:38,794 WARNING zen.zencommand: Command timed out on device <ip removed>: '/bin/cat /proc/meminfo'
2011-05-06 19:03:38,795 WARNING zen.zencommand: Command timed out on device <ip removed>: '/usr/bin/uptime'
2011-05-06 19:03:38,822 INFO zen.zencommand: Daemon zencommand shutting down


Any help would be appreciated.  Zenoss seems to be the exact monitoring system we were looking for, but this issue has me stumped.

  • tec Rank: Green Belt 197 posts since
    Oct 21, 2008

    Sent from my HTC Touch Pro2 on the Now Network from Sprint®.

  • jmp242 ZenossMaster 4,060 posts since
    Mar 7, 2007

    To inform everyone a bit here - you always need to test by running the particular daemon in verbose mode - maybe in the foreground or just to the log temporarily to see what's really going on. It is unfortunate, and a bit of a bug I think, that the various other ways to run commands do not replicate the environment or necessarily options used by the daemons. Of course, this has been like this since 1.1, so I have my doubts it's going to be addressed soon.



    James Pulver

    Information Technology Area Supervisor

    LEPP Computer Group

    Cornell University

More Like This

  • Retrieving data ...


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