Please do as I don't see how that string would ever get there. That is not
a valid trace identifier for native xrootd. Do you have a log I can look
at as the trace identifier would be sprinkled throughout.
On Tue, 19 May 2020, Oliver Freyermuth wrote:
> I'm using pure XRootD here. Will add some log lines tomorrow, I actually only found that the Eventstream-script was given some TID with spaces, but did not correlate that to what XRootD itself has logged yet.
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1200#issuecomment-631188675
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1200#issuecomment-631196849",
"url": "https://github.com/xrootd/xrootd/issues/1200#issuecomment-631196849",
"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