[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Condor-users] weird reason for held job
- Date: Wed, 15 Dec 2010 14:38:27 -0600
- From: Dennis Box <dbox@xxxxxxxx>
- Subject: [Condor-users] weird reason for held job
I can create a condor job which gets held almost immediately after
[dbox@gpsn01 ~]$ condor_q dbox
-- Submitter: gpsn01.fnal.gov : <220.127.116.11:60205> : gpsn01.fnal.gov
ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD
2070.0 dbox 12/15 13:58 0+00:00:00 H 0 0.0
Looking deeper into why it is held:
[dbox@gpsn01 ~]$ condor_q -l 2070.0 | grep HoldReason
LastHoldReason = "Error from slot2@xxxxxxxxxxxxxxxx: Failed to execute
with arguments 360: No such file or directory"
LastHoldReasonCode = 6
LastHoldReasonSubCode = 2
Here's the weird part: I ssh to the machine where the error occurs and
look at it, the file seems to be fine!
[dbox@gpwn002 ~]$ ls -la
-rwxr-xr-x 1 dbox gpcf 800 Dec 15 13:57
Any suggestions on how to proceed to debug this?