Patch 5435 introduces glite-VOBOX version 3.2.15-1. The lcg-vobox package has been upgraded to 2.0.5, a bug fix release. lcg-vobox 2.0.5 fixes issues with respect to the previous release:

• a timeout has been added when the service uses myproxy-info commands. The timeout is to avoid a network problem causing the VOBOX proxy renewal daemon to hang when trying to determine if a proxy's remaining lifetime is below its optionally registered threshold.

Patch 5376 introduces glite-VOBOX version 3.2.14-1. The lcg-vobox package has been upgraded to 2.0.4, a bug fix release. lcg-vobox 2.0.4 fixes issues with respect to the previous release:

• A timeout has been added on MyProxy delegation operations to avoid that a network problem may cause the VOBOX proxy renewal daemon to hang
• Enhancements have been implemented for one site in particular; other sites can simply upgrade - a reconfiguration or restart is not required

For version 2.0.2 all the lcg-vobox code has been completely overhauled to deal with various issues:

• The proxy renewal mini DB can get corrupted by a race condition, requiring it to be removed and the proxies to be re-registered. The new vobox-proxy command automatically converts any existing DB into a set of human-readable files in a "data" subdirectory.
• The voms-proxy-init command can hang indefinitely, which has caused registered proxies to expire on various occasions at various sites. The new code has a timeout + retry loop around the command. (bug #77598)
• The myproxy-get-delegation command can fail when the Globus or MyProxy port range is defined. The new code ensures those variables are unset.
• The new "voname-box-proxyrenewal" service has more robust start and stop behavior. (bug #36766, bug #47204)
• The daemon runs under an "sgm" account, so it can accidentally be killed by that user. However, currently only root can restart the "voname-box-proxyrenewal" service. The new code allows the sgm user to restart the service as well.

 Please refer to the Details page for further information.

What's new

• Retrial for root requests after db reconnection (bug #75064)
• Conditional condrestart action in the init.d startup scripts (bug #76695)
• Added sonames in libraries (bug #57528)
• Added the possibility to send logs to syslog and have log levels (bug #83411)
• Fixed startup script when logfile does not contain a slash (bug #77388)
• Human readable dpns-ls -h (bug #20298)
• Update fs statistics with dpm-modifyfs --st RDONLY even if disabled (bug #78968)
• Fixed segfault in srmv1 and srmv2.2 during security scan (bug #77984)
• Definitions of number of threads for DPM and SRM servers at startup time (bug #77655)
• Parallel file transfers in dpm-drain (bug #61037)
• Increased performance of dpm-drain (bug #60109)
• Return SRM_TOO_MANY_RESULTS on srm-ls for incomplete listings (bug #46961)
• Added missing rfstat man page (bug #83247)
• Added filesystem selection based on assign weights (bug #82361)
• Fixed error message in dpm-modifypool with too many groups specified (bug #82339)

What's new

• Retrial for root requests after db reconnection (bug #75064)
• Conditional condrestart action in the init.d startup scripts (bug #76695)
• Added sonames in libraries (bug #57528)
• Added the possibility to send logs to syslog and have log levels (bug #83411)
• Fixed startup script when logfile does not contain a slash (bug #77388)
• Human readable dpns-ls -h (bug #20298)
• Update fs statistics with dpm-modifyfs --st RDONLY even if disabled (bug #78968)
• Fixed segfault in srmv1 and srmv2.2 during security scan (bug #77984)
• Definitions of number of threads for DPM and SRM servers at startup time (bug #77655)
• Parallel file transfers in dpm-drain (bug #61037)
• Increased performance of dpm-drain (bug #60109)
• Return SRM_TOO_MANY_RESULTS on srm-ls for incomplete listings (bug #46961)
• Added missing rfstat man page (bug #83247)
• Added filesystem selection based on assign weights (bug #82361)
• Fixed error message in dpm-modifypool with too many groups specified (bug #82339)

What's new

This version of the glite-UI includes changes in the following clients with respect to the previously released version: GFAL/lcg_utils, DPM and LFC, FTS and L&B.

What's new

This version of the glite-VOBOX includes changes in the following clients with respect to the previously released version: GFAL/lcg_utils, DPM and LFC, FTS, L&B, BDII and lcg-info.

What's new

This version of the glite-WN includes changes in the following clients with respect to the previously released version: GFAL/lcg_utils, DPM and LFC, FTS and L&B.

What's new

New version of CREAM including a fix in the glite-security-lcmaps-plugins-verify-proxy package. The fix addresses a problem affecting users holding a Terena grid certificate when they submit to CREAM through WMS.

What's new

• Treat "Oracle password soon to expire" as success (bug #46337)
• Fixed issue with startup and long connection strings (bug #83551)
• Fix for user update in read only mode (bug #82941)
• Fixed lfc_readdirg in the perl module (printing only the first letter of each entry) (bug #82403)
• Added GlueServiceAccessControlBaseRule to service publisher (bug #59704)
• Enabled Glue 2.0 publishing in yaim-lfc (bug #62209)
• Removed libclntsh.so.10.1()(64bit) from lfc oracle rpm (bug #85235)
• Retrial for root requests after db reconnection (bug #75064)
• Conditional condrestart action in the init.d startup scripts (bug #76695)
• Added sonames in libraries (bug #57528)
• Added the possibility to send logs to syslog and have log levels (bug #83411)
• Fixed startup script when logfile does not contain a slash (bug #77388)

What's new

This is an update of the torque client to address the vulnerability described in https://wiki.egi.eu/wiki/EGI_CSIRT:Alerts/Torque-2011-06-15 (See also http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2907).

This patch includes a new version of Torque, 2.5.7-1 from EPEL 5.

What's new

This is an update of the torque server to address the vulnerability described in https://wiki.egi.eu/wiki/EGI_CSIRT:Alerts/Torque-2011-06-15 (See also http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2907).

This patch includes a new version of Torque, 2.5.7-1 from EPEL 5.

What's new

This is an update of the torque utils to address the vulnerability described in https://wiki.egi.eu/wiki/EGI_CSIRT:Alerts/Torque-2011-06-15 (See also http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2907).

This patch includes a new version of Torque, 2.5.7-1 from EPEL 5.

What's new

This patch provides an updated BLAH to address some problems when SGE is used as batch system in the CREAM CE

What's new

This update is needed to bring in new versions of the LCMAPS-plugins-pep-c and PEP-API.

• The PEP-API needs updating to fix a randomly occuring time-out when gLExec tries to authorize and the Argus-PEPd-server. 
• The LCMAPS-plugin-c-pep needs updating in order to use the new PEP-API library. At the same time, the new plugin can now handle a situation when the X509_USER_PROXY (proxy of pilot job user) is located on an NFS partition with root-squash enabled.

What's new

This update fixes an issue with the YAIM configuration tool for glite-GLEXEC_wn.

See bug https://savannah.cern.ch/bugs/index.php?83779

The issue mostly affects sites with a large user database and a large number of worker nodes, as the configuration script wrongfully does a full listing of all user accounts in search of the glexec account.

What's new

This is a minor update of the Top BDII which fixes an sporadic installation issue (see bug report). The parameter dncachesize has been included in file /etc/bdii/bdii-top-slapd.conf to address some memory issues. In addition a new version of glite-info-update-endpoints that provide a new configuration option certification_status, which has been requested by EGI.

What's new

This patch provides an updated BLAH to address some problems when SGE is used as batch system in the CREAM CE

What's new

This release of L&B 2.1.21 introduces several hotfixes, namely to job registration and event delivery initiated by WMS, and also fixes several bugs that were affecting the interlogger under non-standard conditions (disk full, long-term inactivity, etc.).

What's new

This gLite-SGE_utils release implements the proper BLAH configuration (in /opt/glite/etc/blah.config) to support SGE/BLAH changes delivered by CREAM CE 1.6.6 for gLite 3.2/sl5_x86_64. Other bug fixes are also included. The reconfiguration of the service is mandatory.

What's new

Version 3.2.10 of the glite-UI contains a variety of updated clients and removes the need for some known issue workarounds documented for the previous release.

What's new

Version 3.2.11 of the glite-WN contains bug fixes and removes the need to apply several known issue workarounds which were documented for the previous release.

What's new

This new version of the glite-VOBOX contains the following changes:

• New version of WMS and LB clients.
  • The dependency glite-wms-brokerinfo-access has been added to the glite-VOBOX metapackage.
• New version of CREAM clients.
  • Provision of glite-ce-job-output command
  • Other bug fixes
  • Known issues: http://grid.pd.infn.it/cream/field.php?n=Main.KnownIssues
• New version of Data Management clients.
  • Added python 2.5 and python 2.6 bindings for Data Management clients
• New version of yaim clients including the SAGA adapters configuration.
• New version of yaim core.
• New version of glite-version (change doesn't actually affect glite-VOBOX).
• New version of VOMS-Admin
• New versions of lcg-infosites and lcg-ManageVOTag.

The following dependencies have been removed because they are no longer needed by the glite-VOBOX: glite-info-generic and glite-info-templates.

The following changes not directly affecting the gLite clients are also included in this release:

• New version of c-ares.
• VOMS fixes for memory leak problems.
• Minor security and gridsite fixes.

What's new

This patch addresses the vulnerability EGI #1569

dCache Server version changed from 1.9.5-19 to 1.9.5-25

Release Notes for dcache-server 1.9.5-25 can be found here: http://www.dcache.org/downloads/1.9/release-notes-1.9.5-25.html

What's new

This patch addresses the vulnerability EGI #1569

dCache Server version changed from 1.9.5-19 to 1.9.5-25

Release Notes for dcache-server 1.9.5-25 can be found here: http://www.dcache.org/downloads/1.9/release-notes-1.9.5-25.html

What's new

This patch addresses the vulnerability EGI #1569

dCache Server version changed from 1.9.5-19 to 1.9.5-25

Release Notes for dcache-server 1.9.5-25 can be found here: http://www.dcache.org/downloads/1.9/release-notes-1.9.5-25.html

What's new

This patch addresses the vulnerability EGI #1569

dCache Server version changed from 1.9.5-19 to 1.9.5-25

Release Notes for dcache-server 1.9.5-25 can be found here: http://www.dcache.org/downloads/1.9/release-notes-1.9.5-25.html

What's new

This version of glite-TORQUE_client depends on the current version of the Torque RPMS in the EPEL repository, 2.3.13.

In these RPMs, /var/spool/pbs is changed to /var/torque in the EPEL supplied Torque RPMs. This cannot be altered.

Because the Torque spool directory has changed location it is not recommended to upgrade a running Torque setup. Information about running jobs will be lost when the new RPMs are installed. Please see the detailed release notes.

What's new

This version of glite-TORQUE_server depends on the current version of the Torque RPMS in the EPEL repository, 2.3.13.

In these RPMs, /var/spool/pbs is changed to /var/torque in the EPEL supplied Torque RPMs. This cannot be altered.

Because the Torque spool directory has changed location it is not recommended to upgrade a running Torque setup. Information about running jobs will be lost when the new RPMs are installed. Please see the detailed release notes.

What's new

This version of glite-TORQUE_utils depends on the current version of the Torque RPMS in the EPEL repository, 2.3.13.

In these RPMs, /var/spool/pbs is changed to /var/torque in the EPEL supplied Torque RPMs. This cannot be altered.

Because the Torque spool directory has changed location it is not recommended to upgrade a running Torque setup. Information about running jobs will be lost when the new RPMs are installed. Please see the detailed release notes.

External dependencies have been cleaned up: dependency bouncycastle-glite removed.

What's new

The main purpose of this site-level BDII release is to address two issues. One issue relating to the case sensitivity of GLUE 2.0 and how this is handled in the BDII. Another issue relating to how multivalued attributes are handled in the BDII. In addition, a number of small packaging issues have also been addressed, see the rpm change log for more details.

What's new

The main purpose of this top-level BDII release is to address the GOC DB URL change. In addition, two issues were also addressed. One issue relating to the case sensitivity of GLUE 2.0 and how this is handled in the BDII. Another issue relating to how multivalued attributes are handled in the BDII. A number of small packaging issues have also been addressed, see the rpm change log for more details.

What's new

This is the first release of glite-CLUSTER. It is a new node type that can publish information about clusters and subclusters in a site, which can be used by any number of compute elements.

To make the glite-CLUSTER work with the CREAM CE please follow the instructions published as part of the Details for this update.

What's new

This new version of the glite-WN contains the following changes:

• FTS clients added as new dependencies.
• New version of WMS and LB clients.
• New version of Data Management clients.
  • Added python 2.5 and python 2.6 bindings for Data Management clients.
• New version of yaim clients including the SAGA adapters configuration.
• New version of yaim core.
• New version of glite-version (change doesn't actually affect glite-WN).
• New version of VOMS-Admin.
• New versions of lcg-infosites and lcg-ManageVOTag.

What's new

This patch includes only the fix for a problem concerning truncation of arguments, which is considered a critical issue for LHC-B

What's new

This version has been prepared after receiving feedback from production sites. It includes a set of bug fixes that should leave CREAM in a much more stable and reliable state for production deployment.

• Staging option in PBS is configurable, to be able to deal with Torque (new and old versions) and PBSPro
• VO setting (as VirtualOrganisation variable) available and usable in xxx_local_submit_attributes.sh script (see http://grid.pd.infn.it/cream/field.php?n=Main.ForwardOfRequirementsToTheBatchSystem)
• Fixed a problem in the connection between CREAM and the old blparser
• Fixed a problem with sudoers file generation
• Other bug fixes

What's new

This release of gLExec 0.8 is fully backwards compatible with both the previous versions 0.7 and 0.6.8. It relaxes a few restrictions made in version 0.7 which were too strict and broke backwards compatibility with version 0.6.8 (when not using YAIM). In addition, a number of new glexec.conf options are introduced. All their default values are ensuring backwards compatibility.

What's new

This release of L&B 2.1.17 introduces a few minor hotfixes, namely to BDII reporting. There are no functionality changes.

What's new

This release of L&B 2.1.18 introduces a few minor hotfixes, namely to the processing of L&B statistics and L&B's log output.

What's new

With this release of LFC 1.8.0-1 a number of bug fixes, a voms related memory leak fix and the user banning feature are introduced.

• "Please make symlinks within python-lfc relative" (bug #73077)
• servers crash when client passes too many FQANs in the proxy (bug #72382)
• Extra information (host, status) to be returned by lfc_getreplicas (bug #72361)
• banning of users and groups (bug #43710)
• use finger to determine home directory only when starting service (bug #69716)
• remove bashisms in LFC/DPM init scripts (bug #68430)
• Memory leak in voms-api-cpp (bug #71102)

What's new

With this release of LFC 1.8.0-1 a number of bug fixes, a voms related memory leak fix and the user banning feature are introduced.

• "Please make symlinks within python-lfc relative" (bug #73077)
• servers crash when client passes too many FQANs in the proxy (bug #72382)
• Extra information (host, status) to be returned by lfc_getreplicas (bug #72361)
• banning of users and groups (bug #43710)
• use finger to determine home directory only when starting service (bug #69716)
• remove bashisms in LFC/DPM init scripts (bug #68430)
• Memory leak in voms-api-cpp (bug #71102)

What's new

This release fixes a series of security vulnerabilities affecting VOMS Admin 2.5.3 and some other bugs.

The vulnerabilities are described in this SVG advisory: https://wiki.egi.eu/wiki/SVG:Advisiory-SVG-2011-505

What's new

This release fixes a series of security vulnerabilities affecting VOMS Admin 2.5.3 and some other bugs.

The vulnerabilities are described in this SVG advisory: https://wiki.egi.eu/wiki/SVG:Advisiory-SVG-2011-505

What's new

This update of the top level BDII enables support for OpenLDAP 2.4 and addresses the degradation problems seen in production.

The main problem addressed in this release is the fix for the performance degradation problem seen in production by some sites. For more details about this fix please see the relevant bug report. In order to fix this issue, OpenLDAP 2.4 is required and this release contains the necessary changes that enable this version to be used. Another performance improvement is the option to use a RAM disk for the database files.

Please note that if you set BDII_RAM_DISK=yes it is advisable to have at least 4GB of RAM in the machine, because a lot of space can be taken by the transaction log files of the LDAP DB (depending on the log level).

Bugs fixed and new features

• Please make symlinks within python-dpm relative (bug #73077)
• servers crash when client passes too many FQANs in the proxy (bug #72382)
• possibility to set an environment variable RFIO_TRACEFILE
• possibility to set the log level when starting rfiod (option -L)
• new method rfio_rcp (third party rfcp)
• banning of users and groups (bug #43710)
• use finger to determine home directory only when starting service (bug #69716)
• remove bashisms in LFC/DPM init scripts (bug #68430)

Bugs fixed and new features

• Please make symlinks within python-dpm relative (bug #73077)
• servers crash when client passes too many FQANs in the proxy (bug #72382)
• possibility to set an environment variable RFIO_TRACEFILE
• possibility to set the log level when starting rfiod (option -L)
• new method rfio_rcp (third party rfcp)
• banning of users and groups (bug #43710)
• use finger to determine home directory only when starting service (bug #69716)
• remove bashisms in LFC/DPM init scripts (bug #68430)
• fix memory leak in the SRM server due to a VOMS library problem (bug #71041)
• xrootd plugin v2.2 - https://twiki.cern.ch/twiki/bin/view/LCG/DpmXrootAccess22

The Argus 1.2 release fixes some bugs and implement some new features.

PAP features:

• The pap-admin CLI now implements the obligation management commands 'add-obligation' and 'remove-obligation'. These commands can be used to add/remove obligations to/from existing policies.
• The pap-admin CLI add-policy command now supports the creation of policy containing obligations at resource or action scope.

PEP daemon features:

• The group mapfile now allows DN and FQAN based group names mapping.
• The gridmap POSIX account mapping obligation handler now handles DN and FQAN based account mapping. DN based mapping is preferred upon FQAN based mapping (configurable).
• The gridmap files now support FQAN pattern matching as described in EGEE document https://edms.cern.ch/file/975443/1/EGEE-III-JRA1_FQAN_wildcard_v1.1.pdf
• A new generic grid authorization profile PIP handles both the Grid CE v1.0 and Grid WN v1.0 authorization profiles.

What's new

• Fixed some problems in the new BLAH blparser for which in some cases jobs were wrongly reported as "lost" (done with reason 999)
• Addressed a performance problem affecting the proxy renewal operation
• PBS submission script created by BLAH is now compliant with newer versions of Torque wrt stagein/stageout directives (-W option)
• CREAM sandbox dir is now relocatable also at yaim level
• Other bug fixes

L&B 2.1 is an evolution of L&B 2.0

What's new

• IPv6 compliance
• Adoption of the common logging format
• Collection aware purging
• WebService interface supporting basic AGU / Glue 2.0
• Advanced authorization with unified configuration
• Elementary native support for CREAM jobs
• Ability to log sandbox transfer progress as a specific job type
• Configuration tuned to allow collocation with WMS
• Job rate and state transition time statistics