Release notes for the gLite 3.1 LB Checkpointing release (patch #1251)

These notes describe the LB checkpoint release 1251 with VDT 1.2.x for SL3

APT configuration

Please use the following repository to install:

http://gimo.pd.infn.it:25555/rep/wmslb-i386/RPMS/

To use apt-get, create glite.list in /etc/apt/sources.list.d with the following contents.

rpm http://gimo.pd.infn.it:25555/ rep/wmslb-i386 wmslb_patch1251 glite ig externals

For CAs, you may need the following apt-get repository (for example in cg-ca.list)

rpm http://linuxsoft.cern.ch/ LCG-CAs/current production

Host certificate installation

• Copy to /etc/grid-security your host and key certificates and then set the right permissions:

chmod 600 /etc/grid-security/hostcert.pem

chmod 400 /etc/grid-security/hostkey.pem

YAIM installation and configuration

Install glite-yaim and ig-yaim (use version glite-yaim-core-3.1.0-2.3)

apt-get update

apt-get install glite-yaim-core

apt-get install ig-yaim

If you use a different repository you need to download the previous rpm from here: ig-yaim

Site-info.def customization

Prepare your customized site-info.def starting from the template provided by ig-yaim (/opt/glite/yaim/examples/siteinfo/ig-site-info.def).

Below we describe the variables that affect the ig_LB31 configuration process in the order you find them in the ig-site-info.def template. For more detailed information please refer to the official Site Installation Guide. An example has been attached.

LB 3.1 installation

Install ig_LB31 profile usign YAIM

/opt/glite/yaim/bin/ig_yaim_wms31 -i -s <site-info.def> -m ig_LB31

where <site-info.def> is the path of your customized site-info.def

LB 3.1 Configuration

Configure ig_LB31 profile using YAIM

/opt/glite/yaim/bin/ig_yaim_wms31 -c -s <site-info.def> -n ig_LB31

where <site-info.def> is the path to your customized site-info.def

LB 3.1 Post Configuration

• There is a bug in bkserverd which causes memory leak. This happens when LB server DB is configured with transactional database support. The workaround is to modify the /opt/glite/etc/init.d/glite-lb-bkserverd file, changing the row:

 --- glite-lb-bkserverd.orig     2007-07-18 10:24:53.000000000 +0200
 +++ glite-lb-bkserverd  2007-07-17 17:43:38.000000000 +0200
@@ -60,10 +60,11 @@
         [ -z "$GLITE_LB_NOTIF_FPREFIX" ] && GLITE_LB_NOTIF_FPREFIX="/var/tmp/glite-lb-notif"
        echo -n Starting glite-lb-bkserver ...
-        su - $GLITE_USER -c "$GLITE_LOCATION/bin/glite-lb-bkserverd \
+       su - $GLITE_USER -c "$GLITE_LOCATION/bin/glite-lb-bkserverd -b 0 \

• Add to file /opt/glite/etc/LB-super-users the lists of the WMS host DN that uses this LB server. For example:

[root@devel12 etc]# cat /opt/glite/etc/LB-super-users
/C=IT/O=INFN/OU=Host/L=CNAF/CN=devel10.cnaf.infn.it

Optional steps

• To start LB server in debug mode, it is needed to change the file /opt/glite/etc/init.d/glite-lb-bkserverd

[root@devel12 init.d]# diff -Bu  glite-lb-bkserverd.orig glite-lb-bkserverd.debug
--- glite-lb-bkserverd.orig     2007-07-18 10:24:53.000000000 +0200
+++ glite-lb-bkserverd    2007-07-19 10:33:11.000000000 +0200
@@ -63,7 +63,8 @@
        su - $GLITE_USER -c "$GLITE_LOCATION/bin/glite-lb-bkserverd \
                --notif-il-sock=$GLITE_LB_NOTIF_SOCK \
                --notif-il-fprefix=$GLITE_LB_NOTIF_FPREFIX \
-               $super $creds -i $pidfile $port $wport $dumpdir $purgedir $maildir" \
+               $super $creds -i $pidfile $port $wport $dumpdir $purgedir $maildir \
+               -d > /var/log/glite/lbbkserver.log 2>&1 &" \
        && echo " done" || echo " FAILED"

where /var/log/glite is an existing path.

• To enable the mysql indexes into the LB database, it is needed to run the following command:

/opt/glite/bin/glite-lb-bkindex --really /opt/glite/etc/glite-lb-index.conf

where /opt/glite/etc/glite-lb-index.conf shoul be created starting from the template file /opt/glite/etc/glite-lb-index.conf.template.

-- Main.gianelle - 19 Jul 2007