Hi,

This error has been verified at least in xrootd 4.11.3 and I suspect it's also in 4.12.3 as we were seeing the same problem when debugging something else.

The problem has been verified on both our head-node (VM hosted on a libvirtd+CentOS8 host) and on a bare metal Dell Inc. PowerEdge R510 both running CentOS7.8
Unfortunately the problem of connection resets happens for both local and remote connections to the same service which rules out most of the kernel settings I would normally check.

[root@srm ~]# cat /proc/`pidof xrootd`/limits
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        unlimited            unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             30000                128301               processes
Max open files            65536                65536                files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       128301               128301               signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0
Max realtime timeout      unlimited            unlimited            us

Additionally the following have been set in the override.conf (probably unrelated but for sake of clarity):

Environment=MALLOC_ARENA_MAX=4
Environment=XRD_MAXREDIRECTCOUNT=1

LimitCORE=infinity
Environment=DAEMON_COREFILE_LIMIT=unlimited

I've attached the xrootd config (minus-secrets) from one of the disk nodes (bare metal) which have had this problem.
Unfortunately this is as deployed by puppet for DPM modulo some reduction in whitespace.
xrootd.cfg.txt

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

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