This is an XrdHttp issue. I already mentioned this in #750. In our setup this gets triggered in the SSL_accept part:
https://github.com/xrootd/xrootd/blob/master/src/XrdHttp/XrdHttpProtocol.cc#L662
And some logs concerning this:
200331 14:32:18 11179 ?:475@fts3devel05 sysXrdHttp: received dlen: 16
200331 14:32:18 11179 ?:475@fts3devel05 sysXrdHttp: received dump: 22 03 01 02 00 01 00 01 -04 03 03 51 -41 41 40 00
200331 14:32:18 11179 ?:475@fts3devel05 sysXrdHttp: This does not look like http at pos 0
200331 14:32:18 11179 ?:475@fts3devel05 sysXrdHttp: This may look like https
200331 14:32:18 11179 ?:475@fts3devel05 sysXrdHttp: Protocol matched. https: 1
200331 14:32:18 11179 ?:475@fts3devel05 sysXrdHttp: Process. lp:0x7ff7a5bc6818 reqstate: 0
200331 14:32:18 11179 ?:475@fts3devel05 sysXrdHttp: Setting host: [2001:1458:201:e3::100:4d1]
200331 14:32:18 11179 ?:475@fts3devel05 sysXrdHttp: Entering SSL_accept...
200331 14:32:18 11179 ?:475@fts3devel05 sysXrdHttp: SSL_accept returned :-1
140701696083712:error:80066405:lib(128):func(102):reason(1029):sslutils.c:1915:
140701696083712:error:80066411:lib(128):func(102):reason(1041):sslutils.c:2110:: CRL has expired [subject=/DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=tbeerman/CN=722011/CN=Thomas Beermann,issuer=/DC=ch/DC=cern/CN=CERN Grid Certification Authority]
140701696083712:error:14089086:SSL routines:ssl3_get_client_certificate:certificate verify failed:s3_srvr.c:3327:
200331 14:32:18 11179 sysXrdHttp: Cleanup
200331 14:32:18 11179 sysXrdHttp: Reset
200331 14:32:18 11179 sysXrdHttp: XrdHttpReq request ended.
Hope this helps,
Elvin
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
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