Licensing

Licensing

New user facing error when trying to connect to a working HPC configuration via RSM. System.Security.SecurityException: Failed to spawn CommandExpectProcess

    • FAQFAQ
      Participant

      If a user submits a job to RSM from Workbench and credentials have not yet been cached for the RSM queue in RSM or the cached password does not validate because user’s OS password has changed or expired, the user will be prompted to specify credentials for that queue. In this case, user credentials are not being validated on the server side. Here, user can manually cache their credentials for an RSM queue: //ansys_inc/v201/RSM/Config/tools/linux/rsmutils creds c[ache] -a account -rq queue When the user runs the caching command, they will be prompted for the password. For example: /apps/ansys_inc/v201/RSM/Config/tools/linux/rsmutils creds cache -a ansystestuser -rq Fluid1q Caching password for: ansystestuser Enter password: If that does not solve the issue, obtai the following logs from the headnode on the cluster and share with Ansys technical support: /tmp/rsmlauncher201-.log /tmp/rsm_username__pid.log