Re: [Condor-users] an odd situation

[Dan Bradley <dan@xxxxxxxxxxxx>]

Until this is somehow addressed by Condor internally, you should be able 
to work around the problem by running condor_reconfig -all after the 
credd has started up.

--Dan

Matthew Farrellee wrote:
> When the condor_startd starts it launches a condor_starter with a 
> special argument (-classad). The condor_starter prints out a class ad 
> that the condor_startd then advertises. If the condor_credd starts after 
> the condor_starter -classad is run, you'll be missing the LocalCredd.
>
> This could be fixed by having the condor_startd periodically run 
> condor_starter -classad, if that isn't already happening.
>
> Best,
>
>
> matt
>
> Dan Bradley wrote:
>   
> > If all that matters is the order in which you start up your daemons, to 
> > determine whether things work or not, this sounds like a Condor bug to 
> > me.  I'll ask some of the people more knowledgeable about this portion 
> > of the code.
> >
> > --Dan
> >
> > caipeng wrote:
> >
> >     
> > > thank you .
> > > Yes ,you are right .
> > > An excuting node without LocalCredd attributes has configure file as 
> > > follows:
> > > <snip>
> > >
> > > The two configure files are almost the same,why a node can get LocalCredd 
> > > and another can not?
> > >
> > > If you have leisure ,please help me analyze this problem.
> > >
> > > Thank you again.
> > >
> > >
> > > ----- Original Message ----- 
> > > From: "Dan Bradley" <dan@xxxxxxxxxxxx>
> > > To: "Condor-Users Mail List" <condor-users@xxxxxxxxxxx>
> > > Sent: Monday, July 07, 2008 10:53 PM
> > > Subject: Re: [Condor-users] an odd situation
> > >
> > >
> > >  
> > >
> > >       
> > > > When you start up your pool in the order that doesn't work, does
> > > > condor_status -long show that the machine ClassAds are lacking the
> > > > LocalCredd attribute?
> > > >
> > > > --Dan
> > > >
> > > > caipeng wrote:
> > > >
> > > >    
> > > >
> > > >         
> > > > > Hi condor-users!
> > > > > My central condor master is on Windows 2003 Server,on which I can
> > > > > submit job but can't execute job;There are two excuting nodes which
> > > > > are also intalled Windows 2003 in the pool . I found that if first
> > > > > started two excuting nodes and after that started the condor master ,
> > > > > the job which submited from central condor master as RUN_AS_OWNER
> > > > > cound't work.
> > > > > The feedback was
> > > > > "019.000: Run analysis summary. Of 16 machines,
> > > > > 16 are rejected by your job's requirements
> > > > > 0 reject your job because of their own requirements
> > > > > 0 match but are serving users with a better priority in the pool
> > > > > 0 match but reject the job for unknown reasons
> > > > > 0 match but will not currently preempt their existing job
> > > > > 0 are available to run your job
> > > > > No successful match recorded.
> > > > > Last failed match: Fri Jul 04 19:48:18 2008
> > > > > Reason for last match failure: no match found
> > > > > WARNING: Be advised:
> > > > > No resources matched request's constraints
> > > > > Check the Requirements expression below:
> > > > > Requirements = (Arch == "INTEL") && (OpSys == "WINNT52") && (Disk >=
> > > > > DiskUsage)
> > > > > && ((Memory * 1024) >= ImageSize) && (HasFileTransfer) &&
> > > > > (HasWindowsRunAsOwner
> > > > > && (LocalCredd =?= "clusterman.mc.com:9620"))
> > > > > "
> > > > > Howerver,if I firsted started central master and later started two
> > > > > excuting nodes,everythings worked well.
> > > > > Who could explain the situation?
> > > > > Thanks.
> > > > >
> > > > > ------------------------------------------------------------------------
> > > > >
> > > > > _______________________________________________
> > > > > Condor-users mailing list
> > > > > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> > > > > subject: Unsubscribe
> > > > > You can also unsubscribe by visiting
> > > > > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> > > > >
> > > > > The archives can be found at:
> > > > > https://lists.cs.wisc.edu/archive/condor-users/
> > > > >
> > > > >
> > > > >      
> > > > >
> > > > >           
> > > > _______________________________________________
> > > > Condor-users mailing list
> > > > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> > > > subject: Unsubscribe
> > > > You can also unsubscribe by visiting
> > > > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> > > >
> > > > The archives can be found at:
> > > > https://lists.cs.wisc.edu/archive/condor-users/
> > > >
> > > >    
> > > >
> > > >         
> > > _______________________________________________
> > > Condor-users mailing list
> > > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> > > subject: Unsubscribe
> > > You can also unsubscribe by visiting
> > > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> > >
> > > The archives can be found at: 
> > > https://lists.cs.wisc.edu/archive/condor-users/
> > >  
> > >
> > >       
> > _______________________________________________
> > Condor-users mailing list
> > To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> > subject: Unsubscribe
> > You can also unsubscribe by visiting
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >
> > The archives can be found at: 
> > https://lists.cs.wisc.edu/archive/condor-users/
> >     
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
> The archives can be found at: 
> https://lists.cs.wisc.edu/archive/condor-users/
>