This maintenance release of L&B provides extended support for sites wishing to move the L&B Server's database to a remote DB server (improved support for connection strings in config), moves the location of the L&B Client JAR file to comply with Fedora/EPEL packaging rules, fixes build on the Power PC platform, updates packaging to comply with dh 7 packaging standards, and makes sure zombie jobs are properly recognized and reported over L&B server's http interface (i.e., when a JobID is used as an URL in a Web browser).
Configuration requires, at the very least, setting MYSQL_PASSWORD, SITE_NAME and SITE_EMAIL in the site-info.def file.
Reconfiguration is required if you are updating. On Scientific Linux, you can (re)configure by YAIM.
On Debian, use the glite-lb-setup command. Upgrading from previous versions of L&B (earlier than 4.0) 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.
Known issues:
There are missing dependencies on 32-bit platforms, which prevent L&B from installing succesfully. They are glite-info-provider-service, bdii and glite-yaim-bdii. They have only been released with EMI-1 and can be obtained from the EMI-1 (or UMD-1) repository if installation on a 32-bit system is required.
We updated the jGlobus version. This results in better error reporting for FTP transfers and X.509 certificates with a comma in the DN are handled correctly. Added support for additional xrootd client commands: querying the server configuration and a file's checksum, and locating a file. Prevented reading of configuration files. We fixed a problem with WASS pool selection. We added proxy-IO for NFS read requests (NFS v4.0 and v4.1).
Important Since version 1.11.3 the WebDAV service responds on the /webdav/[storage-area] path. More details in the WebDAV interface guide.
Important Since version 1.11.3 a security authentication token is used to secure all communication among the storm-frontend and grihttps services and the backend. The token is configured using the STORM_BE_XMLRPC_TOKEN YAIM variable for the three services. More details in the System administrator guide.
Important Please ensure that storage area file permissions are correctly set. Follow these instructions before running the gridhttps server.