Hi 

I have installed several docker containers. (16 in summary)

Now I realized that my syslog is flodded with error messages referencing two of my docker containers ("linuxserver/nextcloud" and "zabbix/zabbix-agent2"). Here a short example:

Sep 12 22:55:57 MyServer nginx: 2020/09/12 22:55:57 [error] 11912#11912: *824237 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/token HTTP/2.0", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/token", host: "myserver.local", referrer: "https://myserver.local/dockerterminal/zabbix-agent2/"
Sep 12 22:56:00 MyServer nginx: 2020/09/12 22:56:00 [error] 11912#11912: *829201 connect() to unix:/var/tmp/nextcloud.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/nextcloud/ws HTTP/1.1", upstream: "http://unix:/var/tmp/nextcloud.sock:/ws", host: "myserver.local"
Sep 12 22:56:02 MyServer nginx: 2020/09/12 22:56:02 [error] 11912#11912: *829210 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/ws HTTP/1.1", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/ws", host: "myserver.local"
Sep 12 22:56:10 MyServer nginx: 2020/09/12 22:56:10 [error] 11912#11912: *824237 connect() to unix:/var/tmp/nextcloud.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/nextcloud/token HTTP/2.0", upstream: "http://unix:/var/tmp/nextcloud.sock:/token", host: "myserver.local", referrer: "https://myserver.local/dockerterminal/nextcloud/"
Sep 12 22:56:12 MyServer nginx: 2020/09/12 22:56:12 [error] 11912#11912: *824237 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/token HTTP/2.0", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/token", host: "myserver.local", referrer: "https://myserver.local/dockerterminal/zabbix-agent2/"
Sep 12 22:56:13 MyServer nginx: 2020/09/12 22:56:13 [error] 11912#11912: *829249 connect() to unix:/var/tmp/nextcloud.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/nextcloud/ws HTTP/1.1", upstream: "http://unix:/var/tmp/nextcloud.sock:/ws", host: "myserver.local"
Sep 12 22:56:14 MyServer nginx: 2020/09/12 22:56:14 [error] 11912#11912: *829260 connect() to unix:/var/tmp/zabbix-agent2.sock failed (111: Connection refused) while connecting to upstream, client: 10.0.0.164, server: , request: "GET /dockerterminal/zabbix-agent2/ws HTTP/1.1", upstream: "http://unix:/var/tmp/zabbix-agent2.sock:/ws", host: "myserver.local"

The mentioned client IP is the IP of my local client.

Where do these messages come from and how could I solve this problem?

 

Thanks!

 

Edited September 12, 20205 yr by UnKwicks

You've left a terminal window open to the zabbix container on your browser, and have stopped / restarted the containers in the interim

Thanks for that info. No idea where the terminal window was but I rebooted and the messages are gone.

Thanks!

On 9/12/2020 at 10:20 PM, Squid said:

You've left a terminal window open to the zabbix container on your browser, and have stopped / restarted the containers in the interim

 

I've been searching for this for ages, I've found no end of people complaining about this error and getting no response from the community.

 

Perhaps this info could be relayed in the Unraid Log. "Have you left a console window open?"

On 2/2/2021 at 12:24 PM, OFark said:

 

I've been searching for this for ages, I've found no end of people complaining about this error and getting no response from the community.

 

Perhaps this info could be relayed in the Unraid Log. "Have you left a console window open?"

 

Agree! That is a particularly complicated sounding error for such a little thing. and it is easy to lose one of those little console windows behind everything else.  Maybe an option to open console and log windows as a new tab instead?

to add to this; if this is really the cause...maybe unraid needs to have a way to disconnect from "any remote console", as i don't have any open and it still storms and brings my network access to the server to a standstill about 4 times a day...even after a reboot.  so if its seeing a ghost open, give me a way to disconnect from it!!