Re: [Condor-users] Schedd and Startd crashes

[Stuart Anderson <anderson@xxxxxxxxxxxxxxxx>]

If the schedd is exiting due to lack of disk space in the log directory
you should see a 0-byte file in that directory named "dprintf_failure.SCHEDD".
At least that is what happenend on our pool earlier this morning running 6.8.4.

On Tue, May 22, 2007 at 05:45:32PM -0700, Rick Lan wrote:
> Hm, Condor Log directory is on local drive. Both local drives have more
> than 8gig of free space. The log file is set to rotate every 2MB.
> Anything else I should check?
> 
> Thanks
> Rick
> 
> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Todd Tannenbaum
> Sent: Saturday, May 19, 2007 9:17 AM
> To: condor-users@xxxxxxxxxxx
> Subject: Re: [Condor-users] Schedd and Startd crashes
> 
> Re the below: an exit status of 44 means a failure writing the debug log
> (aka the ScheddLog etc).  Perhaps every so often these machines are
> running out of disk space?  Or if you have the Condor Log directory on a
> shared filesystem, perhaps these machines loose the mount every so
> often?
> 
> Hope this helps.

-- 
Stuart Anderson  anderson@xxxxxxxxxxxxxxxx
http://www.ligo.caltech.edu/~anderson