Page updated: 06/09/2004
About the website

                        Valid XHTML 1.0!

 
gLite 3.0

glite-LB - Update to version 2.3.4-0

Date 14.01.08
Priority Normal

Description


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

Please see the general release page for the YAIM release notes.
WMS / LB updates

Fixes of missing dependencies of the glite-WMS and glite-LB metapackages as well as update of RPMs to their latest version used in the glite 3.0 repository.

Since a lot of new packages will be installed, apt-get dist-upgrade is required for upgrading.

Multiple bug fixes - besides others:
  • Avoid that a collection with pending jobs is processed multiple times
  • A job can be resubmitted to a CE where it previously failed, if no other compatible CE is available
  • Globus GSS library does not reset SSL error stack (breaking OpenSSL specification) before calling SSL routines in gss_unwrap() implementation, yielding a random false error triggered by various conditions (e.g. expired, actually unused proxy credential file on disk, missing certificate of VOMS server etc.). The bug was reported to globus as http://bugzilla.globus.org/bugzilla/show_bug.cgi?id=5453  and it should be fixed in VDT-1.6.1 soon. This part of the patch is a safe workaround, though.
  • Update lcg-mon-job-status to include new UI field. This update enables the UI host for submission to be published in to R-GMA
  • LB library used to keep a connection to LB proxy opened as long as the LB context is kept. With higher load the number of open contexts in WMS may raise to thousands, exhausting available fd's. On the other hand, keeping them open is useless, LB proxy is able to serve 10 simultaneous connections only.

    This update forces closing the connection after each operation, releasing the fd. The associated performance impact (when multiple requests could be served over a single connection) is negligible, as the LB proxy connection goes via Unix socket.
Please also have a look at the list of known issues.

Fixed bugs

Number Description
 #17154 Publication of the glite-WMS service in the site-BDII
 #19929 yaim configuration of glite-wms-check-daemons.sh cron
 #20483 WMS lacks lcg-expiregridmapdir rpm
 #27146 YAIM overwrites /etc/java/java.conf
 #27656 glite-LB metapackage does not install the rpms required by function config_bdii
 #28816 Unexpected GSSAPI error in LB
 #28953 glite-WMS should not depend on glite-config and they components
 #29324 create-default-dirs-CLASSICSE.sh doesn't work with DNS-like VO names
 #29403 BATCH_LOG_DIR variable in site-info.def undefined
 #30014 LB should be also visible in BDII as a service
 #30186 cronjob glite-lb-purge.cron doesn't work on LB separated from WMS
 #30949 WMS repo missing latest version of lcg-vomscerts
 #31240 org.glite.wms.wmproxy and org.glite.lb.server GlueServices not published.

Updated rpms

Name Version Full RPM name Description
glite-info-generic 2.0.2-2 glite-info-generic-2.0.2-2.noarch.rpm glite-info-generic
glite-LB 2.3.4-0 glite-LB-2.3.4-0.noarch.rpm gLite Logging and Bookkeeping node configuration files
glite-lb-client 2.3.6-1 glite-lb-client-2.3.6-1.i386.rpm L&B client API and tools
glite-security-gsoap-plugin 1.5.2-1 glite-security-gsoap-plugin-1.5.2-1.i386.rpm gSOAP plugin and gss libraries
glite-yaim-core 4.0.3-6 glite-yaim-core-4.0.3-6.noarch.rpm glite-yaim-core
glite-yaim-lb 4.0.1-2 glite-yaim-lb-4.0.1-2.noarch.rpm glite-yaim-lb
lcg-mon-job-status 2.0.8-1 lcg-mon-job-status-2.0.8-1.noarch.rpm lcg-mon-job-status
lcg-mon-logfile-common 1.0.6-2 lcg-mon-logfile-common-1.0.6-2.noarch.rpm lcg-mon-logfile-common
lcg-service-proxy 1.0.3-2 lcg-service-proxy-1.0.3-2.noarch.rpm LCG Service Proxy
python-logging 0.4.6-1 python-logging-0.4.6-1.noarch.rpm Python logging module

The RPMs can be updated using apt via

Service reconfiguration after update

Service must be reconfigured.

Service restart after update

Service must be restarted.

How to apply the fix

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