CREATE THE CONDOR USER, AND UPDATE PASSWORD AND SHADOW FILES ON ALL NODES. [root@node001 root]# adduser condor [root@node001 root]# ssync I [root@node001 root]# cd /usr/local/src [root@node001 src]# tar xvzf condor-6.5.3-linux-x86-glibc22.tar.gz [root@node001 src]# cd condor-6.5.3 [root@node001 condor-6.5.3]# ./condor_install Welcome to condor_install. You are going to need to answer a few questions about how you want Condor configured on this machine, what pool(s) you want to join, and if this machine is going to serve as the Central Manager for its own pool. If you are unsure about how to answer any of the questions asked here, please consult the INSTALL file or the Installation chapter of the Condor Administrator's Manual. The installation is broken down into various steps. Please consult the INSTALL file to refer to a specific step if you have trouble with it. For most questions, defaults will be given in []'s. To accept the default, just press return. If you have problems installing or using Condor, please consult the Condor Administrator's Manual, which can be found on the World Wide Web at: http://www.cs.wisc.edu/condor/manual/ If you still have problems, send email to condor-admin@cs.wisc.edu. Press enter to begin Condor installation ********************************************************************* STEP 1: What type of Condor installation do you want? ********************************************************************* Would you like to do a full installation of Condor? [yes] Press enter to continue. ********************************************************************* STEP 2: How many machines are you setting up for Condor? ********************************************************************* Are you planning to setup Condor on multiple machines? [yes] Will all the machines share files via a file server? [yes] You should run condor_install on your file server, so that root has permission to create files needed by Condor. What are the hostnames of the machines you wish to setup? (Just type the hostnames, not the fully qualified names. Put one machine per line. When you are done, just hit enter.) node001 node002 node003 . . . Setting up Condor for the following machines: node001 node002 node003 ... Press enter to continue. ********************************************************************* STEP 3: Install the Condor "release directory", which holds various binaries, libraries, scripts and files used by Condor. ********************************************************************* which: no condor_config_val in (/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin/ X11:/usr/X11R6/bin:/usr/java/j2re1.4.2/bin:/usr/local/mpich_pgi/bin:/ usr/pgi/linux86/bin:/opt/scali/bin:/opt/scali/sbin:/opt/scali/contrib/ pbs/bin:/root/bin) I can't find a complete Condor release directory. Have you installed a release directory already? [no] Where would you like to install the Condor release directory? [/usr/local/condor] /home/condor Installing a release directory into /home/condor ... etc/ etc/examples/ etc/examples/README etc/examples/condor.generic etc/examples/condor_config.local.central.manager etc/examples/condor_config.local.dedicated.resource etc/examples/condor_config.local.dedicated.submit . . . done. Using /home/condor as the Condor release directory. Press enter to continue. ********************************************************************* STEP 4: How and where should Condor send email if things go wrong? ********************************************************************* If something goes wrong with Condor, who should get email about it? [root@node001.cluster.ornl.gov] What is the full path to a mail program that understands "-s" means you want to specify a subject? [/bin/mail] Using /bin/mail to send email to root@node001.cluster.ornl.gov Press enter to continue. ********************************************************************* STEP 5: Filesystem and UID domains. ********************************************************************* To correctly run all jobs in your pool, including ones that aren't relinked for Condor, you must tell Condor if you have a shared filesystem, and if so, what machines share it. Please read the "Configuring Condor" section of the Administrator's manual (in particular, the section "Shared Filesystem Config File Entries") for a complete explaination of these (and other, related) settings. Do all of the machines in your pool from your domain ("esd.ornl.gov") share a common filesystem? [no] yes Configuring all machines to use "esd.ornl.gov" for their filesystem domain. Do all of the users across all the machines in your domain have a unique UID (in other words, do they all share a common passwd file)? [no] yes Configuring all machines to use "esd.ornl.gov" for their uid domain. In some cases, even if you have unique UIDs, you might not have all users listed in the password file on each machine. Is this the case at your site? [no] Press enter to continue. ********************************************************************* STEP 6: Java Universe support in Condor. ********************************************************************* Enable Java Universe support? [yes] I wasn't able to find a valid JVM. Please enter the full path to the JVM, or "none" to leave unconfigured: /usr/java/j2re1.4.2/bin/java You entered: /usr/java/j2re1.4.2/bin/java Is that right? [no] yes Checking to see if you have a Sun JVM...yes. Using JVM /usr/java/j2re1.4.2/bin/java for Java universe support. Press enter to continue. ********************************************************************* STEP 7: Where should public programs be installed? ********************************************************************* The Condor binaries and scripts are already installed in: /home/condor/bin If you want, I can create some soft links from a directory that is already in the default PATH to point to these binaries, so that Condor users do not have to change their PATH. Alternatively, I can leave them where they are and Condor users will have to add /home/condor/bin to their PATH or explicitly use a full pathname to access the Condor tools. Shall I create links in some other directory? [yes] no Press enter to continue. ********************************************************************* STEP 8: What machine will be your central manager? ********************************************************************* What is the full hostname of the central manager? [node001.cluster.ornl.gov] Your central manager will be on the local machine. Press enter to continue. ********************************************************************* STEP 9: Where will the "local directory" go? ********************************************************************* Each machine in your pool will need a unique directory You have a "condor" user on this machine. Is the home directory for this account (/home/condor) shared among all machines in your pool? [yes] Do you want to put all the Condor directories for each machine in subdirectories of /home/condor/hosts? [yes] Using /home/condor/hosts/[hostname] as the local directory for each host. Creating all necessary Condor directories ... done. Condor needs a few lock files to syncronize access to it's log files. You're using a shared file system for your local Condor directories. Because of problems we've had with file locking over network file systems, we recomend that you specify a directory on a local partition to put these lock files. Do you want to specify a local partition for file locking? [yes] Where should I put the lock files? [/var/lock/condor] /var/lock/condor does not exist. Shall I create it now? [yes] When condor_install completes, you will have to run condor_init on each machine in your pool before you start Condor there. condor_init will create the local lock directory with the right permissions. Press enter to continue. ********************************************************************* STEP 10: Where will the local (machine-specific) config files go? ********************************************************************* Condor allows you to have a machine-specific config file that overrides settings in the global config file. You must specify a machine-specific config file. Do you want all the machine-specific config files for each host in one directory? [yes] What directory should I use? [/home/condor/etc] Naming each config file [hostname].local Creating config files in "/home/condor/etc" ... done. Configuring global condor config file ... done. Created /home/condor/etc/condor_config. Press enter to continue. Setting up node001.cluster.ornl.gov as your central manager What name would you like to use for this pool? This should be a short description (20 characters or so) that describes your site. For example, the name for the UW-Madison Computer Science Condor Pool is: "UW-Madison CS". This value is stored in your central manager's local config file as "COLLECTOR_NAME", if you decide to change it later. (This shouldn't include any " marks). Penguin-Pool Setting up central manager config file /home/condor/etc/node001.local ... done. Press enter to continue. ********************************************************************* STEP 11: How do you want Condor to find its config file? ********************************************************************* Condor searches a few locations to find it main config file. The first place is the envionment variable CONDOR_CONFIG. The second place it searches is /etc/condor/condor_config, and the third place is ~condor/condor_config. Should I put in a soft link from /home/condor/condor_config to /home/condor/etc/condor_config [yes] Created /home/condor/etc/roster, the list of all machines in your pool. Press enter to continue. ********************************************************************* Condor has been fully installed on this machine. ********************************************************************* /home/condor/sbin contains various administrative tools. If you are going to administer Condor, you should probably place that directory in your PATH. Be sure to run condor_init on each machine in your pool to create the lock directory before you start Condor there. To start Condor on any machine, just execute: /home/condor/sbin/condor_master Since this is your central manager, you should start Condor here first. Press enter to continue. You should probably setup your machines to start Condor automatically at boot time. If your machine uses System-V style init scripts, look in /home/condor/etc/examples/condor.boot for a script that you can use to start and stop Condor. Please read the "Condor is installed... now what?" section of the INSTALL file for things you should do before and after starting the Condor daemons. In particular, you might want to set up host/ip access security. See the Adminstrator's Manual for details. RUN CONDOR_INIT ON EVERY NODE IN THE CLUSTER. [root@node001 condor-6.5.3]# brsh /home/condor/sbin/condor_init ** node001 ***** /home/condor/condor_config already exists. /home/condor/hosts/node001/log already exists. /home/condor/hosts/node001/spool already exists. /home/condor/hosts/node001/execute already exists. /home/condor/hosts/node001/condor_config.local already exists. Condor has been initialized, but not started. ** node002 ***** /home/condor/condor_config already exists. /home/condor/hosts/node002/log already exists. /home/condor/hosts/node002/spool already exists. /home/condor/hosts/node002/execute already exists. Creating /home/condor/hosts/node002/condor_config.local Creating /var/lock/condor Condor has been initialized, but not started. . . . NOW RUN CONDOR_INSTALL AGAIN TO COMPLETELY SETUP THE CENTRAL MANAGER. [root@node001 condor-6.5.3]# ./condor_install Welcome to condor_install. You are going to need to answer a few questions about how you want Condor configured on this machine, what pool(s) you want to join, and if this machine is going to serve as the Central Manager for its own pool. If you are unsure about how to answer any of the questions asked here, please consult the INSTALL file or the Installation chapter of the Condor Administrator's Manual. The installation is broken down into various steps. Please consult the INSTALL file to refer to a specific step if you have trouble with it. For most questions, defaults will be given in []'s. To accept the default, just press return. If you have problems installing or using Condor, please consult the Condor Administrator's Manual, which can be found on the World Wide Web at: http://www.cs.wisc.edu/condor/manual/ If you still have problems, send email to condor-admin@cs.wisc.edu. Press enter to begin Condor installation ********************************************************************* STEP 1: What type of Condor installation do you want? ********************************************************************* Would you like to do a full installation of Condor? [yes] no Would you like to setup this host as a submit-only machine? [yes] no Would you like to setup this host as a Condor Central Manager? (Only choose this option if you have already done a full installation on a file server and want to setup the local machine [no] yes Press enter to continue. ********************************************************************* STEP 2: How many machines are you setting up for Condor? ********************************************************************* You can only have 1 machine set up as a central manager. Press enter to continue. ********************************************************************* STEP 3: Install the Condor "release directory", which holds various binaries, libraries, scripts and files used by Condor. ********************************************************************* which: no condor_config_val in (/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin/ X11:/usr/X11R6/bin:/usr/java/j2re1.4.2/bin:/usr/local/mpich_pgi/bin:/ usr/pgi/linux86/bin:/opt/scali/bin:/opt/scali/sbin:/opt/scali/contrib/ pbs/bin:/root/bin) I can't find a complete Condor release directory. Have you installed a release directory already? [no] yes What's the full path to the release directory? /home/condor Using /home/condor as the Condor release directory. Press enter to continue. What name would you like to use for this pool? This should be a short description (20 characters or so) that describes your site. For example, the name for the UW-Madison Computer Science Condor Pool is: "UW-Madison CS". This value is stored in your central manager's local config file as "COLLECTOR_NAME", if you decide to change it later. (This shouldn't include any " marks). Penguin-Pool Setting up central manager config file /home/condor/hosts/sci1-1/condor_config.local ... done. I [root@node001 condor-6.5.3]# brsh /home/condor/sbin/condor_master ** node001 ***** ** node002 ***** . . . CHECK THE STATUS OF CONDOR ON THE CLUSTER. [root@node001 condor-6.5.3]# /home/condor/bin/condor_status Name OpSys Arch State Activity LoadAv Mem ActvtyTime vm1@node001.c LINUX INTEL Uncliamed Idle 0.000 1008 0+00:00:08 vm2@node001.c LINUX INTEL Unclaimed Idle 0.000 1008 0+00:00:05 vm1@node002 LINUX INTEL Uncliamed Idle 0.000 503 0+00:00:15 vm2@node002 LINUX INTEL Uncliamed Idle 0.000 503 0+00:00:16 vm1@node003 LINUX INTEL Uncliamed Idle 0.000 503 0+00:00:15 vm2@node003 LINUX INTEL Uncliamed Idle 0.000 503 0+00:00:16 . . . Machines Owner Claimed Unclaimed Matched Preempting INTEL/LINUX 20 19 0 1 0 0 Total 20 19 0 1 0 0