Computing System Administration

Getting ATLAS releases to work on RHEL5 x86_64 nodes

• For pacman to work you need to install an older 32-bit opensll: rpm -ivh http://ftp.scientificlinux.org/linux/scientific/51/i386/SL/openssl097a-0.9.7a-9.i386.rpm
• To satisfy some packages, especially event generation: yum install libgfortran-4.1.2-44.el5.i386
• You need to install blas: yum install blas.i386 and yum install blas-devel.i386
• To get /usr/lib/libreadline.so.4 (also needed for 32-bit Linux) do rpm -ivh http://linuxsoft.cern.ch/cern/slc5X/i386/SL/compat-readline43-4.3-3.i386.rpm
• You need 32-bit gcc 3.4 (also needed for 32-bit Linux): yum install compat-gcc-34
• You need 32-bit g++ 3.4 (also needed for 32-bit Linux): yum install compat-gcc-34-c++
• You may need to install 32-bit popt: yum install popt.i386

Getting the I686-SLC5-GCC43 kits to validate (and run) on RHEL5

• Install the pacman kit for gcc43, see https://twiki.cern.ch/twiki/bin/view/Atlas/RPMCompatSLC5#Run_SLC4_32bit_binaries_on_SLC5
• You probably need to ln -s /usr/lib/libg2c.so.0.0.0 /usr/lib/libg2c.so
• You probably need to ln -s /usr/lib/gcc/x86_64-redhat-linux/3.4.6/libgcc_s_32.so /lib/libgcc_s_32.so

Installing root and enabling the xrootd service (needed for proof)

• on RHEL5 x86_64 systems: (gcc 4.3 is too advanced for UiO desktops)

tar -xvzf /mn/kvant/hep/linux/root/root_v5.22.00.Linux-slc5-gcc3.4.tar.gz -C /opt

• Assume standard setup is on default system (e.g. scalar.uio.no) and $node is the node you want to install on. Of course if you are logged on to $node all the ssh'ing is not needed

scp /etc/sysconfig/xrootd $node:/etc/sysconfig/
scp /etc/xpd.cf $node:/etc/
scp /etc/rc.d/init.d/xrootd $node:/etc/rc.d/init.d/
ssh $node chkconfig --add xrootd
ssh $node chkconfig --level 35 xrootd on

• Note, xrootd runs under read account (as of May 2009)

ssh $node mkdir /var/log/xrootd <br>ssh $node chown read:fysepf /var/log/xrootd

• Edit /etc/xpd.cf and restart xrootd to add a worker node.
• Redistribute /etc/cpd.cf as well (have to find a simpler but reliable system for this

/sbin/service xrootd start

Installing VirtualBox

• Download and install the appropriate rpm from http://download.virtualbox.org/virtualbox
• Remove the new line with vboxusers from /etc/group
• Add the host's username to the vboxusers group, e.g.

echo vboxusers:x:15522:esbenlu >> /etc/group
echo vboxusers:x:15522:esbenlu >> /etc/group.local

• Finalize the vbox setup:

/etc/init.d/vboxdrv setup

Installing ARC client on RHEL5 boxes (as superuser)

• See http://download.nordugrid.org/repos.html
• Typical /etc/yum.repos.d/nordugrid:

[nordugrid] name=NorduGrid - $basearch - stable

baseurl=http://download.nordugrid.org/repos/redhat/$releasever/$basearch/stable
enabled=1 gpgcheck=1
gpgkey=http://download.nordugrid.org/RPM-GPG-KEY-nordugrid 

• yum groupinstall "ARC Client" to install the client s/w
• yum install nordugrid-arc-ca-utils to install the missing Certificate Authority utilities
• /opt/nordugrid/sbin/grid-update-crls to jumpstart the first update of the Certificate Revocation Lists - after that there is a cron that does the job automatically.

Installing an ATLAS software release

• Decide where to install the software - this is the "repository".
• The install script is here: http://koherens.uio.no/atlas/install/installPacmanKit.sh. Download it somewhere and chmod u+x it.
• A typical installation looks like

mkdir {root of the software repository}/atlas/software/releases/15.2.0<br>
cd {root of the software repository}/atlas/software/releases/15.2.0<br>

• If you download the install script in {root of the software repository}/atlas/software/releases/ then you do 

../installPacmanKit.sh 15.2.0 I686-SLC4-GCC34-OPT {runtimedir}

• The {runtimedir} is set in /etc/arc.conf (normal users should create /<something>/APPS/HEP and use {runtimedir}=/<something>). Last folder of <something> could often be runtime, so e.g. for maikens installation, <something> is: /scratch2/maikenp/atlas/runtime The I686-SLC4-GCC34-OPT downloads a kit built for this platform (which is the only one fully supported for the moment - SLC4 is RHEL4/CentOS 4-compatible, kits for x86_64 and RHEL5 are under development).

• If your OS is 64-bit there may be some missing 32-bit libraries, my "favorites" are from the blas, libgfortran and libf2c packages. The first thing I will do is run a kit validation, e.g. ./KVsubmit nordugris.uit.no 15.2.0 which will send a grid job to validate the kit (KVsubmit is in http://koherens.uio.no/atlas/install/KVsubmit if you want to try it yourself).

• Occasionally the database release is updated after a Kit is packaged. In this case you have to download a new DBRelease. Check the release notes to find out which one should be downloaded. In the directory where you installed the release (i.e. SITEROOT) do e.g. for DBRelease 7.2.1

pacman -get http://atlas.web.cern.ch/Atlas/GROUPS/DATABASE/pacman4/DBRelease:DBRelease-7.2.1

ATLAS VO Registration and Management

This site is used for registering atlas VO grid resource users and for managing information about their affiliation with the ATLAS VO and their permissions regarding use of grid resources.

Installation of a new release of DQ2Clients

• You had better set umask to 022 or nobody else will be able to read files or execute any commands!
• Typical install command is

pacman -trust-all-caches -allow tar-overwrite -get http://atlas.web.cern.ch/Atlas/GROUPS/DATABASE/project/ddm/releases/pacman/cache:DQ2Clients

• Additional documentation is here - there is also a howto.