Difference: TroubleshootingCondor (13 vs. 14)

Revision 142016-05-03 - brodbd

Line: 1 to 1

META TOPICPARENT	name="kill a job"

Troubleshooting Condor Job Problems

Line: 16 to 16

Often this means Condor is having trouble executing the job. Try using condor_q -long and examining the HoldReason attribute. For example: condor_q -global -long 13281 | grep 'HoldReason'.

One particularly common error that some users may find puzzling is "Exec format error." This usually means you've forgotten to include the "shebang" line in a script. While a shebang line is not necessarily required when running a script interactively, Condor needs to see one so it knows what shell or interpreter to use to run the script.

Added:

>
>

condor_submit fails with "no such directory"

Sometimes, usually when working on group projects outside your home directory, condor_submit will fail with an error like

ERROR: No such directory: /projects/foo/bar/biz

This happens when the directory is not owned by you, regardless of whether you have access. (This may be a bug in condor_submit.) If you encounter this, either move the submit script and log file to a directory you own, or contact linghelp@uw to have the directory chown'd to you.

Job runs for a while, then bogs down or gets killed

This often means the job has exceeded its memory request without Condor noticing, and has gotten so large that the machine it's running on has run out of RAM. Check the SIZE column of condor_q and compare to what you've specified on your request_memory line. (The default if you don't specify is 1024 MB.) See BigMemoryCondor and the section below for more information.

View topic | History: r14 < r13 < r12 < r11 | More topic actions...