Page updated: 06/09/2004
About the website

                        Valid XHTML 1.0!

gLite 3.0

glite-VOBOX - Update to version 3.0.32-0

Date 31.10.07
Priority Normal


GIN Update

GIN has been updated not to call GIP directly, but to use site ldap servers. Please note that GIN should now only run on the MON box. On nodes other than the MON box, the glite-rgma-gin rpm should be removed manually.


YAIM 4.0.0 is a release without any important functionality changes, but it fixes bugs found in the YAIM 3.1.1 release. The most relevant changes are:
  • Configuration of the new glite-info-generic rpm.
  • New site-info.def variable SITE_BDII_HOST.
  • users.conf example files includes pool accounts for sgm and prd users.
  • Removal of lcgenv.(c)sh file. Instead, the environment variables created there are now available in grid-env.(c)sh.
  • In the VOBOX, the function config_vobox, should contain a 'break' instead of an 'exit' in line 61.
  • GLOBUS_TCP_PORT_RANGE needs to be edited manually in the form of "num1,num2" for VDT versions 1.6, or "num1 num2" for VDT versions < 1.6. This will be automatically done in the next YAIM release. (Reported as bug #29878.)
Please, check the YAIM 4 guide for more details:
-- Advice:

It is advised to verify the consistency between the accounts listed
in YAIM's users.conf, /etc/passwd and /etc/grid-security/gridmapdir.

Accounts that should no longer be used should only be removed when
the service is in scheduled downtime and activity has drained.

To clean up /etc/grid-security/gridmapdir the following procedure
should be applied:

1. cd /etc/grid-security/gridmapdir

2. For any unwanted account name file "abc123" run this command:

        ls -li abc123

3. If the link count is 1, the file can be removed.

4. If the link count is 2, note the inode number of the file and
   run this command:

        ls -li | awk '$1 == inode_number'

   For example:

        ls -li | awk '$1 == 2467912'

   That will report 2 files: the unwanted account name file and
   the file whose name contains '%' characters and represents
   the user mapped to the account. Both must be removed.

New version of the glite-info-generic including a fix for the plug-in precedence problem, which was found during certification. Plug-in values are now merged for each plug-in. This avoids the problem of one plug-in taking precedence over another if they are both providing values for the same entry.
LB Client

Newer LB server versions may return events that older client versions do not understand. This fix makes clients to ignore these events rather than to crash. In particular, this occurs when gLite 3.0 client is used to query gLite 3.1 job collections.
Other Updates

The incorrectly removed dependency on lcg-version has been re-added to the metapackage.

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
 #15931 GIP should log if incorrect ldif file is created by the plugin
 #15932 The files in /opt/lcg/var/gip/tmp are not cleaned
 #16625 10-50 times speedup for lcg-info-generic.
 #19601 GIP Read mergeing duplicate entries
 #19612 New GIP in-tollerance to ldif files
 #28725 Old glite-job-logging-info crashes querying master job of a collection
 #28969 glite-WN update 3_0_24-0 breaks SAM tests

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-common 3.0.8-1 glite-lb-common-3.0.8-1.i386.rpm L&B common subroutines library
glite-UI 3.0.26-0 glite-UI-3.0.26-0.noarch.rpm gLite User Interface
glite-VOBOX 3.0.32-0 glite-VOBOX-3.0.32-0.noarch.rpm gLite VOBOX node
glite-yaim-clients 4.0.0-5 glite-yaim-clients-4.0.0-5.noarch.rpm org.glite.yaim.clients
glite-yaim-core 4.0.0-12 glite-yaim-core-4.0.0-12.noarch.rpm This is the main yaim core module that contains common functions to all node types.

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)