Difference: Update32-35 (2 vs. 3)

Revision 32012-02-09 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IgiGliteUpdates"
Line: 37 to 37
 
    • * Known issues:*
        • As with all glite-UI releases the correct way to update from a previous (RPM) based release is to use *yum groupupdate glite-UI*
        • The grid-env.sh written by yaim does not work with the standard version of zsh with SL5. See the known issue page
Changed:
<
<
>
>
 
  • WN - Version 3.2.12 of the glite-WN - it includes the following changes:
    • GFAL/lcg_utils has been updated to version 1.11.16-3. (patch #4642). Amongst other fixes this version avoids the generation of debug log files.
Line: 46 to 46
 
Changed:
<
<
  • TORQUE_[client|server|utils]
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).
>
>
The updated EPEL5 build of torque-2.5.7-1 as compared to previous versions enables munge[1] as an inter node authentication method.
It is highly advisable that prior to upgrading to version 2.5.7-1 of this torque package that munge is installed and enabled. A munge package[2] is of course available within EPEL5.
        [1] http://code.google.com/p/munge/ 
        [2] https://admin.fedoraproject.org/community/?package=munge#package_maintenance

To enable munge on your torque cluster:
        Install the munge package on your pbs_server and submission hosts in your cluster.
        On one host generate a key with /usr/sbin/create-munge-key
        Copy the key, /etc/munge/munge.key to your pbs_server and submission hosts on your cluster.
        Start the munge daemon on these nodes.. service munge start && chkconfig munge on

Warning: New internal format for Job arrays: 
TORQUE 2.5 uses a new format for job arrays. It is not backwards compatible with job arrays from version 2.3 or 2.4. Therefore, it is imperative that the system be drained of any job arrays BEFORE upgrading. Upgrading with job arrays queued or running may cause data loss, crashes, etc, and is not supported.
This update from 2.3.10 includes numerous bugfixes and enhancements. Please read the torque Change Log. The significant changes that require action prior to upgrade are however detailed above

 
Changed:
<
<
This patch includes a new version of Torque, 2.5.7-1 from EPEL 5.
These are the release notes for Torque:

Warning: Significant change, munge enabled - action required:

>
>
 
Deleted:
<
<
The updated EPEL5 build of torque-2.5.7-1 as compared to previous versions enables munge[1] as an inter node authentication method.
It is highly advisable that prior to upgrading to version 2.5.7-1 of this torque package that munge is installed and enabled. A munge package[2] is of course available within EPEL5.
[1] http://code.google.com/p/munge/
[2] https://admin.fedoraproject.org/community/?package=munge#package_maintenance

To enable munge on your torque cluster:
Install the munge package on your pbs_server and submission hosts in your cluster.
On one host generate a key with /usr/sbin/create-munge-key
Copy the key, /etc/munge/munge.key to your pbs_server and submission hosts on your cluster.
Start the munge daemon on these nodes.. service munge start && chkconfig munge on

Warning: New internal format for Job arrays:
TORQUE 2.5 uses a new format for job arrays. It is not backwards compatible with job arrays from version 2.3 or 2.4. Therefore, it is imperative that the system be drained of any job arrays BEFORE upgrading. Upgrading with job arrays queued or running may cause data loss, crashes, etc, and is not supported.
This update from 2.3.10 includes numerous bugfixes and enhancements. Please read the torque Change Log. The significant changes that require action prior to upgrade are however detailed above.

 

Prerequisites

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback