Re: [Condor-users] Job continually being run due toshadowexceptionerrors.

[<Greg.Hitchen@xxxxxxxx>]

> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx 
> [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Jaime Frey
> Sent: Thursday, 16 February 2006 11:00 PM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] Job continually being run due 
> toshadowexceptionerrors.
> 
> 
> On Feb 16, 2006, at 1:28 AM, <Greg.Hitchen@xxxxxxxx>  
> <Greg.Hitchen@xxxxxxxx> wrote:
> 
> > This doesn't appear to add any extra logging info.
> >
> > Have I used the correct option?
> >
> >> I have enabled the ALL_DEBUG = D_FULLDEBUG option in the 
> config file 
> >> but am waiting for the changes to percolate around the pool (our 
> >> install script creates a scheduled task that runs daily and checks 
> >> our main condor repository for updated binaries and/or 
> config files).
> 
> Did you run condor_reconfig on all of the machines after the change? 

Yep, our script that checks for new binaries and/or config files
copies them across, and then restarts the condor service.
 
> Did all of the individual daemons already have D_FULLDEBUG enabled  
> (config parameters SCHEDD_DEBUG, STARTD_DEBUG, ...)?
> 

No, just the one ALL_DEBUG = D_FULLDEBUG statement at the start of
the config file.