Hi,
problem ssems to be solved:
The CRLs were corrupt (but produced no error message). Now over night
the CRLs expired (problem with cronjob) and voms-proxy-init generated an
error which made the situation clear.
After updating the CRLs voms-proxy-init runs fine.
Thank for all the good advice which was nevertheless helpful for
spotting the problem.
Cheers,
David
Jan Just Keijser wrote:
> Hi Torsten,
>
> for us, voms-proxy-init from either the glite-3.0.21 tarball or the
> glite-3.1.0-1 tarball work fine on SL4 x86_64 ; we have the exact same
> definition of the atlas-voms.cern.ch file that you have. What does an
> `ldd voms-proxy-init` tell you?
>
> Note that voms-proxy-init is built and linked against the globus SSL
> libraries and is completely independent of the libssl installed on the
> system.
>
> Finally, perhaps it helps to do a
> setarch i386 voms-proxy-init
> ?
>
> cheers,
>
> Jan Just Keijser
> System Integrator
> Nikhef
> Amsterdam
>
> Torsten Harenberg wrote:
>> Well.. we've only atlas-voms.cern.ch configured:
>>
>> # ls -als /opt/glite/etc/vomses | grep atlas
>> 4 -rw-r--r-- 1 root root 85 Aug 14 13:59 atlas-voms.cern.ch
>> # cat /opt/glite/etc/vomses/atlas-voms.cern.ch
>> "atlas" "voms.cern.ch" "15001"
>> "/DC=ch/DC=cern/OU=computers/CN=voms.cern.ch" "atlas"
>>
>> But as he tries to connect the correct server (and gets some packages
>> back), I assume this is not the problem here. I would assume it some
>> incompatibility between the voms software and e.g. the libssl, but
>> how to check this?
>>
>
>
--
Ever tried? Ever failed? No matter. Try Again! Fail again!
Fail better!
Samuel Beckett
+=====================================================+
| Dr. David Meder-Marouelli |
| mailto:[log in to unmask] |
| Bergische Universitaet Wuppertal |
| FB C - Physik Tel.: +49 (0)202 439-2631 |
| Gaussstr. 20 Fax : +49 (0)202 439-2811 |
| 42097 Wuppertal |
+=====================================================+
|