gLite > gLite 3.1 > glite-SE_dpm_mysql (x86_64) > Known Issues  
 
 

 

 

gLite 3.1

gLite DPM mysql x86_64 known issues


httpd/mod_ssl update breaks GridSite

Tracked via Bug 65013

Description

Recently a RHEL4/SL4 update of httpd-2.0.52-41.sl4.7 and mod_ssl-2.0.52-41.sl4.7 was released to fix CVE-2009-3555. In this update the internal structures of mod_ssl were modified, causing gridsite-1.1.18 to fail.

For now the workaround is to keep the httpd-related rpms at their previous versions until bug #65013 is fixed.



Upgrading DPM database schema

Description


There is a potential problem while upgrading the DPM database schema, which is done as a part of the DPM 1.6.x to 1.7 upgrade. Sites with large mysql databases can run into an error when the schema update script is run, either manually or as a part of the YAIM configuration step. While no data should be lost because of the schema upgrade failure it will not be possible to subsequently run the DPM until the database schema is properly updated.

The problem is due to the default mysql InnoDB buffer pool size, which will not allow the schema change to be applied to a large database. A change can be made to the mysql server configuration to allow the update to succeed. However, if the update script has already been run an extra step is required to be able to successfully rerun the script.

Full details are documented here. It should also be noted that the upgrade take some time, possibly several hours.

In case there are any problems or questions after having checked the twiki please feel free to ask them in the direct support list (hep-service-dpm@cern.ch)

mod_ssl timeout error

Tracked via Bug 48458

Description


A buffering issue between mod_ssl and OpenSSL is causing SSL handshake timeout errors in a number of cases. The workaround is to install the dummy-ca-certs-20090630-1.noarch.rpm from the lcg-CA repository. For more details please check the LCG-2 CAs web page, mod_ssl timeout workaround section.

Configuration issue with yaim in Update 46

Tracked via Bug 49369

Description


There is a known problem when configuring DPM 1.7.0-6 using YAIM with a configuration that sets DPNS_BASEDIR to a value different from the default value of "home". This page describes a workaround for the problem and is specific to version 1.7.0-6. The problem described is not present in previous DPM versions and is fixed in later versions.

Issues with Update 38

For x86_64 this update still contains bdii v. 4.0.0-5. However for x86 this update contains bdii v. 4.0.1-0. As bdii v. 4.0.1-0 has important bug fixes we recommend to install bdii v. 4.0.1-0 also on x86_64 nodes. To do this please go to the corresponding x86 web page for the x86_64 node type you are installing and get the bdii v. 4.0.1-0 rpm from the rpm list.

Other Documentation

For an up to date documentation of the DPM known issues, please check also:

gLite wide known issues

Please also check the gLite wide known issues.