Differences

This shows you the differences between two versions of the page.

--- condor:installation:network [2011/07/15 19:38] – added "add condor user" garrettheath4
+++ condor:installation:network [2011/07/18 18:04] – reorganized sections garrettheath4
@@ Line 5: / Line 5: @@
 Our pool uses a dedicated NAS server with a 2.7TB RAID 5+1 drive configuration to provide faster than normal access times to the data than normal hard drive I/O, especially data reads.
-===== Install Binaries =====
+===== Add Local condor User =====
-In order to install the binaries onto the ''tesla.cs.wlu.edu'' NAS, run this command in the terminal:
+In order for daemons to run correctly and for permissions to be properly set, a local ''condor'' user must be present on all members of the Condor pool.  The following must be set for the ''condor'' users:\\
-<code bash>cd /mnt/config/src/fedora64
+  condor UID = 1344
-sudo ./condor_configure --type=manager,submit,execute --central-manager=john.cs.wlu.edu --local-dir=/mnt/config/hosts/_default --install-dir=/mnt/config/release/x86_64_rhap_5 --install --verbose</code>
+  condor GID = 1610
-===== Add Machines to Condor Pool =====
+First, check to see if the ''condor'' user exists on the machine.  Do this by running:
+<code bash>cat /etc/passwd | grep ^condor:</code>
+**If you get a match**, first reset its settings in case the user wasn't created correctly.
+<code bash>sudo groupmod -g 1610 condor
+sudo usermod -c "Owner of Condor Daemons" -d "/var/lib/condor" -m -u 1344 -g condor -s "/sbin/nologin" -L condor</code>
+:!: If you get a message that says that the directory ''/var/lib/condor'' already exists, run this command next:
+<code bash>sudo chown -R condor:condor /var/lib/condor</code>
-FIXME
+**If you do not get a match**, you need to manually add the user.  To do this, run:
+<code bash>sudo groupadd -g 1610 condor
+sudo useradd -c "Owner of Condor Daemons" -d "/var/lib/condor" -m -u 1344 -g condor -s "/sbin/nologin" condor
+sudo usermod -L condor</code>
-==== Add Local condor User ====
+Just to be sure, do <code bash>ls -al /var/lib/condor</code> and verify that the entry "''.''" is owned by ''condor'' and is a part of the ''condor'' group.  If not, you probably have a conflicting UID or GID and will have to set it manually.  Set it to one that is not being used by the local user system or by the network and then set the ''CONDOR_IDS'' variable in that individual host's Condor local configuration file((A host's individual configuration file is located at ''/mnt/config/hosts/<HOSTNAME>/config/condor_config.local'' .))
-First, check to see if the ''condor'' user exists on the machine.  Do this by running:
+===== Install Binaries =====
-<code bash>cat /etc/passwd | grep ^condor:</code>
-If you get a match, you need to edit the ''/etc/passwd'' file and manually set the UID and GID of the user.  Assuming that the UID and GID doesn't conflict with any other user (either local or network), change the line to read:
-<code>condor:x:201:481:Owner of Condor Daemons:/var/lib/condor:/sbin/nologin</code>
-If you do not get a match, you need to manually add the user.  To do this, run:
+In order to install the binaries onto the ''tesla.cs.wlu.edu'' NAS, run this command in the terminal:
-<code bash>sudo groupadd -g 481 condor</code>
+<code bash>cd /mnt/config/src/fedora64
-sudo useradd -c "Owner of Condor Daemons" -d "/var/lib/condor" -m -u 201 -g 481 -s "/sbin/nologin" condor</code>
+sudo ./condor_configure --type=manager,submit,execute --central-manager=john.cs.wlu.edu --local-dir=/mnt/config/hosts/_default --install-dir=/mnt/config/release/x86_64_rhap_5 --owner=condor --install --verbose</code>
-==== Set Machine Variables ====
+===== Set Machine Variables =====
 The problem with putting as much of Condor on the NAS is that this introduces a lot of NFS traffic onto the network, especially when Condor jobs are running.  Having the user executables stored centrally on the NAS will cause all of the computers to be almost constantly reading from the NAS when the executables are opened and run.