Re: [Condor-users] old version of condor_master keeps trying to start every 3 minutes

[Dan Bradley <dan@xxxxxxxxxxxx>]

Steve,

It really sounds like something on your system is configured to 
periodically start the master.

If you can't turn that off, I suggest the following:

chmod a-x /opt/condor/sbin/condor_master

--Dan

On 8/11/11 10:39 AM, Steven Platt wrote:
> Hello,
>
> Taking Matts advice I'm upgrading to 7.6.2 and everything's going well
> ... until I had a look at my MasterLog on the master machine.
>
> Without any condor running (confirmed by 'ps aux | grep condor_') the
> following pops up in the MasterLog every 3 minutes
>
> 8/11 16:21:44 ******************************************************
> 8/11 16:21:44 ** condor_master (CONDOR_MASTER) STARTING UP
> 8/11 16:21:44 ** /opt/condor/sbin/condor_master
> 8/11 16:21:44 ** $CondorVersion: 7.0.5 Sep 20 2008 BuildID: 105846 $
> 8/11 16:21:44 ** $CondorPlatform: X86_64-LINUX_RHEL5 $
> 8/11 16:21:44 ** PID = 29397
> 8/11 16:21:44 ** Log last touched 8/11 16:18:45
> 8/11 16:21:44 ******************************************************
> 8/11 16:21:44 Using config source: /home/condor/condor_config
> 8/11 16:21:44 Using local config sources:
> 8/11 16:21:44    /opt/condor/etc/condor_config.local
> 8/11 16:21:44 DaemonCore: Command Socket at<xxx.xxx.xxx.xx:49852>
> 8/11 16:21:44 Usage: /opt/condor/sbin/condor_master [-f] [-t] [-n name]
> 8/11 16:21:44 **** condor_master (condor_MASTER) EXITING WITH STATUS 1
>
> With 7.6.2 successfully started it's this every 3 minutes...
>
> 8/11 16:06:44 ******************************************************
> 8/11 16:06:44 ** condor_master (CONDOR_MASTER) STARTING UP
> 8/11 16:06:44 ** /opt/condor/sbin/condor_master
> 8/11 16:06:44 ** $CondorVersion: 7.0.5 Sep 20 2008 BuildID: 105846 $
> 8/11 16:06:44 ** $CondorPlatform: X86_64-LINUX_RHEL5 $
> 8/11 16:06:44 ** PID = 28695
> 8/11 16:06:44 ** Log last touched 8/11 16:06:13
> 8/11 16:06:44 ******************************************************
> 8/11 16:06:44 Using config source: /home/condor/condor_config
> 8/11 16:06:44 Using local config sources:
> 8/11 16:06:44    /opt/condor/etc/condor_config.local
> 8/11 16:06:44 FileLock::obtain(1) failed - errno 11 (Resource
> temporarily unavailable)
> 8/11 16:06:44 ERROR "Can't get lock on
> "/tmp/condor-lock.queen/InstanceLock"" at line 848 in file master.C
>
> I've trawled through configs&  crontabs and have switched off our
> monitoring service, all to no avail.
> It could be a non-condor problem as we're running on a Rocks cluster
> (v5.1) that was installed by someone ~3 years ago who's since left.
>
> What I do know is that this is probably the cause of the problems
> reported earlier
> https://lists.cs.wisc.edu/archive/condor-users/2011-August/msg00037.shtm
> l
>
> Has anyone come across anything similar?
>
> Thanks
> Steve
> -----------------------------------------
> **************************************************************************
> The information contained in the EMail and any attachments is
> confidential and intended solely and for the attention and use of
> the named addressee(s). It may not be disclosed to any other person
> without the express authority of the HPA, or the intended
> recipient, or both. If you are not the intended recipient, you must
> not disclose, copy, distribute or retain this message or any part
> of it. This footnote also confirms that this EMail has been swept
> for computer viruses, but please re-sweep any attachments before
> opening or saving. HTTP://www.HPA.org.uk
> **************************************************************************
> _______________________________________________
> 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/