 |
 |
Wierd, where do that status code come from? It wasn't suppose to be returned to old clients at all. I will need to look to see what happened (and review the ticket once again). On Fri, 19 Jun 2020, simonmichal wrote: > @wyang007 : this should fix the problem with `--tlnodata`: https://github.com/xrootd/xrootd/commit/1499b758b3888b9c8e6d8218910874b650228f76 > > However, the problem remains for transfers with data streams, e.g.: `xrdcp -S 1` > > ``` > [2020-06-19 03:46:51.071785 -0700][Dump ][AsyncSock ] [griddev06.slac.stanford.edu:1094.1] Received message header for 0x440438c0 size: 8 > [2020-06-19 03:46:51.071825 -0700][Dump ][XRootD ] [griddev06.slac.stanford.edu:1094] Got unrecognized response 4007 to message kXR_read (handle: 0x00000000, offset: 0, size: 1000000) > [2020-06-19 03:46:51.071851 -0700][Error ][AsyncSock ] [griddev06.slac.stanford.edu:1094.1] Socket error encountered: [ERROR] TLS error > [2020-06-19 03:46:51.071925 -0700][Debug ][ExDbgMsg ] [griddev06.slac.stanford.edu:1094] Calling MsgHandler: 0x1184db0 (message: kXR_read (handle: 0x00000000, offset: 0, size: 1000000) ) with status: [ERROR] Invalid response. > ``` > > The code `4007` corresponds to `kXR_status`, which is not yet supported in the client. > > To be investigated. > > -- > You are receiving this because you are subscribed to this thread. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/1214#issuecomment-646601283 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1214#issuecomment-646832655 ######################################################################## 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