LSF Known Issues and Workarounds

The following are known issues. Workarounds are noted when available:

• Desktop or remote machine cannot have multiple IP addresses. This is unsupported.
• Core dump files may appear when a job has finished running. Results are still computed correctly. Workaround: Limit size of core dumps to 0 through the following job submit option: bsub -C 0 -n <number-of-cores> -q <queue-name>
• Firewall should be turned off on all machines in the cluster.
• Sometimes LSF ends a job (for example, a job may be preempted due to a high priority job). This may result in the presence of a .lock file in the project directory. You must manually delete the .lock file before continuing with further analysis.
• When an LSF job is ended, MainWin services (watchdog, regss, and mwrcpss) could keep running. The result is that later jobs cannot start on the machine. The fix is to end these processes before starting a new job.
• Analysis fails abruptly when running out of resources (cpu/memory/disk). Ensure sufficient resources are provided.