HTCondor Project List Archives



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

[Condor-devel] Installation issues.



Hi there, condor-devel, it's me again.  I've been going through the
condor installation process pretty carefully, and have found some
problems with condor_configure (v6.6.9) that you ought to know about.

I wanted to use condor_configure to set up my central manager.  I
invoked it thusly:

$ ./condor_configure --install --install-dir=/home/condor/demopool/
--local-dir=/scratch/condor/demopool/ --type="submit,execute,manager"

It worked.  Cool, I thought.  I started the daemons.  They appeared to
be running.  Cool again.  But wait...the startd is gone.  From the log:

6/2 14:55:48 ******************************************************
6/2 14:55:48 ** condor_startd (CONDOR_STARTD) STARTING UP
6/2 14:55:48 ** /abode/condor/demopool/sbin/condor_startd
6/2 14:55:48 ** $CondorVersion: 6.6.9 Mar 10 2005 $
6/2 14:55:48 ** $CondorPlatform: I386-LINUX_RH9 $
6/2 14:55:48 ** PID = 15748
6/2 14:55:48 ******************************************************
6/2 14:55:48 Using config file: /abode/condor/demopool/etc/condor_config
6/2 14:55:48 Using local config files:
/scratch/condor/demopool//condor_config.local
6/2 14:55:48 DaemonCore: Command Socket at <192.168.25.191:59762>
6/2 14:55:55 ERROR "Required attribute "START" is not defined" at line
252 in file util.C

Huh?

$ condor_config_val START
Not defined: START

No, it's really not there.  Turns out, it is specifically set to nothing
in condor_config.local:

$ cat /scratch/condor/demopool/condor_config.local | grep "^START"
START =

Checking out condor_configure around line 156:

-----------------------------------
elsif (defined($opt_type)) {

    my @types=split(/\,/, $opt_type);
    my $daemon_list="MASTER";

    $local_config{START}="";
    $local_config{PREEMPT}="";
    $local_config{SUSPEND}="";
    $local_config{VACATE}="";
    $local_config{COLLECTOR_NAME}="";
-----------------------------------

START (and all those other variables) are specifically set to nothing,
and then are never modified.  (I took a brief look at v6.7.6 and believe
this problem exists there, too.)  Not setting them at all would probably
avoid this issue.

My second comment is that I was disappointed that no changes were made
to the global config file - only the local config file.  Since I was
installing the central manager explicitly, this would have been an ideal
time to set RELEASE_DIR, LOCAL_DIR, CONDOR_HOST, etc in the global
config file.  Relegating it to the local config file only creates more
work for the (poor beleaguered) user.

I'm now going to go beat on condor_install.  :-)  Wish me luck...

-Mike