Print

Print

CMS is struggling to get RelVals for a data taking out the door because of a exception due to the Xrootd client. See:

https://ggus.eu/index.php?mode=ticket_info&ticket_id=128888

(particularly, the attached log has a full stdout).

It seems that the client will randomly be unable to handle a ReadV response. It looks like it subsequently gets confused by the state of the session, causing the server to abruptly close the socket.

CMSSW then retries against the EOS headnode and gets a socket timeout.

I'd like to focus on the ReadV response issue; it's not clear if the issue with the socket timeout is related to this.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"XrdCl is not correctly parsing client response? (#528)"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/528"}}}

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