Hi Jon,
Googling this yielded some potential answers from Winnie and Kashif:
"Error in OLD GAA code: Could not get policy info:"
BTW: Assuming this happening on a UI, one way to attack it is to check
if it's the UI or the proxy. Can another user log in to the same UI
system, create a proxy and issue a similar command that works? If so,
it's the proxy. If not, it's the UI. Another thing you can do is print
two proxies, one that works, and one that doesn't. Then eyeball them
until you see a difference.
# voms-proxy-init --voms dteam
# openssl x509 -in /user2/sjones/.globus/x509up_u460 -text
Judging by the message, it looks like a version problem to me.
Cheers,
Steve
On 11/04/2015 10:13 AM, Jonathan Perkin wrote:
> Hi all,
>
> I have a user that can create a valid voms proxy but who gets a strange error when trying to read from the LFC. They found the
> $ export CSEC_TRACE=1
> symbol after a bit of googling and it dumps a nice stream of output, ending with:
>
> ERROR: initializing context: GSS Error: GSS Major Status: Authentication Failed, MECH Error: GSS Minor Status Error Chain:, globus_gsi_gssapi: SSLv3 handshake problems, globus_gsi_callback_module: Could not verify credential, globus_gsi_callback_module: Error with signing policy, globus_gsi_callback_module: Error in OLD GAA code: Could not get policy info: Minor status=201
> _Csec_send_token: Sending packet Magic: ca03 Type: 6, Len: 4
> 00 00 00 00
>
> send2nsd: NS002 - send error : Bad credentials
> Csec_clearContext: Clearing context
> Csec_unload_shlib: Entering
> /grid/t2k.org/nd280: Bad credentials
>
> Does anyone know what is going wrong? Other users at the same institute (presumably using the same middleware (emi-version-3.15.0-1.el6.x86_64) do not observe this issue.
>
> Cheers
>
> Jon
--
Steve Jones [log in to unmask]
Grid System Administrator office: 220
High Energy Physics Division tel (int): 43396
Oliver Lodge Laboratory tel (ext): +44 (0)151 794 3396
University of Liverpool http://www.liv.ac.uk/physics/hep/
|