Free Courses Fluids Structures 3D Design Electronics Materials Photonics Student Teams STEM Python Missions Indo Kursus My Courses

[FAQ]

This error can be caused by a few different reasons. Essentially this error will happen if the UserProxy process starts but then fails immediately after starting. This failure may happen before a UserProxy log is written out, making it more difficult to debug. The first common reason for this error message is, there is a “zombied” UserProxyProcess already running for the user and was not properly shutdown for whatever reason. To resolve this issue locate the process: ps -ef | grep -i UserProxy. Then manually kill it with “kill ” or “kill -9 ” The second common reason is that something in the user’s environment is preventing a proper start up of the UserProxy process, such as a bad TMPDIR environment variable. To get more information about what that might be, you can start the userproxy process for the user manually, and watch the terminal output (as root): su – -s /bin/csh -c /usr/ansys_inc/v195/RSM/Config/tools/linux/rsmuserproxy -primary _ This will manually launch the user proxy process in a way very similar to how the RSM Launcher process launches them. Here you will get more information from the process itself that may not get written to a log. One common example of an issue we see where an log is not written is when a user modifies their TMPDIR environment variable. Sometimes a user will modify this to a location that is no longer valid. When that happens the UserProxy process fails to be able to write the log file, and dies immediately. So please check the user’s TMPDIR and verify that is set properly.