7.14. "Failed command: LaunchProxy. Unable to contact RSM."

Engineering Knowledge Manager

EKM Troubleshooting Guide | Chapter 7: Job Management Issues |

7.13. Cannot run interactive jobs |  | 7.15. Jobs page error: "Could not find the object at /Jobs/File System"
Prev |  | Next

## 7.14. "Failed command: LaunchProxy. Unable to contact RSM."

When starting a job, you may get an error similar to the following:

    Failed command: LaunchProxy. Unable to contact RSM. Please verify RSM Manager service is running.
    Error: No response after waiting for 120000 milliseconds.

In this case you will also see repeated messages similar to the following in the RSM launcher log file (rsmlauncher182-<timestamp>.log):

    2017-03-01 13:04:06 [WARN] Mutex /tmp/UserProxyXmlRpcLock.lock is taking a long time to obtain, but the
    process that is using the mutex is still running ekmtestvm1.ansys.com:::28324:::Ans.Rsm.Launcher. PID 28324
    2017-03-01 13:04:09 [WARN] Mutex /tmp/UserProxyXmlRpcLock.lock is taking a long time to obtain, but the
    process that is using the mutex is still running ekmtestvm1.ansys.com:::28324:::Ans.Rsm.Launcher. PID 28324

To resolve this issue:

1. Stop the RSM launcher service.

2. Remove /tmp/UserProxyXmlRpcLock.lock.

3. Restart RSM.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.