HP Scalable Visualization Array, V1.1 Readme/Release Notes

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. DMX: DMX Console Breaks SHIFT/control/caps LOCK KEYS
• Impact
Low.
• Summary
Occasionally, the remote machine that displays the DMX Console is left with a non-functioning
SHIFT/CONTROL/CAPS LOCK keys after DMX exits.
• Solution
One solution is to place the following commands into a shell script which can be launched by
typing only lowercase letters, for example, fixkeyboard.sh:
xmodmap -e 'add Control = Control_L'
xmodmap -e 'add Lock = Caps_Lock'
xmodmap -e 'add Shift = Shift_L'
xmodmap -e 'add Shift = Shift_R'
xmodmap -e 'add Control = Control_R'
xmodmap -e "keysym Alt_L = Meta_L Alt_L"
11. DMX: DMX Won't Start Because of Stale x Lock Files
• Impact
Medium.
• Summary
DMX creates a lock file which it uses to make sure only one instance of DMX is running. If this file
is not removed by DMX or the launch script, other users will not be able to launch DMX on that
node.
• Solution
Changes have been made to the DMX launch scripts to reduce the likelihood of this problem.
However, if the clean-up doesn't run, it can prevent DMX from starting.
ssh to the execution node for the job and remove the following files:
a. /tmp/.X11-unix/X1
b. /tmp/.X1-lock
You need to do this as root or the original creator of these files.
Release Notes 11