Skip navigation
Currently Being Moderated

52.6 Resolving CHANNEL_OPEN_FAILURE Issues

Created on: Oct 11, 2011 6:15 PM by Zenoss API - Last Modified:  Oct 11, 2011 6:15 PM by Zenoss API

 6. Resolving CHANNEL_OPEN_FAILURE Issues

The zencommand daemon's log file ($ZENHOME/collector/zencommand.log) may show messages stating:

ERROR zen.SshClient CHANNEL_OPEN_FAILURE: Authentication failure
WARNING:zen.SshClient:Open of command failed (error code 1): open failed

If the sshd daemon's log file on the remote device is examined, it may report that the MAX_SESSIONS number of connections has been exceeded and that it is denying the connection request. In the OpenSSH daemons, this MAX_SESSIONS number is a compile-time option and cannot be reset in a configuration file.

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:

  1. Navigate to the device or device class in the  Resource Manager interface.

    • If applying changes to a device class:

      1. Select the class in the devices hierarchy.

      2. Click Details.

      3. Select Configuration Properties.

    • If applying changes to a device:

      1. Click the device in the device list.

      2. Select Configuration Properties.

  2. Apply an appropriate value for the maximum number of sessions.


    Table 52.4. Concurrent SSH Configuration Properties



    Maximum number of sessions supported by the remote device's MAX_SESSIONS parameter. Common values for Solaris is 2 or 10.

  3. Click Save to save your changes.

Comments (0)