This topic provides information to help you troubleshoot issues that you might encounter when implementing remote actions in your environment.

Executing a reboot command using a remote action results in timeout messages

When you run the reboot command on a remote system, you might receive a timeout message on an action result event even though the remote system was rebooted successfully.

For example, if you run a reboot action without specifying the execute_user parameter in the credential_repository.xml file, the remote system is rebooted, but the server does not receive a response from the remote system. Because it does not receive any response, it displays a timeout message, such as exit code 111: Timeout occurred while reading commands output.

If you run a reboot action without specifying the execute_user parameter in the credential_repository.xml file, the remote system is rebooted, but the server does not receive a response from the remote system. If the server cannot determine whether the lack of a response is due to a timeout or some other failure such as loss of a network connection, it displays a message, such as exit code 1007: Encountered error while waiting for system response. May be timed out.

Was this page helpful? Yes No Submitting... Thank you
© Copyright 2013-2015 BMC Software, Inc.
© Copyright 2013-2015 BladeLogic, Inc.
Legal notices