 |
 |
Just rerun with the origin started with the -d command line option to see where it stalled. On Mon, 4 May 2020, Derek Weitzel wrote: > Ah, ok. I set the value to `session`. The cache seems to just "stall"... it connects to the origin then nothing. > > Here's the origin's logs: > ``` > 200504 21:03:13 22229 XrdSched: running main accept inq=0 > 200504 21:03:13 22186 XrdInet: Accepted connection from 113@cache > 200504 21:03:17 22187 XrdSched: Now have 4 workers > 200504 21:03:17 22187 XrdSched: running monitor window clock inq=0 > 200504 21:03:17 22187 XrdSched: scheduling monitor window clock in 5 seconds > 200504 21:03:22 22281 XrdSched: running monitor window clock inq=0 > 200504 21:03:22 22281 XrdSched: scheduling monitor window clock in 5 seconds > 200504 21:03:27 22187 XrdSched: running monitor window clock inq=0 > 200504 21:03:27 22187 XrdSched: scheduling monitor window clock in 5 seconds > 200504 21:03:32 22281 XrdSched: running monitor window clock inq=0 > 200504 21:03:32 22281 XrdSched: scheduling monitor window clock in 5 seconds > 200504 21:03:37 22187 XrdSched: running monitor window clock inq=0 > 200504 21:03:37 22187 XrdSched: scheduling monitor window clock in 5 seconds > 200504 21:03:42 22281 XrdSched: running monitor window clock inq=0 > 200504 21:03:42 22281 XrdSched: scheduling monitor window clock in 5 seconds > 200504 21:03:43 22186 XrdProtocol: anon:113@cache terminated handshake not received > ... > ``` > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/1188#issuecomment-623706624 -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1188#issuecomment-623709736 ######################################################################## 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