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.

While running YAIM function config_torque_submitter_ssh an error message regarding munge may be printed: munge: Error: Unable to access "/var/run/munge/munge.socket.2": No such file or directory

This is harmless and may be ignored.

These are the release notes for Torque:

Warning: Significant change, munge enabled - action required:

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 ChangeLog. The significant changes that require action prior to upgrade are however detailed above.