dCache server, v. 2.2.21 and dCache srmclient, v. 2.2.22
Affected services
affected service: dCache server, UI ,WN
What's new:
dCache server, v. 2.2.21
The upgrade from jGlobus 1.8 to 2.0 introduced a performance regression: the last-modified time of CA-related files are checked for each request, which, when these files are stored on a shared filesystem, introduces unacceptable latency. This release uses an updated jGlobus that throttles how often it checks the last-modified attribute of files.
The rebalancer command accepts options to modify its behaviour. The online help has been updated to better describe these options.
The SRM Client 2.2.22 follows the FHS compliant directory layout.
Changes:
Migration to jglobus2.0: SRM client now supports secure hash algorithm SHA-2 and therefore SHA-2 signed certificates. jGlobus2.0 also supports SHA-1 signed certificates. Please be aware that VOs are encouraged not to issue SHA-1 certificates any longer. Migrating to this version of SRM Client is therefore recommended.
Switch to jglobus with jumbo proxies support. There was a problem with growing proxies which would at some point cause problems with SRM. This fix solves the jumbo proxy issue.
To deploy, update your installation and restart the Web-server.
Known issues:
When upgrading from the EMI repository on Debian, mod_gridsite is not correctly replaced. Uninstall the old module first and install the new one to work around the issue.
This maintenance release of L&B provides fixes for several rare memory handling issues, fixes the handling of MySQL configuration file by L&B Server's set-up script, and improves the reliability of the Site Notification Keeper.
Installation & Configuration:
The emi-lb metapackage is installed by yum.
Configuration requires, at the very least, setting MYSQL_PASSWORD, SITE_NAME and SITE_EMAIL in the site-info.def file.
Reconfiguration is required. Reconfiguration by YAIM will restart the service automatically. On Debian, use the glite-lb-setup command.
Upgrading from previous versions of L&B involves a database schema change. A DB migration script is available. In typical scenarios it will be initiated automatically during reconfiguration. Follow documentation in case it needs to be started manually.