[condor-users] condor_config syntax error

[Daniel Loughlin <loughlin@xxxxxxxxxxxx>]

Hi,

I upgraded condor in my pool from 6.5.2 to 6.6.3. When the condor_master 
daemon restarted condor_startd I received the following error in my log file

4/26 19:08:07 ** condor_startd (CONDOR_STARTD) STARTING UP
4/26 19:08:07 ** $CondorVersion: 6.6.3 Mar 29 2004 $
4/26 19:08:07 ** $CondorPlatform: I386-LINUX-RH72 $
4/26 19:08:07 ** PID = 31279
4/26 19:08:07 ******************************************************
4/26 19:08:07 Using config file: /usr/local/condor/condor_config
4/26 19:08:07 Using local config files: 
/cluster/condor/etc/condor_config.BOB /cluster/condor/etc/host017.local
4/26 19:08:07 DaemonCore: Command Socket at <144.174.160.147:44265>
4/26 19:08:13 ERROR "Syntax error in Rank expression: '((Scheduler =?= 
"DedicatedScheduler@xxxxxxxxxxxxxxxxxxxx" * 1000000) + ) || (Owner == 
"bob")'" at line 361 in file util.C


I believe the relevant line in the condor_config.BOB file is
RANK    = ((Scheduler =?= $(DedicatedScheduler) * $(RANK_FACTOR)) + 
$(RANK)) || (Owner == "BOB")
I assume RANK is not getting a value before this line.
When I added RANK = 0 before this line the daemons started back up.

My question is why would the original configuration work fine in 6.5.2 
but not in 6.6.3?

Thanks,
Danny


The condor_config.BOB file looks like this:

######################################################################
##
##  condor_config.local.dedicated.resource
##
##  This is the default local configuration file for any resources
##  that are going to be configured as dedicated resources in your
##  Condor pool.  If you are going to use Condor's dedicated MPI
##  scheduling, you must configure some of your machines as dedicated
##  resources, using the settings in this file.
##
##  PLEASE READ the discussion on "Configuring Condor for Dedicated
##  Scheduling" in the "Setting up Condor for Special Environments"
##  section of the Condor Manual for more details.
##
##  You should copy this file to the appropriate location and
##  customize it for your needs.  The file is divided into three main
##  parts: settings you MUST customize, settings regarding the policy
##  of running jobs on your dedicated resources (you must select a
##  policy and uncomment the corresponding expressions), and settings
##  you should leave alone, but that must be present for dedicated
##  scheduling to work.  Settings that are defined here MUST BE
##  DEFINED, since they have no default value.
##
######################################################################

######################################################################
######################################################################
##  Settings you MUST customize!
######################################################################
######################################################################

##  What is the name of the dedicated scheduler for this resource?
##  You MUST fill in the correct full hostname where you're running
##  the dedicated scheduler, and where users will submit their
##  dedicated jobs.  The "DedicateScheduler@" part should not be
##  changed, ONLY the hostname.
DedicatedScheduler = "DedicatedScheduler@xxxxxxxxxxxxxxxxxxxx"


######################################################################
######################################################################
##  Policy Settings (You MUST choose a policy and uncomment it)
######################################################################
######################################################################

##  There are three basic options for the policy on dedicated
##  resources:
##  1) Only run dedicated jobs
##  2) Always run jobs, but prefer dedicated ones
##  3) Always run dedicated jobs, but only allow non-dedicated jobs to
##     run on an opportunistic basis.  
##  You MUST uncomment the set of policy expressions you want to use
##  at your site.

##--------------------------------------------------------------------
## 1) Only run dedicated jobs
##--------------------------------------------------------------------
#START        = Scheduler =?= $(DedicatedScheduler)
#SUSPEND    = False
#CONTINUE    = True
#PREEMPT    = False
#KILL        = False
#WANT_SUSPEND    = False
#WANT_VACATE    = False
#RANK        = Scheduler =?= $(DedicatedScheduler)

##--------------------------------------------------------------------
## 2) Always run jobs, but prefer dedicated ones
##--------------------------------------------------------------------
#START        = True
#SUSPEND    = False
#CONTINUE    = True
#PREEMPT    = False
#KILL        = False
#WANT_SUSPEND    = False
#WANT_VACATE    = False
#RANK        = Scheduler =?= $(DedicatedScheduler)

##--------------------------------------------------------------------
## 3) Always run dedicated jobs, but only allow non-dedicated jobs to
##    run on an opportunistic basis.  
##--------------------------------------------------------------------
##  Allowing both dedicated and opportunistic jobs on your resources
##  requires that you have an opportunistic policy already defined.
##  These are the only settings that need to be modified from your
##  existing policy expressions to allow dedicated jobs to always run
##  without suspending, or ever being preempted (either from activity
##  on the machine, or other jobs in the system).

SUSPEND    = Scheduler =!= $(DedicatedScheduler) && ($(SUSPEND))
PREEMPT    = Scheduler =!= $(DedicatedScheduler) && ($(PREEMPT))
RANK_FACTOR    = 1000000
RANK    = ((Scheduler =?= $(DedicatedScheduler) * $(RANK_FACTOR)) + 
$(RANK)) || (Owner == "BOB")
START    = (Scheduler =?= $(DedicatedScheduler)) || ($(START))

##  Note: For everything to work, you MUST set RANK_FACTOR to be a
##  larger value than the maximum value your existing rank expression
##  could possibly evaluate to.  RANK is just a floating point value,
##  so there's no harm in having a value that's very large.


######################################################################
######################################################################
##  Settings you should leave alone, but that must be defined
######################################################################
######################################################################

##  Path to the special version of rsh that's required to spawn MPI
##  jobs under Condor.  WARNING: This is not a replacement for rsh,
##  and does NOT work for interactive use.  Do not use it directly!
MPI_CONDOR_RSH_PATH = $(SBIN)

##  This setting puts the DedicatedScheduler attribute, defined above,
##  into your machine's classad.  This way, the dedicated scheduler
##  (and you) can identify which machines are configured as dedicated
##  resources. 
STARTD_EXPRS = $(STARTD_EXPRS), DedicatedScheduler





Condor Support Information:
http://www.cs.wisc.edu/condor/condor-support/
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>