Too many open files (24) - how?

[Jorsher]

I have three clients that repeatedly run into these errors. One has ~40k torrents, two have ~115k torrents each.

I'm using transmission-daemon 4.0.5 running under the user 'transmission' in a Debian systemd-nspawn container on TrueNAS.

Code: Select all

root@tm:~# sudo -u transmission /bin/bash -c "ulimit -a"
real-time non-blocking time  (microseconds, -R) unlimited
core file size              (blocks, -c) 0
data seg size               (kbytes, -d) unlimited
scheduling priority                 (-e) 0
file size                   (blocks, -f) unlimited
pending signals                     (-i) 254999
max locked memory           (kbytes, -l) 8202720
max memory size             (kbytes, -m) unlimited
open files                          (-n) 1048576
pipe size                (512 bytes, -p) 8
POSIX message queues         (bytes, -q) 819200
real-time priority                  (-r) 0
stack size                  (kbytes, -s) 8192
cpu time                   (seconds, -t) unlimited
max user processes                  (-u) 254999
virtual memory              (kbytes, -v) unlimited
file locks                          (-x) unlimited

ulimit shows the user 'transmission' is limited to 1048576, and I don't believe it's actually hitting that limit.

Code: Select all

ls -l /proc/153/fd | wc -l

...only shows 653, which is even less than the default '1024' open files. Most of them are sockets.

What else could I troubleshoot? Not sure what else to check.

[Jorsher]

The above file limits were for the user 'transmission'

Today I also set higher file limits for the daemon-transmission service, and higher file limits for the systemd-nspawn container service, and after an hour it seems to be fine. May not have been necessary to edit open file limit for the user, but definitely isn't hurting.

If the issue pops up again, will edit.

Closed.