Since this is a client problem, set the following envar and restart:
XRD_LOGLEVEL=Debug
We can turn on additional debugging if this doesn't yield sufficient
information. The log file will be rather large so just send it to me via
email or provide a pointer so I can fetch it. The log file may have
informtion that you would rather not make public so avoid posting it.
Andy
On Thu, 11 Feb 2021, pmusset wrote:
> Really strange. No I dont have the problem with three of the four sites I tried yesterday. Still happens with an EOS instance at Cern
> Normally nothing has changed since yesterday. Or I didnt pull correctly my docker image with the rc7 and it only worked today.
>
> Which debug level should I rise ?
>
> Is there still an issue where xrdcl-http doesnt check in `/etc/grid-security/certificates` for the certificates ? Could it be linked to that ? On XrootD 4 I know I had to do
> ```
> RUN cp /etc/grid-security/certificates/*.pem /etc/pki/ca-trust/source/anchors/ && update-ca-trust extract
> ```
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1394#issuecomment-777440015
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1394#issuecomment-777847167",
"url": "https://github.com/xrootd/xrootd/issues/1394#issuecomment-777847167",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
