Print

Print


Uhm , and now

140709 17:45:51 10615 XrdLink: Unable to send file to
100.6882:[log in to unmask]; bad address
140709 17:45:51 10615 XrootdXeq: 100.6882:[log in to unmask] disc
0:00:00 (sendfile failure)
140709 17:45:51 10002 XrdLink: Unable to send file to
281.6760:[log in to unmask]; bad address


"bad address" ....

tom


On Wed, Jul 9, 2014 at 4:35 PM, Tommaso Boccali <[log in to unmask]>
wrote:

> Ciao, I have a server under very heavy load (1 GB/s incoming, 200 MB/s
> outgoing - these are bytes, not bits!), which is failing all the xrootd
> file serving, with stuff like
>
> 140709 16:22:20 7453 XrdLink: Unable to send file to
> cmsplt00.41552:[log in to unmask]; operation canceled
> 140709 16:22:20 7453 XrootdXeq: cmsplt00.41552:[log in to unmask]
> disc 0:05:21 (sendfile failure)
>
> I see no other real problems on that ... any hint on what can be the
> problem?
> FS? network saturated?
>
> I really see tons of rootd connections:
>
> [root@stormgf1 cms]# netstat|grep rootd|wc
>    2033   12203  180956
>
>  this is 5 min after a restart, and they are still increasing ....
>
> the other thing I do not get is why the other server (stormgf2.pi.infn.it)
> is getting instead < 1/2 of the files
>
>
> can you confirm the error is just due to high traffic and NOT to (for
> example) max threads reached or so?
>
> tom
>
> --
> Tommaso Boccali
> INFN Pisa
>



-- 
Tommaso Boccali
INFN Pisa

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1