Thanks Ewan! However, after checking this repo, it seems I'm already up
to date:
[root@epgf04 ~]# yum list voms-clients3 voms-api-java3
Loaded plugins: priorities, protectbase, security
Repository 'CVMFS' is missing name in configuration, using id
Repository 'EGI-trustanchors' is missing name in configuration, using id
Repository 'HEP_OSlibs' is missing name in configuration, using id
Repository 'dag' is missing name in configuration, using id
176 packages excluded due to repository priority protections
0 packages excluded due to repository protections
Installed Packages
voms-api-java3.noarch 3.0.1-1.sl6 @EMI-3-updates
voms-clients3.noarch 3.0.3-1.sl6 @EMI-3-updates
and this is with adding the voms-clients repo as well :( Mabye I've
messed the config up somehow - I'll try a reinstall tomorrow of one of
the nodes and see...
Thanks,
Mark
On 07/09/13 17:12, Ewan MacMahon wrote:
>> -----Original Message-----
>> From: Testbed Support for GridPP member institutes [mailto:TB-
>> [log in to unmask]] On Behalf Of Mark Slater
>> Sent: 07 September 2013 16:22
>>
>> I've just upgraded all my workers, CREAM CE and Torque to SL/EMI3 and I'm
>> having some problems with Atlas pilot jobs. One set of workers seem to run
>> OK but another set (C6145s) are failing. I'm not certain yet as to whether
>> this is due to the hardware difference or if something happened this
>> morning across the board and I'm just seeing jobs submitted to the one set
>> of hardware, but anyway: Has anyone seen this error before?
>>
> That's consistent with not having the fixed voms-clients3 package from the
> product team; the one in the EMI3 repo is still buggy.
>
> The release announcement for the new version is here:
> http://italiangrid.github.io/voms/2013/08/21/voms-clients-3-0-3-released.html
> and the download instructions are here:
> http://italiangrid.github.io/voms/download.html
> but if I were you, I'd just cherry-pick the appropriate packages from
> the voms repo, rather than actually configuring it properly on the
> nodes.
>
> Ewan
|