Daniel Butler
2013-09-13 14:52:35 UTC
Daniel Butler [http://community.zenoss.org/people/dbutler] created the discussion
"Re: JMX Connection Error"
To view the discussion, visit: http://community.zenoss.org/message/74635#74635
--------------------------------------------------------------
I had a similar issue where ZenJMX was unable to connect in v4.2.3 with the same error:
java.net.ConnectException: Connection refused
Looks like this is a bug where the ZenJMX ZenPack uses the Device ID rather than IP address to attempt to connect. When creating a device the IP address is the same as the Device ID, however, if you subsequently Reset the IP address of a device it appears that the IP address gets updated but the device ID stays the same as the original IP address. You can see the Device IDs that have been created in /opt/zenoss/perf/Devices
The bug seems to be that the zenjmx zenpack uses the device ID rather than the IP address which seems to be used correctly by other zenpacks/components.
A workaround is to delete the device (checking the box to delete all of the performance data) and readd it with the new IP address instead of trying to reset the IP address of an existing device.
This is a particular problem if you are using AWS where you may be terminating and respin instances on a regular basis as it means that you lose all of your historical performance data (or at least end up with lots of orphaned data).
I'd love to know how Zenoss plan to track zenoss data with autoscaling groups!
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74635#74635]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Re: JMX Connection Error"
To view the discussion, visit: http://community.zenoss.org/message/74635#74635
--------------------------------------------------------------
I had a similar issue where ZenJMX was unable to connect in v4.2.3 with the same error:
java.net.ConnectException: Connection refused
Looks like this is a bug where the ZenJMX ZenPack uses the Device ID rather than IP address to attempt to connect. When creating a device the IP address is the same as the Device ID, however, if you subsequently Reset the IP address of a device it appears that the IP address gets updated but the device ID stays the same as the original IP address. You can see the Device IDs that have been created in /opt/zenoss/perf/Devices
The bug seems to be that the zenjmx zenpack uses the device ID rather than the IP address which seems to be used correctly by other zenpacks/components.
A workaround is to delete the device (checking the box to delete all of the performance data) and readd it with the new IP address instead of trying to reset the IP address of an existing device.
This is a particular problem if you are using AWS where you may be terminating and respin instances on a regular basis as it means that you lose all of your historical performance data (or at least end up with lots of orphaned data).
I'd love to know how Zenoss plan to track zenoss data with autoscaling groups!
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74635#74635]
Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]