Reply to this email directly or view it on GitHub.
Just for future reference, one more flavor of the same problem. The difference is now that the opaque info is present but the file is opened in read-only mode the second time. And when the client tries to do a write as it requested initially, it gets a bad file descriptor ....
150916 18:08:49 time=1442419729.151055 func=open level=INFO logid=373c4864-5c8d-11e5-ba88-2c600c20da16 unit=[log in to unmask]:1094 tid=140656173213440 source=XrdxCastor2Ofs
:448 tident=stage.10839:167@tpsrv108 [log in to unmask], opaque=castor.exptime=1442423329&[log in to unmask]&castor.pfn2=
0:15511:4f5fc56c-efeb-4365-b4c4-4dd0dff85aac&castor.signature=VLeSPg583SzSWeVBdTHEbrr4j76SL74tIQjbOM+LcehzxQtcStobfzW2D0LST3s57u5i0Y7t083HaRMFkSgmIw==&castor.txtype=tape, isRW=1, open_mode=4200, file_pt
r=0x7fedec039460
150916 18:08:49 13608 stage.10839:167@tpsrv108 castor2ofs_open: 4200-40600 [log in to unmask]
150916 18:09:49 16674 XrootdXeq: stage.10839:339@tpsrv108 pvt IPv4 login as stage
150916 18:09:49 16674 stage.10839:339@tpsrv108 XrootdProtocol: endsess 14508:167.9144
150916 18:09:49 16674 stage.10839:339@tpsrv108 XrootdProtocol: endsess 14508:167.9144 rc=4 (Resource temporarily unavailable)
150916 18:09:49 time=1442419789.020039 func=open level=INFO logid=5aeb8fc2-5c8d-11e5-a435-2c600c20da16 unit=[log in to unmask]:1094 tid=140656749336320 source=XrdxCastor2Ofs:448 tident=stage.10839:339@tpsrv108 [log in to unmask], opaque=castor.exptime=1442423329&[log in to unmask]&castor.pfn2=0:15511:4f5fc56c-efeb-4365-b4c4-4dd0dff85aac&castor.signature=VLeSPg583SzSWeVBdTHEbrr4j76SL74tIQjbOM+LcehzxQtcStobfzW2D0LST3s57u5i0Y7t083HaRMFkSgmIw==&castor.txtype=tape, isRW=0, open_mode=4000, file_ptr=0x7ff164029420
150916 18:09:49 19285 stage.10839:339@tpsrv108 castor2ofs_open: 4000-40600 [log in to unmask]
150916 18:09:49 19285 castor2ofs_write: stage.10839:339@tpsrv108 Unable to write [log in to unmask]; bad file descriptor
150916 18:09:49 19285 stage.10839:339@tpsrv108 XrootdResponse: sending err 3005: Unable to write [log in to unmask]; bad file descriptor
—
Reply to this email directly or view it on GitHub.
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