@adriansev : from what I see after 30s a RequestTimeout happened:

[2022-01-19 23:20:02.098749 +0200][Dump   ][XRootD            ] [f01-120-179-e.gridka.de:1094] Sending message kXR_read (handle: 0x00000000, offset: 16784378, size: 8388608)
...
[2022-01-19 23:20:32.113471 +0200][Dump   ][XRootD            ] [f01-120-179-e.gridka.de:1094] Stream event reported for msg kXR_read (handle: 0x00000000, offset: 16784378, size: 8388608)

This is a non-recoverable error by definition: it is a user defined timeout that tells the XrdCl runtime to abort a request if it elapses.

Now, looking at the logs you guys do set a very short RequestTimeout of 30 seconds:

[2022-01-19 23:20:00.972606 +0200][Debug  ][Utility           ] Env: overriding entry: requesttimeout=1800 with 30

My advice would be to set the StreamTimeout to 30 seconds and leave the RequestTimeout with its default value.


Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1597/1061956231@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1597#issuecomment-1061956231", "url": "https://github.com/xrootd/xrootd/issues/1597#issuecomment-1061956231", "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