On 26/6/11 3:05 PM, Maarten Litmaath wrote:
> Hi Elena,
>
>> LCMAPS 1: 2011-06-25.18:38:55Z-23986 : Error: pep_authorize(request,response)
>> failed: 11: [11]: authorize: processing error:
>> PEPd[https://lcgargus.shef.ac.uk:8154/authz]: sending XACML request failed:
>> curl[7]: couldn't connect to server.
>
> Can the WN actually reach the server? Try:
>
> telnet lcgargus.shef.ac.uk 8154
>
> If that works, check the Argus logs for requests that fail, but see below.
>
>> [...]
>>
>> If I'm trying to perform a check recommended by Oxford guys I'm getting the same error:
>> [pilops11@gw001 root]$ export GLEXEC_CLIENT_CERT=/tmp/x509up_u60730
>> [pilops11@gw001 root]$ export GLEXEC_SOURCE_PROXY=/tmp/x509up_u60730
>> [pilops11@gw001 root]$ export X509_USER_PROXY=/tmp/x509up_u60730
>> [pilops11@gw001 root]$ /opt/glite/sbin/glexec /usr/bin/id
>
> Try setting these variables as well:
>
> export LCMAPS_DEBUG_LEVEL=5
> export LCMAPS_LOG_LEVEL=5
>
> Then /var/log/glexec/lcas_lcmaps.log will have more details.
>
> If that still does not help enough, open a GGUS ticket for Argus...
For reference, there is another interesting debugging possibility build in
the LCMAPS C PEP plug-in:
You can configure the lcmaps.db file for glexec to have the "--pep-c-debug"
option enabled with the plug-in's configuration.
Online manpage (with configuration examples) can be found here:
http://www.nikhef.nl/grid/lcaslcmaps/man/lcmaps_plugins_c_pep.8.html
The result will be that gLExec will give you the details from the Argus PEP
C library on the stderr, including the HTTP messages. This is intended for
debugging/test purposes.
But before you do this, double check the Argus version and the Argus PEP C
library version with those on the GGUS tickets. It might be a known issue.
Oscar
|