Ansys RSM tests not working
I just installed Ansys on a new system to make it an Ansys RSM server. This seems not work. In Workbench I can simulate things. But in the RSM Configuration all queues test in errors. The error is rater vague and I don't know where to find the logs. Where can I find these? What could be causing this?
RSM Version: 188.8.131.52, Build Date: 4/5/2018 11:06:31 AM Job Name: Default Test Job Type: SERVERTEST Client Directory: C:\Users\test_user\AppData\Local\Temp\RsmConfigTest\ggrtsc0j.g0r Client Machine: SRV635 Queue: Default [localhost, default] Template: SERVERTEST Cluster Configuration: localhost [localhost] Cluster Type: ARC Custom Keyword: blank Transfer Option: None Staging Directory: blank Local Scratch Directory: blank Platform: Windows Using SSH for inter-node communication on cluster Cluster Submit Options: blank Normal Inputs: [*,commands.xml,*.in] Cancel Inputs: [-] Excluded Inputs: [-] Normal Outputs: [*] Failure Outputs: [-] Cancel Outputs: [-] Excluded Outputs: [-] Inquire Files: normal: [*] inquire: [*.out] Submission in progress... Runtime Settings: Job Owner: DASTUD\test_user Submit Time: Friday, October 16, 2020 6:16 AM Directory: C:\Users\test_user\AppData\Local\Temp\RsmConfigTest\ggrtsc0j.g0r 2.76 KB, .05 sec (58.81 KB/sec) Submission in progress... Submission in progress... JobType is: SERVERTEST Final command platform: AllWindows RSM_PYTHON_HOME=C:\Program Files\ANSYS Inc\v191\commonfiles\CPython\2_7_13\winx64\Release\python RSM_HPC_JOBNAME=RSMTest Distributed mode requested: True RSM_HPC_DISTRIBUTED=TRUE Running 5 commands Job working directory: C:\Users\test_user\AppData\Local\Temp\RsmConfigTest\ggrtsc0j.g0r Number of CPU requested: 1 AWP_ROOT191=C:\Program Files\ANSYS Inc\v191 Testing writability of working directory... C:\Users\test_user\AppData\Local\Temp\RsmConfigTest\ggrtsc0j.g0r If you can read this, file was written successfully to working directory Writability test complete Checking queue default exists ... JobId was parsed as: 25 Job was not run on the cluster. Check the cluster logs and check if the cluster is configured properly. Job was not run on the cluster. Check the cluster logs and check if the cluster is configured properly. No files transferred.