Seeing a warning when starting the container

[ovizii]

docker-socket-proxy  | [WARNING] 017/082756 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory     
docker-socket-proxy  | Proxy dockerbackend started.                                                                                                  
docker-socket-proxy  | Proxy dockerfrontend started.                                                                                                 
docker-socket-proxy  | [NOTICE] 017/082756 (1) : New worker #1 (8) forked

everything works I just wanted toreport this.

[NicolasGoeddel]

I see a similar warning but it also seems to work just fine.

socket-proxy-telegraf  | [WARNING] 073/185645 (1) : Can't open server state file '/var/lib/haproxy/server-state': No such file or directory
socket-proxy-telegraf  | [NOTICE] 073/185645 (1) : New worker #1 (7) forked

[kevinberthiaume]

I also see the same warning line : [WARNING] 137/002946 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory Proxy dockerbackend started. Proxy dockerfrontend started. [NOTICE] 137/002946 (1) : New worker #1 (8) forked

[poudenes]

Same here on a Synology DS220+

[sammcj]

Still an issue on the latest edge release as well:

[WARNING] 267/211702 (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] 267/211702 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
[NOTICE] 267/211702 (1) : New worker #1 (8) forked

[ovizii]

Still an issue on the latest edge release as well:

[WARNING] 267/211702 (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] 267/211702 (1) : Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory
[NOTICE] 267/211702 (1) : New worker #1 (8) forked

I can confirm.

[sammcj]

Ah, came to log this as well, is this something we're configuring wrong or a bug?

Stopping backend dockerbackend in 0 ms.
[WARNING] 280/032546 (8) : Proxy dockerbackend stopped (cumulated conns: FE: 0, BE: 26).
Stopping backend docker-events in 0 ms.
[WARNING] 280/032546 (8) : Proxy docker-events stopped (cumulated conns: FE: 0, BE: 1).
Stopping frontend dockerfrontend in 0 ms.
[WARNING] 280/032546 (8) : Proxy dockerfrontend stopped (cumulated conns: FE: 1, BE: 0).
Proxy dockerbackend stopped (cumulated conns: FE: 0, BE: 26).
Proxy docker-events stopped (cumulated conns: FE: 0, BE: 1).
Proxy dockerfrontend stopped (cumulated conns: FE: 1, BE: 0).
[WARNING] 280/032546 (8) : Proxy GLOBAL stopped (cumulated conns: FE: 0, BE: 0).
[WARNING] 280/032557 (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'.
[NOTICE] 280/032557 (1) : New worker #1 (8) forked

[mrvalterhugo]

Same issue here

[vvstubbs]

I got around that issue by under volumes: /var/lib/haproxy/server-state:/var/lib/haproxy/server-state

and just prepare a 0 byte file sudo mkdir -p /var/lib/haproxy && sudo touch /var/lib/haproxy/server-state

[vvstubbs]

What did anyone do about: |To fix this, please ensure that all following | timeouts are set to a non-zero value: 'client', 'connect', 'server'. entries in environment: I presume