HP SVA V1.1 Patch Kit 3 Readme/Release Notes

This is an effective way of ensuring that all pieces of your job go away when your job
exits. However, if you have other processes on that node, even if not started by the job
(for example, when debugging), they are also killed.
• Solution
You can disable the epilog by changing /hptc/slurm/etc/slurm.conf and restarting
SLURM on all nodes using this command:
pdsh -a service slurm restart
Future SVA jobs may not be able to start if processes are left around by previous jobs
and not cleaned up by the epilog. If you don't want the SVA-specific behavior of killing
rgsender processes and removing X server lock files, but you do want to kill processes
owned by the user who ran the job, change the following:
Epilog=/opt/sva/sbin/sva_epilog.clean
To:
Epilog=/opt/hptc/slurm/etc/slurm.epilog.clean
If you don't want any of this cleanup behavior, delete the following line:
Epilog=/opt/sva/sbin/sva_epilog.clean
9. Job Termination: Spurious scanel Warnings
• Impact
Low.
• Summary
Occasionally, jobs end with an warning similar to the following:
scancel: error: Kill job error on job id 431.17: Invalid job id specified
• Solution
This message is harmless and you can ignore it.
The message is an artifact of how job cleanup is done. The cleanup script occasionally
tries to clean parts of the job that didn't start.
10. Environment Variables: path/ld_library_path Conflicts
• Impact
Low.
• Summary
The SVA software adds items to PATH and LD_LIBRARY_PATH environment variables
when the user logs in or starts a shell. If these values are over written, then the SVA
tools will not be able to start.
• Solution
Instead of replacing a PATH/LD_LIBRARY_PATH, you should append any new values
to existing values in the environment variables.
1.4 Known Problems and Limitations 15