As a followup; the log indicaes that the client timed out and then retried the operation. This is indicated by the fact that the previous operation was still in progress. It's easy to determine this, if the previous stat of the operation is equal to the timeout value (typically 30 minutes) when the next login occurs, then you know the problem exists in he timeout retry code. Simply set the timeout to be vey short and test that way with Castor. Andy On Wed, 16 Sep 2015, Elvin Sindrilaru wrote: > > Happens quite often now in CASTOR for diskservers which are under heavy load. It has the following signature: > > 150916 17:43:22 21073 XrootdXeq: alicedaq.8138:441@aldaqtdsm03 pvt IPv4 login as alicedaq > 150916 17:43:22 21073 alicedaq.8138:441@aldaqtdsm03 XrootdProtocol: endsess 14245:353.19908 > 150916 17:43:22 21073 alicedaq.8138:441@aldaqtdsm03 XrootdProtocol: endsess 14245:353.19908 rc=4 (Resource temporarily unavailable) > 150916 17:43:22 time=1442418202.152684 func=open level=INFO logid=a912d31c-5c89-11e5-bf06-001b21551dbc [log in to unmask]:1094 tid=140534474995456 source=XrdxCastor2Ofs:448 tident=alicedaq.8138:441@aldaqtdsm03 path=/castor/cern.ch/alice/raw/technical/2015/09/16/16/15000236105030.1319.root, opaque=mode=644&oss.asize=1865279545, isRW=1, open_mode=4002, file_ptr=0x7fd0d24ed010 > 150916 17:43:22 time=1442418202.152714 func=ExtractTransferInfo level=ERROR logid=a912d31c-5c89-11e5-bf06-001b21551dbc [log in to unmask]:1094 tid=140534474995456 source=XrdxCastor2Ofs:1000 tident=alicedaq.8138:441@aldaqtdsm03 no diskmanager opaque information i.e. castor.pfn2 missing > 150916 17:43:22 17023 castor2ofs_open: alicedaq.8138:441@aldaqtdsm03 Unable to get diskmanager opaque info (pfn2) ; input/output error > > The opaque information should have contained the pfn2 info. > > Btw, @abh3 do you have any suggestion how I can easily get the server in a state where it triggers a retry on the client side for open? > > --- > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/287 --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/287#issuecomment-141007606 ######################################################################## 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