Re: [Condor-users] Scheduler : job staying idle when submited onlyonce or twice

["Fabrice Bouye" <FabriceB@xxxxxxx>]

> After a bit of Google searching I found a possible reason for this happening--that with a single job

> it is automatically sent to the machine that submitted the job [ i.e. the local machine] which is having

> problems.  

 

That seems an odd behavior to me as the submitting machine is logically busy (claimed by its user) and cannot run the job at the time it's being submitted. On the other hand my colleague told me he had a single condor job that stayed up for 3 days before it cancelled it, so that includes night-time when the machine should have been available to the condor pool. Of course the very same job was dispatched and executed properly when submitted several times.

 

 > What kind of jobs are you sending? Have you tried submitting a single job in the vanilla universe to see if it works?

I'm just running test jobs on the behalf of my colleague, all in the vanilla universe. My current test script just copies a zipped R archive and unzip it.

----
Fabrice Bouyé (http://fabricebouye.cv.fm/)
Research Officer (Data)
Tel: +687 26 20 00 (Ext 411)
Oceanic Fisheries, Pacific Community
http://www.spc.int/