Core: Connection pool is full, discarding connection

[hnnweb]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.57.2

Python release (python3 --version):
$ python3 -V
Python 3.5.3

Component/platform:
Log

Description of problem:
When starting hass log fills with:

2017-11-08 13:04:22 INFO (Thread-6) [homeassistant.components.zwave] Z-Wave network autoheal is enabled
2017-11-08 13:04:23 INFO (MainThread) [homeassistant.components.light] Setting up light.hue
2017-11-08 13:04:25 WARNING (Thread-15) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:25 WARNING (Thread-8) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:25 WARNING (Thread-2) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:25 WARNING (Thread-16) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:25 WARNING (Thread-21) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:25 INFO (MainThread) [homeassistant.components.light] Setting up light.tradfri
2017-11-08 13:04:25 WARNING (Thread-2) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:25 WARNING (Thread-18) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:25 WARNING (Thread-13) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:25 WARNING (Thread-3) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:25 WARNING (Thread-12) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2017-11-08 13:04:26 WARNING (Thread-10) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.155.1xx
2

Expected:
Not to see the warnings

[EraYaN]

This also seems to break influxdb logging, there are tons of gaps in my history data.

[tubalainen]

Same here ... :/

2017-11-13 13:49:30 WARNING (SyncWorker_14) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:30 WARNING (SyncWorker_7) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_4) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_3) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_17) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_6) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_15) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_11) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_17) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_6) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_8) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:32 WARNING (SyncWorker_10) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:34 WARNING (SyncWorker_5) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:34 WARNING (SyncWorker_1) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:34 WARNING (SyncWorker_7) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:34 WARNING (SyncWorker_10) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:34 WARNING (SyncWorker_16) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:34 WARNING (SyncWorker_9) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:34 WARNING (SyncWorker_0) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1
2017-11-13 13:49:34 WARNING (SyncWorker_4) [urllib3.connectionpool] Connection pool is full, discarding connection: 127.0.0.1

[Frankster-NL]

Got the exact same, even after a full, clean install of Raspbian Stretch and Homeassistant.

[Atrejoe]

Same here, HASS 0.58.0 running as a Docker image connecting to an influxdb instance on another device (Raspberry Pi)

2017-11-20 23:26:10 WARNING (SyncWorker_4) [urllib3.connectionpool] Connection pool is full, discarding connection: 192.168.1.108

[JojjeErvalla]

+1

[nodomain]

+1 also with Arlo. Lots of entries - sometimes Arlo does not update or activate in automations.

Dec 06 06:51:18 tower hass[19295]: 2017-12-06 06:51:18 WARNING (Thread-19) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:51:18 tower hass[19295]: 2017-12-06 06:51:18 WARNING (Thread-2) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:51:18 tower hass[19295]: 2017-12-06 06:51:18 WARNING (Thread-8) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:43 tower hass[19295]: 2017-12-06 06:52:43 WARNING (Thread-20) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:43 tower hass[19295]: 2017-12-06 06:52:43 WARNING (Thread-22) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:43 tower hass[19295]: 2017-12-06 06:52:43 WARNING (Thread-14) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:43 tower hass[19295]: 2017-12-06 06:52:43 WARNING (Thread-21) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:43 tower hass[19295]: 2017-12-06 06:52:43 WARNING (Thread-21) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:46 tower hass[19295]: 2017-12-06 06:52:46 WARNING (Thread-15) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:46 tower hass[19295]: 2017-12-06 06:52:46 WARNING (Thread-2) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:46 tower hass[19295]: 2017-12-06 06:52:46 WARNING (Thread-17) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:46 tower hass[19295]: 2017-12-06 06:52:46 WARNING (Thread-19) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:47 tower hass[19295]: 2017-12-06 06:52:47 WARNING (Thread-6) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:52:47 tower hass[19295]: 2017-12-06 06:52:47 WARNING (Thread-1154) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:54:13 tower hass[19295]: 2017-12-06 06:54:13 WARNING (Thread-15) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:54:13 tower hass[19295]: 2017-12-06 06:54:13 WARNING (Thread-5) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:54:13 tower hass[19295]: 2017-12-06 06:54:13 WARNING (Thread-19) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:54:13 tower hass[19295]: 2017-12-06 06:54:13 WARNING (Thread-4) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:54:13 tower hass[19295]: 2017-12-06 06:54:13 WARNING (Thread-22) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:55:44 tower hass[19295]: 2017-12-06 06:55:44 WARNING (Thread-21) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:55:44 tower hass[19295]: 2017-12-06 06:55:44 WARNING (Thread-11) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:55:45 tower hass[19295]: 2017-12-06 06:55:45 WARNING (Thread-5) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:55:45 tower hass[19295]: 2017-12-06 06:55:45 WARNING (Thread-21) [urllib3.connectionpool] Connection pool is full, discarding connection: arlo.netgear.com
Dec 06 06:55:45 tower hass[19295]: 2017-12-06 06:55:45 WARNING

[jamieshaw]

I'm seeing this issue with Home Assistant's influxdb connection also. Disabling removes messages from logging, fine until update.

[jo-me]

@jamieshaw Same here after update from 0.58.1 to 0.59.2

Why are there so many parallel requests instead of queues, bulk updates or whatnot?

[zajnic]

Same issue, keep getting the connection pool is full on 0.59.2

2017-12-12 10:43:27 WARNING (SyncWorker_15) [urllib3.connectionpool] Connection pool is full, discarding connection: 
2017-12-12 10:43:53 WARNING (SyncWorker_3) [urllib3.connectionpool] Connection pool is full, discarding connection: 
2017-12-12 10:43:53 WARNING (SyncWorker_9) [urllib3.connectionpool] Connection pool is full, discarding connection: 
2017-12-12 10:44:13 WARNING (SyncWorker_10) [urllib3.connectionpool] Connection pool is full, discarding connection: 
2017-12-12 10:44:13 WARNING (SyncWorker_0) [urllib3.connectionpool] Connection pool is full, discarding connection: 
2017-12-12 10:44:13 WARNING (SyncWorker_17) [urllib3.connectionpool] Connection pool is full, discarding connection: 
2017-12-12 10:44:35 WARNING (SyncWorker_5) [urllib3.connectionpool] Connection pool is full, discarding connection: 
2017-12-12 10:44:57 WARNING (SyncWorker_0) [urllib3.connectionpool] Connection pool is full, discarding connection: 
2017-12-12 10:45:18 WARNING (SyncWorker_2) [urllib3.connectionpool] Connection pool is full, discarding connection:

[rossdargan]

Same issues here. Docker 0.59.2

[binbin2000]

Same issues here as well. Docker 0.59.2.
I'm not sure if it's related, but when these errors started showing up I also started having troubles with Z-wave commands through an Aeon Z-stick. Receiving Z-wave updates (state changes etc.) is still working, but when I try to send a Z-wave command (turning on a switch for example) it doesn't work. Even when I turn on a switch physically, Hass receives the updated state, but it still cannot be controlled from within Hass.

[Frankster-NL]

After I did "pip3 reinstall --force-dependencies --ignore-cache-dir homeassistant" the same issue still arises, but the errors are no longer fatal; the connection will be reinstated after an error, so in the end I keep on getting data into influxdb and into Emoncms.

[kahlin]

Same issues for me, running home assistant 0.60 on hassbian, influxdb 1.0.2.

I seem to have mitigated the problem by adding max_retries: 10 and retry_queue_limit: 100 to the influxdb config. I'm still seeing the problem occasionally in the logs but much less often and data seems to be written to influxdb. (Caveat: I haven't tested/verified this "fix" extensively)

[simpss]

influxdb-python now has the pool size as a configurable option.
I prepared a pull request a while ago to include this option in home-assistant here https://github.com/simpss/home-assistant/pull/1

Sadly I don't have the time to bring it up to date atm, so if anyone wants to rebase the fork, update the dependency version and merge feel free to go ahead.

I'll be able to pick it up again mid-february if the issue remains.

[Naesstrom]

Same problem for me! :(

[kennedyshead]

Ill have a look at it