Page updated: 21/03/2007
About the website

                        Valid XHTML 1.0!

 
gLite 3.0

glite-CE - Update to version 2.4.18

Date 21.08.2006
Priority Normal

Description


This update fixes various bugs. For the full list of bugs, please see list below.

Known issues


Logging
Extra steps are required for full logging on the glite CE. The first involves creating a configuration file for blah, /opt/glite/etc/blah.config, with the following contents 
    BLAHPD_ACCOUNTING_INFO_LOG=/var/log/glite/accounting/blahp.log
and then 
    mkdir /var/log/glite/accounting
    chmod u+s /opt/glite/bin/BDlogger
At present there is no version APEL available which is compatible with these logs.
 
gLite CE and TORQUE server has problems with gridmapfile generation.
Please run the following rather than combining the node-types in one command: 
    /opt/glite/yaim/scripts/configure_node site-info.def gliteCE
    /opt/glite/yaim/scripts/configure_node site-info.def TORQUE_server
TORQUE server does not always start
For details see:

    https://savannah.cern.ch/bugs/index.php?func=detailitem&item_id=17586

If you are configuring a torque server, please ensure the server is running: 
    # /etc/init.d/pbs_server start
before running yaim's configure_node script.
 
VOtag publishing
For details see:
 

    https://savannah.cern.ch/bugs/?func=detailitem&item_id=10872

Please create the appropriate directories - one for each VO - under

    /opt/edg/var/info

 owned by the sgm. Also create

   /etc/sysconfig/edg

and

    EDG_LOCATION=/opt/edg
    EDG_LOCATION_VAR=/opt/edg/var

Problem if CE_DATADIR="" (default)
Due to bug

    https://savannah.cern.ch/bugs/index.php?func=detailitem&item_id=18328

the glite-CE configuration the lcg-info-static-ce.ldif file is not created correctly if in the site-info.def file the CE_DATADIR="" (default).

The fix is, in case the ce_datadir id not defined to put:

    CE_DATADIR=unset

to the site-info.def file.
 
Running a separate TORQUE server

Run the following on the torque server (BLParserPBS is from glite-ce-blahp) 

      /opt/glite/bin/BLParserPBS -p 33332 -s /var/spool/pbs
Insert gLite CE hostname into /etc/hosts.equiv on the torque server.
On WNs put gLite CE hostname into


      /opt/edg/etc/edg-pbs-knownhosts.conf

and run /opt/edg/sbin/edg-pbs-knownhosts (it will run as cron later anyway)

Fixed bugs

Number Description
 #15050 job-status returns Running and Waiting jobs even after proxy expired
 #15450 rare Unable to Register the Job during the job error
 #15524 site bdii publishes using the base 'mds-vo-name=resource,o=grid'
 #16502 automatic sequence code generation is incorrect
 #17866 BDII rpm is not relocatable; file in /etc
 #17967 top-level BDII overload due to LDIF providers
 #17968 BDII should cache LDIF sources
 #17969 BDII must listen on INADDR_ANY
 #18047 yaim still configures edg-utils-sytem but we have moved to fetch-crl
 #18130 BDII FCR filter lets some entries pass through
 #18204 BDII sorts LDAP records unnecessarily
 #18219 BDII error messages may refer to the wrong LDAP records
 #9777 unable to get logging-info -2 info for 1000 jobs

Updated rpms

Name Version Full RPM name Description
bdii 3.8.1-1_sl3 bdii-3.8.1-1_sl3.noarch.rpm bdii
glite-CE 2.4.18-0 glite-CE-2.4.18-0.noarch.rpm gLite Computing Element node configuration files
glite-config 1.6.32-0 glite-config-1.6.32-0.noarch.rpm gLite configuration scripts
glite-lb-client 2.1.4-1 glite-lb-client-2.1.4-1.i386.rpm L&B client API and tools
glite-lb-common 3.0.5-1 glite-lb-common-3.0.5-1.i386.rpm L&B common subroutines library
glite-security-utils-config 1.2.5-1 glite-security-utils-config-1.2.5-1.noarch.rpm gLite Security Utilities configuration files
glite-yaim 3.0.0-22 glite-yaim-3.0.0-22.noarch.rpm glite-yaim
lcg-info-dynamic-scheduler-pbs 1.6.0-1 lcg-info-dynamic-scheduler-pbs-1.6.0-1.noarch.rpm Plugins for the lcg-info-dynamic-scheduler GIP plugin. The two plugins here are for Maui (scheduler) and PBS/Torque (LRMS).

The RPMs can be updated using apt via

Configuration changes

None

Service restart after update

Recommended.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)