Troubleshooting

Test Connection fails for managed systems with the following error when the SSH login prompt appears with a delay:

[TimeoutException] [Possible suggestions] Tune the parameter <sshTimeOut>. [Error details] Timeout occurred while setting the shell 'sh'

This error occurs when the connector tries to log in to the target managed system with SSH and execute the sh command. The sh command fails because of the delay on the target managed system for the SSHLogin prompt to appear.

Resolution – To resolve this issue, adjust the following timeout parameters in the application Debug page:

• sshWaitTime – Default value – 500 ms

  This timeout parameter is responsible for the wait to receive a command output.

• SSHTimeOut – Default value – 120000 ms

This timeout parameter is responsible for tuning the maximum time for a SSH command to execute. After this timeout, the connection is dropped and the operation will time out, even if the command execution is in progress on the target host.

Aggregation/test connection fails with the following timeout error:

Exception during aggregation of Object Type account on Application <application name> Reason: Unable to create iterator sailpoint.connector.TimeoutException: [TimeoutException] [Possible suggestions] Tune the parameter <sshTimeOut>. [Error details] Timeout occurred while reading command response.

Test Connection fails with following timeout error:

[TimeoutException] [Possible suggestions] Tune the parameter <sshTimeOut>. [Error details] Timeout occurred while reading output stream for the executed command.

Resolution – Change the value of the sshWaitTime (in millisecond) application attribute as required using the REST API:

Set the following attribute using the SailPoint REST API. Refer to Best Practices: REST API Authentication and REST API - Update Source (Partial).

• Attribute Key – sshWaitTime

• Attribute Value – 500

For AIX sources, there is a timeout error. It has been observed that if any of the AIX machines have any third-party software (for example, Centrify) installed, then it does not prompt for the sudo user's password.

Note
If the sshWaitTime setting does not solve the problem, connect to the AIX System using the sudo user to check the system's behavior.

After executing the following command, the connector should prompt for %SAILPOINTSUDO where the user is asked enter the sudo user's password:

sudo -p %SAILPOINTSUDO echo TestConnection

However, because some third-party software (for example, Centrify), may not prompt for %SAILPOINTSUDO;, the AIX source does not detect that it is being asking for the sudo user's password, and therefore doesn't prompt the user.

For example, if the system prompts for CSO Password:, then the source should recognize that it is actually a prompt for the sudo user's password. Manually configure a custom sudo user password prompt using the SudoPasswdPrompt attribute.

Set the following attribute using the SailPoint REST API.

• Attribute Key – SudoPasswdPrompt

• Attribute Value: <actual third party software prompt>

For example, for Centrify software you can also use CSO Password: as a value.

Note
For more information on SailPoint's REST APIs, refer to Best Practices: REST API Authentication and REST API - Update Source (Partial) in the SailPoint Developer Community.