2011/5/16 Andrew Hanushevsky <[log in to unmask]>: >> Question 2) >> 110515 11:47:32 11957 XrootdXeq: usatlas1.12016:[log in to unmask] login >> 110515 11:47:32 11957 usatlas1.12016:[log in to unmask] XrootdProtocol: >> endsess 11955:61.163901 >> 110515 11:47:32 11957 usatlas1.12016:[log in to unmask] XrootdProtocol: >> endsess 11955:61.163901 rc=-3 (No such process) >> 110515 11:47:32 11957 usatlas1.12016:[log in to unmask] XrootdResponse: >> sending err 3011: session not found >> Is this "session not found" the cause of the failures? > >>> This is a request to end a session that apparently does not >>> exist... I will have a closer look. > > Actually, this is a bug on the client's part. As far as I remember it seems > to have been introduced about Summer 2010. The client is supposed to keep > track of the last session it had to a server. When it disconnects and then > reconnects it is supposed to try to cancel that last session. The error > recovery action corrects duplicate session problems involving held locks and > open files. Since last summer it appears that the client always sends an end > session request whether or not there actually was a previous session. > Annoying but not fatal. OK. I was not aware of this. https://savannah.cern.ch/bugs/index.php?82354 Cheers, Lukasz