[Swift-devel] SWIFT jobs in C/X states on uc3-sub

[Michael Wilde]

My jobs must be fossils; David, Yadu, we should test whether and why Swift doesnt always clean up.

I realize that if Swift hangs and needs to be SIGKILL'ed then it cant.  But lets see if the Condor provider is cleaning up when Swift gets a catchable signal.

Lincoln, lease remove the "wilde" jobs if you can do that.

Thanks,

- Mike

----- Original Message -----
> From: "Lincoln Bryant" <lincolnb at uchicago.edu>
> To: "David Kelly" <davidk at ci.uchicago.edu>
> Cc: "Michael Wilde" <wilde at mcs.anl.gov>
> Sent: Wednesday, March 20, 2013 11:26:30 AM
> Subject: SWIFT jobs in C/X states on uc3-sub
> 
> Hi David / Mike,
> 
> I notice there are a lot of old jobs sitting in the UC3 queue.
> They're sitting in either "X" (removed) or "C" (completed). Sample
> below:
> 
> > 70980.0   wilde           3/12 11:42   0+00:18:59 C  0   43.9 perl
> > cscript906755
> > 70981.0   wilde           3/12 11:42   0+00:03:14 C  0   46.4 perl
> > cscript906755
> > 70982.0   wilde           3/12 11:42   0+00:03:14 C  0   46.4 perl
> > cscript906755
> 
> > 71652.0   davidk          3/13 19:28   0+00:00:01 X  0   0.0  perl
> > cscript500002
> > 71653.0   davidk          3/13 19:28   0+00:00:01 X  0   0.0  perl
> > cscript500002
> > 71896.0   davidk          3/13 19:38   0+00:00:01 X  0   0.0  perl
> > cscript339551
> 
> Are these jobs completing OK on your side?
> 
> Occasionally I go in and purge old jobs, but I'm curious if there's
> something in your submit files that is causing them to stick.
> 
> Cheers,
> Lincoln