Re: [Condor-users] condor won't start after yum update

["Jack Fowler" <fowler@xxxxxxxxxxxxx>]

Thanks for both of your replies. Yes, that was the problem. I killed <pid> condor_master and now it starts. Cheers.

> -----Original Message-----
> From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-
> bounces@xxxxxxxxxxx] On Behalf Of Cathrin Weiss
> Sent: Friday, November 05, 2010 11:57 AM
> To: Condor-Users Mail List
> Subject: Re: [Condor-users] condor won't start after yum update
> 
> The instance lock prevents you from starting multiple instances of
> Condor (almost as the name indicates). Have you made sure that no older
> condor_master is still running?
> 
> 
> >   I updated condor to 7.4.4-1 and it now won't start with this error message in
> /var/log/condor/MasterLog :
> >
> > 11/05 11:05:30 FileLock::obtain(1) failed - errno 11 (Resource temporarily
> unavailable)
> > 11/05 11:05:30 ERROR "Can't get lock on "/var/lock/condor/InstanceLock"" at
> line 956 in file master.cpp
> >
> > Has anyone seen this before?
> 
> 
> --
> Cathrin Weiss
> Condor Project
> _______________________________________________
> 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/