@rajanandakumar - perfect, here are the two lines that I was looking for: ``` [2020-08-02 08:56:08.987640 +0000][Dump ][XRootD ] [xrootd.echo.stfc.ac.uk:1094] Message kXR_readv (handle: 0x00000000, chunks: 627, total size: 9057777) has been successfully sent. ... [2020-08-02 09:02:01.021140 +0000][Dump ][XRootD ] [xrootd.echo.stfc.ac.uk:1094] Stream event reported for msg kXR_readv (handle: 0x00000000, chunks: 627, total size: 9057777) [2020-08-02 09:02:01.021152 +0000][Debug ][XRootD ] [xrootd.echo.stfc.ac.uk:1094] Handling error while processing kXR_readv (handle: 0x00000000, chunks: 627, total size: 9057777): [ERROR] Operation expired. ``` So, it looks like the timeout is set to something in the neighborhood of 350 seconds. To me, it's a bit more plausible to be hitting "real" timeouts at 350 seconds than 1,800 seconds (30 minutes)! -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1259#issuecomment-670578269 ######################################################################## 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