 |
 |
We observe the following problem with xrootd 3.3.2:
'''
130527 10:20:50 29232 XrootdXeq: daemon.17349:63@lxfssl4102 login as daemon
[..some time..]]
130527 11:55:13 4686 XrdPoll: Sever event occured for daemon.17349:63@lxfssl4102
130527 11:55:13 9327 XrootdXeq: daemon.17349:63@lxfssl4102 disc 1:34:23 (socket error)
130527 11:55:13 4686 XrdPoll: Sever event occured for daemon.17349:63@lxfssl4102
130527 11:55:13 4686 XrdPoll: Unable to exclude link daemon.17349:63@lxfssl4102; no such file or directory
130527 11:55:13 4686 XrdPoll: Sever event occured for daemon.17349:63@lxfssl4102
130527 11:55:13 4686 XrdPoll: Unable to exclude link daemon.17349:63@lxfssl4102; bad file descriptor
130527 11:55:13 4686 XrdPoll: Sever event occured for daemon.17349:63@lxfssl4102
130527 11:55:13 4686 XrdPoll: Unable to exclude link daemon.17349:63@lxfssl4102; bad file descriptor
130527 11:55:13 4686 XrdPoll: Sever event occured for daemon.17349:63@lxfssl4102
'''
Once this happens the XRootd server spit's out in a tight loop the same error message until the disk is filled up from the logfile ...
—
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