Hi Andrew,
I just added a counter on the XrdPfc/XrdPfc.cc:
45 int ct = 0;
656 ct++;
658 cout << "GSTREAM" << ct << endl;
The error occurred on XrdPfc/XrdPfcInfo.cc:
543 TRACE(Warning, trace_pfx << "Corrupted access record,
skipping.");
618 TRACE(Warning, trace_pfx << "Corrupted access record,
skipping.");
and XrdPfc/XrdPfcFile.cc:
201 TRACEF(Error, "ioActive for io " << io <<" called on a closed
file. This should not happen.");
Thank you!
*--Fábio Andrijauskas*
On Mon, Oct 4, 2021 at 5:12 PM Andrew Hanushevsky ***@***.***>
wrote:
> Could you point me to the modified code along with line numbers where the
> modification occurred? As for "Corrupted access record" this is he first
> time it has been reported; so, Matevz may have some insight into this.
>
> On Mon, 4 Oct 2021, Fabio Andrijauskas wrote:
>
> > I am creating code on the OSG Xrootd collector to process GStream data.
> The test architecture is:
> >
> > xrootd (Gstream configured) -> collector -> rabbitqm -> rabbitqm reader
> >
> > For the GStream, the configuration is:
> >
> > `xrootd.monitor all flush 2s window 2s fstat 2 lfn ops xfr 2 dest fstat
> info user pfc tcpmon ccm host:9940
> > `
> >
> > For debug, I added code and compiled a version of xrootd to show a
> counter of how many requests the xrootd tries to send. And after some
> requests (~5000), the number of requests is larger than the counter on
> xrootd. There is no UDP dropped packets or anything on logs on the system.
> Otherwise, on the xrootd logs sometimes it shows:
> >
> > Corrupted access record, skipping
> > ioActive for io " << io <<" called on a closed file. This should not
> happen
> >
> >
> >
> >
> > --
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly or view it on GitHub:
> > https://github.com/xrootd/xrootd/issues/1525
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/xrootd/xrootd/issues/1525#issuecomment-933952125>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACEEH76K3GV2BHV2F3HC3NLUFI7FZANCNFSM5FKQTC3A>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1525#issuecomment-933958230",
"url": "https://github.com/xrootd/xrootd/issues/1525#issuecomment-933958230",
"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
