Mailing List Archives

Public Access

 		[Computer Systems Lab]

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

RE: [Condor-users] condor installation... config questions...

hi...

in trying to install condor on a single linux rh8.0 box. i've done a rpm
install.

when i do a ps -ef | egrep condor_

i see plenty of condor processes....

however, when i run 'condor_master', i get an error that states:
[root@lserver5 root]# condor_master
ERROR: Can't read config file
/opt/condor-6.6.6/local.lserver2/condor_config.local

any idea as to what i'm doing wrong, or what mistake i've made in the config
file.

i'm creating a test network using machines which are on a local/192.168.1.*
network behind a firewall...

thanks

-bruce

ps. if possible, could someone post/email me a copy of an actual working
config file for both a master/client server....??

-------------------------------------------------------------------

i've configured the condor config file as:

######################################################################
######################################################################
##
##  ######                                     #
##  #     #    ##    #####    #####           ##
##  #     #   #  #   #    #     #            # #
##  ######   #    #  #    #     #              #
##  #        ######  #####      #              #
##  #        #    #  #   #      #              #
##  #        #    #  #    #     #            #####
##
##  Part 1:  Settings you must customize:
######################################################################
######################################################################

##  What machine is your central manager?
CONDOR_HOST     = lserver2

##--------------------------------------------------------------------
##  Pathnames:
##--------------------------------------------------------------------
##  Where have you installed the bin, sbin and lib condor directories?
RELEASE_DIR             = /opt/condor-6.6.6/etc

##  Where is the local condor directory for each host?
LOCAL_DIR               = $(TILDE)
#LOCAL_DIR              = $(RELEASE_DIR)/hosts/$(HOSTNAME)

##  Where is the machine-specific local config file for each host?
#LOCAL_CONFIG_FILE      = $(LOCAL_DIR)/condor_config.local
LOCAL_CONFIG_FILE = /opt/condor-6.6.6/local.lserver2/condor_config.local

## If the local config file is not present, is it an error?
## WARNING: This is a potential security issue.
## If not specificed, te default is True
#REQUIRE_LOCAL_CONFIG_FILE = TRUE

##--------------------------------------------------------------------
##  Mail parameters:
##--------------------------------------------------------------------
##  When something goes wrong with condor at your site, who should get
##  the email?
CONDOR_ADMIN            = bedouglas@xxxxxxxxxxxxx

##  Full path to a mail delivery program that understands that "-s"
##  means you want to specify a subject:
MAIL                    = /usr/bin/mail

##--------------------------------------------------------------------
##  Network domain parameters:
##--------------------------------------------------------------------
##  Internet domain of machines sharing a common UID space.  If your
##  machines don't share a common UID space, use the second entry
##  which specifies that each machine has its own UID space.
UID_DOMAIN              = lserver2
#UID_DOMAIN             = $(FULL_HOSTNAME)

##  Internet domain of machines sharing a common file system.
##  If your machines don't use a network file system, use the second
##  entry which specifies that each machine has its own file system.
FILESYSTEM_DOMAIN       = lserver2
#FILESYSTEM_DOMAIN      = $(FULL_HOSTNAME)


######################################################################
######################################################################
##
##  ######                                   #####
##  #     #    ##    #####    #####         #     #
##  #     #   #  #   #    #     #                 #
##  ######   #    #  #    #     #            #####
##  #        ######  #####      #           #
##  #        #    #  #   #      #           #
##  #        #    #  #    #     #           #######
##
##  Part 2:  Settings you may want to customize:
##  (it is generally safe to leave these untouched)
######################################################################
######################################################################

##--------------------------------------------------------------------
##  Flocking: Submitting jobs to more than one pool
##--------------------------------------------------------------------
##  Flocking allows you to run your jobs in other pools, or lets
##  others run jobs in your pool.
##
##  To let others flock to you, define FLOCK_FROM.
##
##  To flock to others, define FLOCK_TO.

##  FLOCK_FROM defines the machines where you would like to grant
##  people access to your pool via flocking. (i.e. you are granting
##  access to these machines to join your pool).
FLOCK_FROM =
##  An example of this is:
#FLOCK_FROM = somehost.friendly.domain, anotherhost.friendly.domain

##  FLOCK_TO defines the central managers of the pools that you want
##  to flock to. (i.e. you are specifying the machines that you
##  want your jobs to be negotiated at -- thereby specifying the
##  pools they will run in.)
FLOCK_TO =
##  An example of this is:
#FLOCK_TO = central_manager.friendly.domain, condor.cs.wisc.edu

##  FLOCK_COLLECTOR_HOSTS should almost always be the same as
##  FLOCK_NEGOTIATOR_HOSTS (as shown below).  The only reason it would be
##  different is if the collector and negotiator in the pool that you are
##  flocking too are running on different machines (not recommended).
##  The collectors must be specified in the same corresponding order as
##  the FLOCK_NEGOTIATOR_HOSTS list.
FLOCK_NEGOTIATOR_HOSTS = $(FLOCK_TO)
FLOCK_COLLECTOR_HOSTS = $(FLOCK_TO)
## An example of having the negotiator and the collector on different
## machines is:
#FLOCK_NEGOTIATOR_HOSTS = condor.cs.wisc.edu,
condor-negotiator.friendly.domain
#FLOCK_COLLECTOR_HOSTS =  condor.cs.wisc.edu,
condor-collector.friendly.domain

##--------------------------------------------------------------------
##  Host/IP access levels
##--------------------------------------------------------------------
##  Please see the administrator's manual for details on these
##  settings, what they're for, and how to use them.

##  What machines have administrative rights for your pool?  This
##  defaults to your central manager.  You should set it to the
##  machine(s) where whoever is the condor administrator(s) works
##  (assuming you trust all the users who log into that/those
##  machine(s), since this is machine-wide access you're granting).
HOSTALLOW_ADMINISTRATOR = $(CONDOR_HOST)

##  If there are no machines that should have administrative access
##  to your pool (for example, there's no machine where only trusted
##  users have accounts), you can uncomment this setting.
##  Unfortunately, this will mean that administering your pool will
##  be more difficult.
#HOSTDENY_ADMINISTRATOR = *

##  What machines should have "owner" access to your machines, meaning
##  they can issue commands that a machine owner should be able to
##  issue to their own machine (like condor_vacate).  This defaults to
##  machines with administrator access, and the local machine.  This
##  is probably what you want.
HOSTALLOW_OWNER = $(FULL_HOSTNAME), $(HOSTALLOW_ADMINISTRATOR)

##  Read access.  Machines listed as allow (and/or not listed as deny)
##  can view the status of your pool, but cannot join your pool
##  or run jobs.
##  NOTE: By default, without these entries customized, you
##  are granting read access to the whole world.  You may want to
##  restrict that to hosts in your domain.  If possible, please also
##  grant read access to "*.cs.wisc.edu", so the Condor developers
##  will be able to view the status of your pool and more easily help
##  you install, configure or debug your Condor installation.
##  It is important to have this defined.
HOSTALLOW_READ = 192.168.1.*
#HOSTALLOW_READ = *.your.domain, *.cs.wisc.edu
#HOSTDENY_READ = *.bad.subnet, bad-machine.your.domain, 144.77.88.*

##  Write access.  Machines listed here can join your pool, submit
##  jobs, etc.  Note: Any machine which has WRITE access must
##  also be granted READ access.  Granting WRITE access below does
##  not also automatically grant READ access; you must change
##  HOSTALLOW_READ above as well.
##  If you leave it as it is, it will be unspecified, and effectively
##  it will be allowing anyone to write to your pool.
HOSTALLOW_WRITE = 192.168.1.*
#HOSTALLOW_WRITE = *.your.domain, your-friend's-machine.other.domain
#HOSTDENY_WRITE = bad-machine.your.domain

##  Negotiator access.  Machines listed here are trusted central



-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx]On Behalf Of Alain Roy
Sent: Wednesday, October 06, 2004 3:30 PM
To: Condor-Users Mail List
Subject: RE: [Condor-users] condor installation... config questions...



>this should be the name of my box..
>#CONDOR_HOST    = central-manager-hostname.your.domain
>CONDOR_HOST    = lserver2 (can i also use ip address)?

While it can be your IP address, please note that Condor requires that DNS
is working and that it can resolve IP addresses to names and vice-versa.
Given that DNS is required, you might as well use the name instead of the
IP address.

>RELEASE_DIR             = /usr/local/condor
>(i don't have a '/usr/local/condor' dir, should i create one, and copy the
>bin/sbin/lib dirs to it, or just replace this with the parent location of
>the dirs..?

Replace /usr/local/condor with wherever you installed Condor. But first,
check your condor_config.local to see if RELEASE_DIR was overridden. The
installation process normally sets this up correctly.

>LOCAL_DIR               = $(TILDE)
>#LOCAL_DIR              = $(RELEASE_DIR)/hosts/$(HOSTNAME)
>(i'm completely confused by what should be here!!!!!)

Have you read what the manual says about it?

http://www.cs.wisc.edu/condor/manual/v6.6/3_3Configuration.html#SECTION00432
000000000000000

Also, check to see if your condor_config.local file overrides this. The
installation process normally sets this up correctly.

>UID_DOMAIN              = your.domain      (lserver2)
>#UID_DOMAIN             = $(FULL_HOSTNAME)
>(???? what should, if anything, go here...)
>(what is meant by full_hostname)

If it was filled in with your.domain, then you don't have DNS set up
correctly.

Read this part of the manual for more information about UID_DOMAIN and
FILESYSTEM_DOMAIN:

http://www.cs.wisc.edu/condor/manual/v6.6/3_3Configuration.html#sec:Shared-F
ilesystem-Config-File-Entries

-alain


_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
http://lists.cs.wisc.edu/mailman/listinfo/condor-users