Page updated: 21/03/2007
About the website

                        Valid XHTML 1.0!

gLite 3.0

glite-UI - Update to version 3.0.3

Date 21.08.2006
Priority Normal


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

Known Issues

Writable tmp user space

/tmp/glite/glite-ui/ has to be writable by any user:

  • chmod a+w /tmp/glite/glite-ui/ 
Relocatable distribution

Please find new instructions on installing the relocatable release here.

Note that the dependencies should now be untarred in the top level ($INSTALL_ROOT).

A new tarball is currently being tested (as of 18/08/06) which will fix a number of problems, including the fetch-crl issue discovered recently. We recommend waiting for the next release.

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
 #16502 automatic sequence code generation is incorrect
 #17322 lcg-infosites and lcg-info from relocatable gLite 3.0 installation don't work
 #17450 PERLLIB is not populated with edg/lib/perl from csh shell
 #17517 Reassigned item: gsidcap fails when > 56 CAs on server
 #17540 Bug #13789 appearing again due to missing merge of 1.4 quick-fix into glite 3.0
 #17569 problem in LFC Python interface
 #18047 yaim still configures edg-utils-sytem but we have moved to fetch-crl
 #18131 Attribute VOMS_FQAN not added by glite-job-list-match command [None]
 #9777 unable to get logging-info -2 info for 1000 jobs

Updated rpms

Name Version Full RPM name Description
dcache-client 1.6.7-4 dcache-client-1.6.7-4.i386.rpm d-cache Client
edg-profile 2.0.9-1 edg-profile-2.0.9-1.noarch.rpm edg-profile
glite-UI 3.0.3-0 glite-UI-3.0.3-0.noarch.rpm gLite User Interface
glite-ui-config 1.3.20-0 glite-ui-config-1.3.20-0.noarch.rpm gLite User Interface configuration files
glite-yaim 3.0.0-22 glite-yaim-3.0.0-22.noarch.rpm glite-yaim
lcg-version 3.0.2-1 lcg-version-3.0.2-1.noarch.rpm lcg version info

The RPMs can be updated using apt via

Configuration changes


Service restart after update


How to apply the fix

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