Re: [Condor-users] condor_master

[Dan Bradley <dan@xxxxxxxxxxxx>]

Barnett,

You should never have more than one condor_master running using the same 
condor configuration.  That is why when you already have condor_master 
running and you run condor_master by hand, you are seeing it complain 
about "InstanceLock".  It is correctly detecting that there is already 
another master running.  You may ask why it doesn't state this fact in 
plain English.  Good question!

--Dan

Barnett P. Chiu wrote:

> Hi,
>  
>    I used the command "condor_master -f -t" to view log as suggested 
> but somehow got stale log content for a master that no longer exists.
>
> Here is the condor_master currently running with ps uwx:
>
> pleiades  7734  0.2  0.0  7112 3164 ?        S    13:42   0:00 
> condor_master
> pleiades  7735  0.0  0.0  7040 2904 ?        S    13:42   0:00 
> condor_collector -f
> pleiades  7736 11.3  0.0  7676 3340 ?        S    13:42   0:09 
> condor_startd -f
> ...
>
> as you can see Condor master's pid is 7734 whose info is available in 
> MasterLog.
> However, condor_master -f -t shows:
>
> 3/23 21:42:00 ******************************************************
> 3/23 21:42:00 ** condor_master (CONDOR_MASTER) STARTING UP
> 3/23 21:42:00 ** /home/condor/sbin/condor_master
> 3/23 21:42:00 ** $CondorVersion: 6.8.4 Feb  1 2007 $
> 3/23 21:42:00 ** $CondorPlatform: I386-LINUX_RH9 $
> 3/23 21:42:00 ** PID = 27254
> 3/23 21:42:00 ** Log last touched time unavailable (Success)
> 3/23 21:42:00 ******************************************************
> 3/23 21:42:00 Using config source: 
> /usatlas/u/pleiades/test/condor_debug/gridui03.d/condor_config
> 3/23 21:42:00 Using local config sources:
> 3/23 21:42:00    
> /usatlas/u/pleiades/test/condor_debug/gridui03.d/condor_config.local
> 3/23 21:42:00 Attempting to lock 
> /usatlas/u/pleiades/test/condor_debug/gridui03.d/log/InstanceLock.
> 3/23 21:42:00 FileLock::obtain(1) failed - errno 11 (Resource 
> temporarily unavailable)
> 3/23 21:42:00 ERROR "Can't get lock on 
> "/usatlas/u/pleiades/test/condor_debug/gridui03.d/log/InstanceLock"" 
> at line 978 in file master.C
>
> Could this log (shown above) be stale information still held in 
> collector?
>
>
>
> And, by the way, what would cause the error message: can't get lock on 
> a diretory (as shown in the last line of the stale log messages)?
>
>
> Thank you.
>
>
> ~Barnett
>
>
> */Ian Stokes-Rees <ijstokes@xxxxxxxxxxxxxxxxxxx>/* wrote:
>
>     It would be nice if these options were documented on the man page. 
>
>     Dan Bradley wrote:
>
> > > Where
> > > do I find logging output?  Can I get condor to log to stdout?  
> > > Any ideas why it refuses to start?
> > >    
> > condor_master -f -t
> >  
>     Ian
>
> --
> Ian Stokes-Rees                            W: http://sbgrid.org
> ijstokes@xxxxxxxxxxxxxxxxxxx               T: +1 617 418-4168
> SBGrid, Harvard Medical School             F: +1 617 432-5600
>
>    
>
>     _______________________________________________
>     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/
>
>
> ------------------------------------------------------------------------
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try 
> it now. 
> <http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ%20> 
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/
>