Hello everyone,
I hope someone can help me.
I’m having issues with the new version of Ansys Mechanical (2025 R1).
The version is correctly installed (just like the previous ones), but from the interactive app I configured, when I select version 2025 R1, I get an error when starting the script.
The submitted job is terminated with exit code 1 (without an apparent reason).
The command executed in the script.sh.erb is as follows: ansys251 -i {input_file} -o {output_name} -b nolist -p ansys -j {name} -dir {output_dir} -np 8 -dmp
Moreover, if the SMP mode is selected in the submission form, everything works fine.
The same command executed from the command line on the compute node runs correctly, as well as when run within a shell script and submitted using the sbatch command.
This sounds like it could be a fairly involved Ansys issue - perhaps there’s some flag & environment combination that’s blowing up. Have you checked out the session data output.log file?
Good evening,
Unfortunately, I am still stuck and unable to find a solution… I am sure I am missing some detail.
The issue persists:
If I run the script.sh directly from the terminal (sbatch script.sh), the run completes successfully, and the ansys251 command executes correctly. script_sh.txt (403 Bytes)
If I submit the job from the interactive app (I am attaching the form, submit, and script) on Open OnDemand, I keep getting an exit code 1 (the ansys251 command is never executed, as evidenced by the fact that the ansys output file is not even created). script_sh_erb.txt (727 Bytes) submit_yml_erb.txt (1.1 KB) form_yml_erb.txt (3.8 KB)
The node where the job is executed is the same in both cases (it is the only one available for the partition used, and I have also checked with scontrol the submitted jobs).
Is there anything different from the simple sbatch command being executed when submitting the job from OOD that I might be missing?
Are there any environment variables instantiated for some reason that could be causing the issue?
Try sbatch --export=NONE script.sh. That more accurately replicates the issue. This is the default in the Slurm support (a choice made long before my time) to export NONE.
To get --export=ALL use copy_environmet: true. Here I’ve added it to the script in your submit.yml.erb file.