gLite > gLite 3.1 > glite-WN > Known Issues  
 
 

 

 

gLite 3.1

gLite Worker Node 64Bit known issues


This version of the Worker Node is targeted to setup x86_64 machines in "compatibility" mode, i.e. both 32bit and 64bit libraries are provided. The YAIM tool configures the LD_LIBRARY_PATH variable accordingly. The command to install the Worker Node is yum groupinstall as follows
yum groupinstall glite-WN

In order to get both 32bit and 64bit libraries, both versions of certain rpms must be installed. On a x86_64 machine yum resp. rpm usually installs the 64bit rpm over the 32bit package but for certain rpms this seems not to be the case (for yet unknown reasons). It has been observed that the following binaries are 32bit on the x86_64 Worker Node:

  • /opt/lcg/bin/gfal_*
  • /opt/lcg/bin/lcg-*
  • /opt/lcg/bin/lfc-*
  • /opt/glite/bin/glite-delegation-*
  • /opt/glite/bin/glite-srm-*
  • /opt/glite/bin/glite_data_catalog_*
  • /opt/glite/bin/glite-transfer-*
It has been observed that some of these even may cause unexpected behaviour (see Bug #40734 ). In this case it is advised ro reinstall the 64Bit version of the lcg-utils package.
This issue will be dealt with in future releases.



Other know issues which affect 32 and 63 Bit version of the Worker Node:

  • With lcg_util 1.7.2 (Update 45) the option "-t" was deprecated. Trying to use the option should result in a warning, however in some cases a segmentation fault can happen (bug 50265)
  • A runtime error with the LFC Perl API reported as bug 26535
  • rgma-client-check used wrong log4j location 26943
  • The format of GLOBUS_TCP_PORT_RANGE is different for VDT1.6. Thus for gLite 3.1 WN you will need a new format:
    GLOBUS_TCP_PORT_RANGE="20000,25000"
    whereas in gLite 3.0 the format is
    GLOBUS_TCP_PORT_RANGE="20000 25000"


When running yaim for the first time an error message is displayed:
ERROR 1045 (28000): Access denied for user 'hydra1'@'localhost' (using password: YES)
The error message disappears when running yaim a second time. This issue is tracked in bug #43945.



Please also check the gLite wide known issues.

If you are installing the Worker Node via a tarball, please also have a look to the known issues specific for the tarball installation.