Page updated: 06/09/2004
About the website

                        Valid XHTML 1.0!

gLite 3.0

glite-SE_dcache_admin_postgres - Update to version 3.0.1-0

Date 23.04.07
Priority Normal


This update contains a new version of glite-yaim-3.0.1. The new version contains the following new features:
  • To configure correctly the glite-CE with torque, the following parameters are obligatory:
    # Jobmanager specific settings
  • In case of site BDII separated from CE, it is necessary to install by hand the lcg-info-templates and lcg-info-generic packages to the site BDII node and to remove the ${INSTALL_ROOT}/lcg/var/gip/ldif/static-file-Site.ldif file on all CE nodes.
  • In the site-info.def file is necessary to define the BDII_CE_URL parameter as follows:
  • In the site-info.file given in ./examples, where is
    /C=CH/O=CERN/OU=GRID/CN=host/ ops' 'ops 15004
    should be
    /C=CH/O=CERN/OU=GRID/CN=host/ ops' 'ops 15009
  • If optional bin/yaim command is used to configure a gLiteCE, then the node will not work properly until service gLite is restarted since the gatekeeper will not be running after the configuration. If default configure_node script is used then all works without problems.
Please also have a look at the list of known issues.

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

Fixed bugs

Number Description
 #16877 myproxy is installed with glite-SE_dpm_mysql
 #17307 config_rfio show error messages when CASTOR-client is empty package
 #24190 Use $pbsserver instead of $clienthost in mom_priv/config for torque > 2.
 #24303 empty line in users.conf causes config_users to fail
 #24712 config_users creates accounts for unsupported VOs
 #24784 Starting mysqld in DPM config steps (Yaim)

Updated rpms

Name Version Full RPM name Description
glite-SE_dcache_admin_postgres 3.0.1-0 glite-SE_dcache_admin_postgres-3.0.1-0.noarch.rpm glite SE dcache admin postgres node
glite-yaim 3.0.1-10 glite-yaim-3.0.1-10.noarch.rpm glite-yaim

The RPMs can be updated using apt via

Service reconfiguration after update

Not needed.

Service restart after update

Not needed.

How to apply the fix

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