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

Re: [Condor-users] problem starting condor in init.d

I do have a local config file in /opt/condor-6.7.9/local.HOSTNAME/condor_config.local
HOSTNAME is usually something like compute-0-0
this used to work with the previous version I was using 6.6.8 but I probably messed something up when upgrading. I am wondering why upon installation it is now using the "localhost" even though the correct directory of local.compute-0-0 is there with a condor_config.local file in it.


Erik Paulson wrote:

On Wed, Aug 03, 2005 at 02:57:35PM -0400, Ian Chesal wrote:

Hi All,

I am trying to find where the path to condor_config.local is set when
using init.d to start condor. I don't have a local.localhost


and I cannot find any file where this is specified. see below:

#/etc/init.d/condor start
Starting up Condor
ERROR: Can't read config file

The location of the local configuration file is specified in your
condor_config file using the LOCAL_CONFIG_FILE setting.

You can remove the need for a local configuration file by setting:


Or just comment out the setting for LOCAL_CONFIG_FILE. The idea behine REQUIRE_LOCAL_CONFIG_FILE is that you might have a global config file in NFS, and say something like

LOCAL_CONFIG_FILE = /some/path/to/nfs/$(HOSTNAME).local

that way, you don't have to create a local config file for every machine in
your pool, but if you want to it's automatically picked up.

Condor-users mailing list