- Zenoss 4.2.5
Sometimes adding new devices to a remote collector through Zenoss Resource Manager fails and errors are generated. Sometimes the device addition succeeds but creates an event in the event log. The event log can display an exit code like 126 or the SiteErrorLog contains an error. For example:
exit code 126 for... ........ line 95:\
/opt/zenoss/bin/pyraw: No such file or \
line 95: exec: /opt/zenoss/bin/pyraw: \
cannot execute: No such file or directory
ERROR Zope.SiteErrorLog 1463077212.230.796819641732 \
http://myservername:8080/zport/dmd/Devices/Server/Linux/devices/checkValidId... \ ...
BadRequest: The id "abcde" is invalid - it is already in use.
These types of errors can be the result of recently installed or upgraded zenpacks. They can also be the result of duplicate IP addressing or stale network information.
This KB describes how to use use the Zenoss toolbox script zennetworkclean to fix stale network information or duplicate IP addresses.
To correct duplicate IP addresses or stale network information, use the Zenoss toolbox script zennetworkclean.
For example: as root (or a user with root authority), issue the following command:
When this script completes, you should be able to add the device, or if the device successfully added, the generated event in the log should resolve.
For additional information on the Zenoss Toolbox (utilities for analyzing and debugging environments), see the Zenoss Github site: https://github.com/zenoss/zenoss.toolbox.
For information on installing and using the Zenoss Toolbox, see the KB article:
How To Install and Use the zenoss.toolbox