[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

On Fri, Nov 5, 2010 at 11:52 AM, Jack Fowler <fowler@xxxxxxxxxxxxx> wrote:
 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?

I haven't but it looks like either Condor just didn't get shut down properly or the update updated your condor_config and pointed the lock file to a new location. Check to make sure there are no condor processes running:

  ps -ef | grep condor

And then:

  rm -rf /var/lock/condor/InstanceLock

If that path/file doesn't exist, create it:

  mkdir -p /var/lock/condor

- Ian