Hi,
I’ve been running InfluxDB v2.0.8 in a Docker container without issues for a while now. I collect mainly network ping data using telegraf and recently I started to get the error
ts=2022-01-06T21:20:20.192628Z lvl=info msg="http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s" log_id=0YtJzV~l000 service=http
ts=2022-01-06T21:20:21.193420Z lvl=info msg="http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s" log_id=0YtJzV~l000 service=http
ts=2022-01-06T21:20:22.194211Z lvl=info msg="http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s" log_id=0YtJzV~l000 service=http
ts=2022-01-06T21:20:23.194960Z lvl=info msg="http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s" log_id=0YtJzV~l000 service=http
ts=2022-01-06T21:20:24.196203Z lvl=info msg="http: Accept error: accept tcp [::]:8086: accept4: too many open files; retrying in 1s" log_id=0YtJzV~l000 service=http
In my docker host (Ubuntu 20.10), I’ve increased the ulimit -n 65535
as suggested here
ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 14935
max locked memory (kbytes, -l) 489733
max memory size (kbytes, -m) unlimited
open files (-n) 65535
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) 14935
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
However the issue still persists. I’m not quite sure what is recommended when InfluxDB is running in a Docker container.
Any tips?
cheers