Troubleshooting remote actions
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.
Remote actions are not available for users on the TrueSight console
Remote actions are not available on the TrueSight console if you are not a member of the out-of-the-box user group. However, these remote actions are available in the Infrastructure Management server.
Do the following to resolve this issue:
- Add the user group in the following files on the Infrastructure Management server:
- pw/server/etc/cellName/kb/bin/mc_actions.mrl: Add the user group entry for the required remote action.
- Run the following command to recompile cell KB:
mccomp -n cellName
- Restart the Infrastructure Management server.
- Restart the Presentation Server.