Ansys Products

Ansys Products

Discuss installation & licensing of our Ansys Teaching and Research products.

licensing problem while using remote PBS cluster

    • komanek
      Subscriber

      Hi,

      I'm trying to solve the problem with upgrade to 2024R2.02. Upgraded license manager, still works for the older Ansys versions both solving on local desktop or PBS cluster. Version 2024R2.02 works only when the solver is executed on the user's desktop, but not through PBS. The task is uploaded to the compute node, started, bud ends with exit code 7, claiming the licenses are not available.

      Command Exit Code: 7
      Saving exit code file: /ansys/scratch/komanek/kvjiqlkg.6fw/exitcode_284d9a72-76ea-4895-9ca7-b77b9506f91e.rsmout
          Exit code file: /ansys/scratch/komanek/kvjiqlkg.6fw/exitcode_284d9a72-76ea-4895-9ca7-b77b9506f91e.rsmout has been created.
      Saving exit code file: /scratch-fast/komanek/kvjiqlkg.6fw/exitcode_284d9a72-76ea-4895-9ca7-b77b9506f91e.rsmout
          Exit code file: /scratch-fast/komanek/kvjiqlkg.6fw/exitcode_284d9a72-76ea-4895-9ca7-b77b9506f91e.rsmout has been created.
      Saving exit code file: /ansys/scratch/komanek/kvjiqlkg.6fw/exitcodeCommands_284d9a72-76ea-4895-9ca7-b77b9506f91e.rsmout
          Exit code file: /ansys/scratch/komanek/kvjiqlkg.6fw/exitcodeCommands_284d9a72-76ea-4895-9ca7-b77b9506f91e.rsmout has been created.
      Saving exit code file: /scratch-fast/komanek/kvjiqlkg.6fw/exitcodeCommands_284d9a72-76ea-4895-9ca7-b77b9506f91e.rsmout
          Exit code file: /scratch-fast/komanek/kvjiqlkg.6fw/exitcodeCommands_284d9a72-76ea-4895-9ca7-b77b9506f91e.rsmout has been created.
      solve -->
      solve -->  ANSYS LICENSE MANAGER ERROR:
      solve -->  Request name ansys does not exist in the licensing pool.
      solve -->
      solve -->  *** ERROR - ANSYS license not available.

      License server is accessible from the compute node with no network issues (e.g. ansys_inc/v242/licensingclient/linx64/lmutil lmstat -c 1055@licsrv -a ), in the license server logs I also see "ins" and "outs" for my username, but still, the resulting state is error.

      16:19:25 (ansyslmd) OUT: "ansys" komanek@komanek-ipp-cas-cz  [135598] 
      16:22:55 (ansyslmd) IN: "ansys" komanek@komanek-ipp-cas-cz  [135598] 
      16:30:52 (ansyslmd) (@ansyslmd-SLOG@) 00000001 ms at Tue Oct 01 2024 16:16:19 CEST,#12,(komanek,komanek-ipp-cas-cz,38)
      16:30:52 (ansyslmd) (@ansyslmd-SLOG@) 00000001 ms at Tue Oct 01 2024 16:16:19 CEST,#12,(komanek,komanek-ipp-cas-cz,38)
      16:30:52 (ansyslmd) (@ansyslmd-SLOG@) 00000001 ms at Tue Oct 01 2024 16:16:19 CEST,#12,(komanek,komanek-ipp-cas-cz,38)
      16:30:52 (ansyslmd) (@ansyslmd-SLOG@) 00000001 ms at Tue Oct 01 2024 16:16:19 CEST,#12,(komanek,komanek-ipp-cas-cz,38)
      16:30:52 (ansyslmd) (@ansyslmd-SLOG@) 00000001 ms at Tue Oct 01 2024 16:16:19 CEST,#12,(komanek,komanek-ipp-cas-cz,38)
      16:33:06 (ansyslmd) OUT: "ansys" komanek@komanek-ipp-cas-cz  [143231] 
      16:36:25 (ansyslmd) IN: "ansys" komanek@komanek-ipp-cas-cz  [143231] 

      So the problem is there only if I use Ansys 2024 and only if it is passed through PBS. Versions 2021-2023 work well on the same compute nodes. Both Ansys and License Manager are fully updated, RSM configuration and queue handling is working.

      Does anybody had this problem? Or do you know how to trace/diagnose this kind of version specic problem?

      Thanks,

        David

       

    • komanek
      Subscriber

      Finally I managed to solve this. Ansys workbench doesn't pass the license information to the remotely executed solver, not even the location of the license server. All the communication with the license server was from the workbench, while nodes tried to contact localhost. It was not obvoius from the job logs..

      I had to create a file ansys_inc/shared_files/licensing/ansyslmd.ini manualy, since it is not created at the time of ansys installation (tested on two different linux computers), which seems was working better in previous versions of ansys.

       

Viewing 1 reply thread
  • You must be logged in to reply to this topic.