V4 issues on unraid container

[blassley]

Appears something is going on with the newest release. Here is what the log shows, it doesn't happen immediately, container runs for a few hours then shuts down with this

WARNING] 240/100039 (1) : config : missing timeouts for backend 'docker-events'. | While not properly invalid, you will certainly encounter various problems | with such a configuration. To fix this, please ensure that all following | timeouts are set to a non-zero value: 'client', 'connect', 'server'. [WARNING] 240/100039 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory Proxy dockerbackend started. Proxy docker-events started. Proxy dockerfrontend started. [NOTICE] 240/100039 (1) : New worker #1 (12) forked

[josep-tecnativa]

Thanks for reporting!

From the logs you shared, I don’t see anything that would trigger a container shutdown — those are just HAProxy warnings (about timeouts and missing state file) and not fatal errors.

I remember a related Docker bug moby/moby#49511 (comment)

[TheGITofTeo997]

Hello, sadly i am encountering the same issue on my NAS, since the version updated. The container does a loop of this:

[NOTICE]   (12) : haproxy version is 3.2.4-98813a1
[WARNING]  (12) : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[NOTICE]   (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
[ALERT]    (12) : [haproxy.main()] Cannot raise FD limit to 8034, limit is 1024.
[NOTICE]   (1) : haproxy version is 3.2.4-98813a1
[WARNING]  (1) : Failed to load worker!

[blassley]

Hello, sadly i am encountering the same issue on my NAS, since the version updated. The container does a loop of this:

[NOTICE]   (12) : haproxy version is 3.2.4-98813a1
[WARNING]  (12) : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[NOTICE]   (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
[ALERT]    (12) : [haproxy.main()] Cannot raise FD limit to 8034, limit is 1024.
[NOTICE]   (1) : haproxy version is 3.2.4-98813a1
[WARNING]  (1) : Failed to load worker!

By chance are you using dockwatch that's what was causing mine, for some reason it was in a loop trying to update it. Restarting dockwatch and I woke up today to no issues

[TheGITofTeo997]

Hello, sadly i am encountering the same issue on my NAS, since the version updated. The container does a loop of this:

[NOTICE]   (12) : haproxy version is 3.2.4-98813a1
[WARNING]  (12) : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[NOTICE]   (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
[ALERT]    (12) : [haproxy.main()] Cannot raise FD limit to 8034, limit is 1024.
[NOTICE]   (1) : haproxy version is 3.2.4-98813a1
[WARNING]  (1) : Failed to load worker!

By chance are you using dockwatch that's what was causing mine, for some reason it was in a loop trying to update it. Restarting dockwatch and I woke up today to no issues

I did not know what dockwatch was honestly, but I found out it might be something similar to watchtower, which is what I am running. Do you think it might cause the same issue?

[blassley]

Hello, sadly i am encountering the same issue on my NAS, since the version updated. The container does a loop of this:

[NOTICE]   (12) : haproxy version is 3.2.4-98813a1
[WARNING]  (12) : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[NOTICE]   (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
[ALERT]    (12) : [haproxy.main()] Cannot raise FD limit to 8034, limit is 1024.
[NOTICE]   (1) : haproxy version is 3.2.4-98813a1
[WARNING]  (1) : Failed to load worker!

By chance are you using dockwatch that's what was causing mine, for some reason it was in a loop trying to update it. Restarting dockwatch and I woke up today to no issues

I did not know what dockwatch was honestly, but I found out it might be something similar to watchtower, which is what I am running. Do you think it might cause the same issue?

It's possible as they do the same thing, I suggest going into watch tower and seeing if it shows up to date or not, if not then manually grab update, so it'll refresh and show up to date. This was my issue anyways, it was showing not up to date in dockwatch but was up to do date. A manual check and restart of the container fixed mine so far

[TheGITofTeo997]

Hello, sadly i am encountering the same issue on my NAS, since the version updated. The container does a loop of this:

[NOTICE]   (12) : haproxy version is 3.2.4-98813a1
[WARNING]  (12) : missing timeouts for backend 'docker-events'.
   | While not properly invalid, you will certainly encounter various problems
   | with such a configuration. To fix this, please ensure that all following
   | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
[NOTICE]   (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
[ALERT]    (12) : [haproxy.main()] Cannot raise FD limit to 8034, limit is 1024.
[NOTICE]   (1) : haproxy version is 3.2.4-98813a1
[WARNING]  (1) : Failed to load worker!

By chance are you using dockwatch that's what was causing mine, for some reason it was in a loop trying to update it. Restarting dockwatch and I woke up today to no issues

I did not know what dockwatch was honestly, but I found out it might be something similar to watchtower, which is what I am running. Do you think it might cause the same issue?

It's possible as they do the same thing, I suggest going into watch tower and seeing if it shows up to date or not, if not then manually grab update, so it'll refresh and show up to date. This was my issue anyways, it was showing not up to date in dockwatch but was up to do date. A manual check and restart of the container fixed mine so far

I tried but it's sadly still not working, thanks anyway

[TheGITofTeo997]

Hello, I downgraded to version 0.3.0 using the old docker image and all immediately started to work. For now I will just use the old version, probably not advised but that's the only way if I want to use the proxy

[Programmer-Admin]

@TheGITofTeo997 - It seems like haproxy v3 has introduced a new file, which was earlier absent in the prior versions.

File : https://github.com/haproxy/haproxy/blob/master/src/limits.c
Line Number : Line Number 462-466

Once I get some time, I will check on this. Thanks for reporting!

[josep-tecnativa]

@TheGITofTeo997 Can you share how you are starting the docker-socket-proxy container?
From the logs it looks like the issue is related to the file descriptor (FD) limit.
If you’re using docker run, you could try adding the --ulimit flag, for example:

docker run --ulimit nofile=10000:10000 ...

This way the container will have enough FDs available for HAProxy v3.

[TheGITofTeo997]

@TheGITofTeo997 Can you share how you are starting the docker-socket-proxy container? From the logs it looks like the issue is related to the file descriptor (FD) limit. If you’re using docker run, you could try adding the --ulimit flag, for example:

docker run --ulimit nofile=10000:10000 ...

This way the container will have enough FDs available for HAProxy v3.

Thank you. Adding

    ulimits:
      nofile:
        soft: 10000
        hard: 10000

to compose file fixed it, and now the proxy is running.

[pedrobaeza]

@josep-tecnativa @Programmer-Admin maybe that should land here directly?