Dear all,
according to http://glite.cern.ch/R3.1/ the lcg-CE is supported for
security fixes until 30/04/2012. Does this include the 'torque'
dependency as well?
The new EPEL packages of the torque security update (bumped version to
2.5.7) are incompatible with the last lcg-CE:
[root@brutus-vm1 ~]# rpm -Fhv http://kojipkgs.fedoraproject.org/packages/torque/2.5.7/1.el4.1/x86_64/libtorque-2.5.7-1.el4.1.x86_64.rpm http://kojipkgs.fedoraproject.org/packages/torque/2.5.7/1.el4.1/x86_64/torque-2.5.7-1.el4.1.x86_64.rpm http://kojipkgs.fedoraproject.org/packages/torque/2.5.7/1.el4.1/x86_64/torque-client-2.5.7-1.el4.1.x86_64.rpm http://kojipkgs.fedoraproject.org/packages/torque/2.5.7/1.el4.1/x86_64/torque-docs-2.5.7-1.el4.1.x86_64.rpm
Retrieving http://kojipkgs.fedoraproject.org/packages/torque/2.5.7/1.el4.1/x86_64/libtorque-2.5.7-1.el4.1.x86_64.rpm
Retrieving http://kojipkgs.fedoraproject.org/packages/torque/2.5.7/1.el4.1/x86_64/torque-2.5.7-1.el4.1.x86_64.rpm
Retrieving http://kojipkgs.fedoraproject.org/packages/torque/2.5.7/1.el4.1/x86_64/torque-client-2.5.7-1.el4.1.x86_64.rpm
Retrieving http://kojipkgs.fedoraproject.org/packages/torque/2.5.7/1.el4.1/x86_64/torque-docs-2.5.7-1.el4.1.x86_64.rpm
error: Failed dependencies:
libtorque.so.2()(64bit) is needed by torque-client-2.5.7-1.el4.1.x86_64
libtorque.so.2 is needed by (installed) maui-client-3.2.6p21-snap.1224706197.2.slc4.i386
libtorque.so.2 is needed by (installed) torque-client-2.3.6-1cri.slc4.i386
libtorque.so.2 is needed by (installed) torque-drmaa-2.3.6-1cri.slc4.i386
torque = 2.3.6-1cri.slc4 is needed by (installed) torque-client-2.3.6-1cri.slc4.i386
torque = 2.3.6-1cri.slc4 is needed by (installed) torque-devel-2.3.6-1cri.slc4.i386
On the other hand I'm still able to submit jobs from the old torque
client to an updated server, although this should be impossible in
theory ... I just had to do something like this
qmgr -c 'set server authorized_users=*@<lcg-ce-host>'
as it is documented here:
http://www.clusterresources.com/torquedocs21/1.3advconfig.shtml
So I wonder whether munge is used at all ... As it is stated there, you
have to explicitly configure munge support during compilation time. Is
this true? According to
http://koji.fedoraproject.org/koji/buildinfo?buildID=257938 the EPEL
rpms don't use this '–enable-munge-auth' configure switch ...
Could someone please enlighten me how this should be handled? Is there a
documentation on the update plan somewhere?
Thanks & Cheers,
Andreas
--
| Andreas Haupt | E-Mail: [log in to unmask]
| DESY Zeuthen | WWW: http://www-zeuthen.desy.de/~ahaupt
| Platanenallee 6 | Phone: +49/33762/7-7359
| D-15738 Zeuthen | Fax: +49/33762/7-7216
|