Zenoss zenpack install log

Product Inclusion ZenPacks must always be developed with the understanding that the potential exists for them to become part of the product. Even in cases were ownership of the ZenPack does not rest with Zenoss this must be observed because ownership can change in the future. For this reason, special attention must be paid to document the inclusion of any sensitive company data in ZenPacks. Access to Test Environment In cases where the ZenPack developer s do not have access to endpoints necessary for integration and testing work some standard operating procedures must be suspended.

To make it easier for other developers to more easily get up to speed with the ZenPack in the future, the following recommendations for file locations should be used.

This configure. In the case of pure-Python modules they can be located directly here. In the case of binary modules the build process must install them here. See the section of License Compliance below for more information on how to properly handle third-party content. While the ZenPack installation code will load objects from any file in this directory with a.

IFacade should be defined in this file. IInfo should be defined in this file. Interface should be defined in this file. The account used to monitor the device does not require root access or special privileges.

Implemented with Solaris 10, Solaris Zones act as isolated virtual servers within a single operating system instance. This ZenPack has no special installation considerations. To install the ZenPack you must copy the. After installing you must restart Zenoss by running the following command as the zenoss user on your master Zenoss server:. For Solaris 9, only SSH monitoring is supported. However, this monitoring is always performed using SNMP. To remove this ZenPack you must run the following command as the zenoss user on your master Zenoss server:.

You must then restart the master Zenoss server by running the following command as the zenoss user:. To work around this sshd daemon limitation, use the configuration property zSshConcurrentSessions to control the number of connections created by zencommand to the remote device:. Set the zSshConcurrentSessions property.

If this occurs, it usually indicates that the remote device has taken too long to return results from the commands.

To increase the amount of time to allow devices to return results, change the configuration property zCommandCommandTimeout to a larger value. Increase the zCommandCommandTimeout property incrementally to a maximum of until the timeout is resolved.