Core: Fatal error on transport TCPTransport and websocket error

[zepixir]

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.63.3 (On Hass.io)

Python release (python3 --version):
3.6.3

Component/platform:
homeassistant.core and websocket api

Description of problem:
Getting the following messages:

2018-02-23 12:05:32 ERROR (MainThread) [homeassistant.components.websocket_api] WS 1848485712: Client exceeded max pending messages [2]: 512
2018-02-23 12:07:21 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out

Expected:
No error messages

Additional info:

Seems to not be the only one:

https://community.home-assistant.io/t/help-client-exceeded-max-pending-messages/32276

https://community.home-assistant.io/t/fatal-errors-on-tcp-transports/35921

[broesie]

Got constantly also errors of TCP transport...

Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out

[dooz127]

Seeing the same thing:

HASS v 0.63.3 (running on docker)
Python 3.6.4

2018-02-24 09:13:48 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of platform ring is taking over 10 seconds.
2018-02-24 09:13:48 WARNING (MainThread) [homeassistant.components.sensor] Setup of platform ring is taking over 10 seconds.
2018-02-24 09:13:48 WARNING (MainThread) [homeassistant.components.camera] Setup of platform ring is taking over 10 seconds.
2018-02-24 09:27:41 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ring binary_sensor took longer than the scheduled update interval 0:00:05
2018-02-24 10:06:47 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 10:07:10 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 10:07:19 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 10:11:47 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Connection timed out
2018-02-24 10:18:53 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 10:18:55 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 10:18:56 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 10:18:57 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 16:39:57 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
OSError: [Errno 113] No route to host
2018-02-24 18:24:31 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ring binary_sensor took longer than the scheduled update interval 0:00:05
2018-02-24 20:28:03 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 20:28:03 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 22:41:37 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ring binary_sensor took longer than the scheduled update interval 0:00:05
2018-02-24 23:59:52 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 23:59:54 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 23:59:54 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 23:59:56 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 23:59:56 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-24 23:59:57 WARNING (MainThread) [haffmpeg.core] FFmpeg isn't running!
2018-02-25 02:39:37 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ring binary_sensor took longer than the scheduled update interval 0:00:05

[RikVerstijnen]

Same here; v 0.64.1 running on Hassio

2018-03-01 01:51:59 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out
2018-03-01 04:48:35 ERROR (Thread-11) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-03-01 09:24:20 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out
2018-03-01 09:46:48 ERROR (Thread-72) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-03-01 09:52:03 ERROR (Thread-72) [pychromecast.socket_client] Failed to connect. No retries.
2018-03-01 11:45:35 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out
2018-03-01 12:04:32 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out

[xnappo]

Same here on 64.1 running Hassio on Pi3. Hardwired.

2018-03-03 17:56:42 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback) TimeoutError: [Errno 110] Operation timedout``

[hwikene]

Same here on 65.2. running Hassio on docker. Hardwierd.

2018-03-12 12:47:25 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out
2018-03-12 12:48:49 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out

[edif30]

I noticed that after this error showed up in the log, a couple of my grafana graphs stopped showing data points. Restart of HA and they came back. But the timestamp is right on par with when this error showed up.

 [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)

[metbril]

Same here. Started noticing this with 0.65.3. Running Hass.io on a RPi 2B over wired 1GB LAN.

The error is repeating every 10 minutes, sometimes twice in one minute.

[metbril]

By coincidence I noticed that the error vanished when I disabled my (fairly default) telegram setup. I use the polling (since webhook stopped working some updates ago).

################################################
## Telegram Bot
################################################

telegram_bot:
  - platform: polling
    api_key: !secret telegram_bot_api_key
    allowed_chat_ids:
      - !secret telegram_bot_chat_id_robert

################################################
## Notify
################################################

notify:
  - name: telegram
    platform: telegram
    chat_id: !secret telegram_bot_chat_id_robert

Can anyone confirm that they use telegram when the error occurs and it disappears when you remove telegram from your config?

[metbril]

Possibly related to #12774

[urbydoo]

@metbril I can confirm disabling my telegram bot appears to have resolved the error for me as well

[zepixir]

I don't use telegram, but still have the issue 😕

[metbril]

The hass.io system log shows this error:

18-03-29 02:59:17 ERROR (MainThread) [asyncio] Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
protocol: <asyncio.sslproto.SSLProtocol object at 0x71d1b110>
transport: <TCPTransport closed=False reading=False 0x750bedf0>
TimeoutError: [Errno 110] Operation timed out

[metbril]

@balloob are the dev team aware of this error? Looks like something deep in the asyncio core?

[balloob]

Looks like some services that we connect to over SSL (like telegram) are canceling our connections in an incorrect way. It's nothing to worry about.

[andylebedev]

I get this error after I setup ssl certs for https

Log Details (ERROR)
Mon Apr 09 2018 09:20:01 GMT+0300 (EEST)

Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 794, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host

Log Details (WARNING)
Mon Apr 09 2018 09:04:04 GMT+0300 (EEST)

<asyncio.sslproto.SSLProtocol object at 0x692acc30> stalled during handshake

[rich710se]

My HA-installation has crashed two times the last days, with the same error.

2018-04-15 18:46:24 WARNING (MainThread) [asyncio] socket.send() raised exception.
2018-04-15 18:46:24 WARNING (MainThread) [asyncio] socket.send() raised exception.
2018-04-15 18:56:19 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140388792521672: Client exceeded max pending messages [2]: 512
2018-04-15 18:56:19 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140387450450216: Client exceeded max pending messages [2]: 512
2018-04-15 18:56:19 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140388792521672: Client exceeded max pending messages [2]: 512
2018-04-15 18:56:19 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140387450450216: Client exceeded max pending messages [2]: 512
2018-04-15 18:56:19 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140388792521672: Client exceeded max pending messages [2]: 512
2018-04-15 18:56:19 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140387450450216: Client exceeded max pending messages [2]: 512

[davidw3591]

Also having a lot of issues. Have to reboot every day.

Logfile looks like this:

2018-04-16 14:17:31 ERROR (MainThread) [homeassistant.components.websocket_api] WS 1618902480: Client exceeded max pending messages [2]: 512
2018-04-16 14:18:55 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-04-16 14:23:30 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-04-16 14:24:00 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-04-16 14:24:03 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
2018-04-16 14:24:41 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
OSError: [Errno 113] No route to host
2018-04-16 14:28:53 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

The timer out of sync repeats every 10s-60s.

[zenturacp]

Mine got the same error - but it came after i added Unifi support - guess it sometimes does a timeout when polling. It though still works.

[davidw3591]

Wat is this line about, does it have something to do with the inbuilt MQTT broker?
2018-04-16 14:17:31 ERROR (MainThread) [homeassistant.components.websocket_api] WS 1618902480: Client exceeded max pending messages [2]: 512

Because if I debug the mqtt component I get 4 lines in the logfile for every single message. The broker is broadcasting it twice to homeassistant.

Related topic: https://community.home-assistant.io/t/mqtt-multiple-loglines/50693

[gb53smith]

I get the same two errors and now at hassio 0.70.0
I have not noticed any loss in functionality.
My rant:
I guess that I am a perfectionist and driven to fix ERRORS. The goal should be no repeating errors after startup. If they are not critical can they be changed to warnings and filtered out?
These errors create "error message noise". It is hard for users to know which errors can be fixed by changes to yaml code.
There are a lot of wasted user time hunting around for solutions to these error messages which are coming from HA core functionality. (SSL, MQTT)
I cannot recommend HA to friends in its current state.

[balloob]

@gb53smith We won't reduce the warnings because they need to be fixed. If you are willing to help, please let us know. Don't go off ranting in an issue as that helps exactly 0. If you don't have anything meaningful to add, don't post, ok? You can add an emoji to the first post to show that you have the same issue.

[metbril]

In my current config with hassio 0.71.0 I only get the errors with the DarkSky component enabled.

[davedan]

So, I'm experiencing the same issue and I have the feeling my Node-Red flows are impacting on this. I started having several 'server-state-changed' nodes and I started to see how the performance was droping. Even being unable to access the site for a while. After modifying some of the flows and reduce the # of this nodes looks like reduces the impact. I'm in 0.73.2 ... hope this helps and happy to test if I can help.

[jwelter1971]

I've also started to get this error after setting up HA to handle the SSL termination. Prior I was using HAProxy to do the SSL termination and proxying HA in http mode and no errors at all.

By switching HTTPS off the errors go away again so it's confirmed it's somehow connected.

I get the errors always in pairs and roughly every 8 hours or so.

[SelcouthGuy]

Got the same error like in issue description
WS 1753762096: Client exceeded max pending messages [2]: 512

What is really interesting I had this error about 8:05 p.m. According to Logbook there was no actions between 7 p.m. and 9:30 p.m. so I suppose that this is not configuration/setup issue.

[jwelter1971]

Got the same error like in issue description
WS 1753762096: Client exceeded max pending messages [2]: 512

What is really interesting I had this error about 8:05 p.m. According to Logbook there was no actions between 7 p.m. and 9:30 p.m. so I suppose that this is not configuration/setup issue.

This is consistent with what I saw; no activity that was obvious but suspect it was some sort of background fetch.

I have now moved back to HAProxy terminating the SSL and passing to HA over HTTP and the message/warning/error has not shown up in 6 days. So in my case it appears to be triggered by HA handling the SSL termination. Same SSL certs; from LetsEncrypt; are being used. HAProxy running on the same host as HA; listening on 443 and with HA on 8123.

[stainlessray]

This error appears to coincide with node red failures after the error. HA keeps chugging, or recovers, I can't tell which. But Node Red is instantly broken ending flows.

[comatose-tortoise]

I have this error too. 0.82.1 running in docker on a dedicated ubuntu machine.

[RezzZ]

I see this error once in a while on 0.83.2 as well. RPi3B+ raspbian / docker / mariadb (currently with influxdb disabled due to high loads).

[JanHG]

I have this error on 0.83.2. Hassio, RPi3.

[Fonta]

Error also in 0.85.0b0.
Running in docker on dedicated ubuntu machine.

[sagilo]

I get these errors since I've enabled 'darksky weather component' (it was enabled as sensor before, now as both sensor and weather)
Running 0.84.6 on Ubuntu/Docker

[andreas-bulling]

same error here - I think since upgrading to 0.87

[e-budianto]

same error here, since upgrading to 0.87
running on hassio, raspi 3B+ with MariaDB

[michael0731]

arch | x86_64
-- | --
dev | false
docker | true
hassio | true
os_name | Linux
python_version | 3.7.2
timezone | Asia/Taipei
version | 0.88.1
virtualenv | false

Unhandled error in exception handler
context: {'message': 'Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)', 'exception': TimeoutError(110, 'Operation timed out'), 'transport': <TCPTransport closed=False reading=False 0x557a0c453fd8>, 'protocol': <uvloop.loop.SSLProtocol object at 0x7ff4965799b0>}
Traceback (most recent call last):
  File "uvloop/loop.pyx", line 2234, in uvloop.loop.Loop.call_exception_handler
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 110, in async_loop_exception_handler
    "Error doing job: %s", context['message'], **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1412, in error
    self._log(ERROR, msg, args, **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1519, in _log
    self.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1529, in handle
    self.callHandlers(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1591, in callHandlers
    hdlr.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 905, in handle
    self.emit(record)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 168, in emit
    _figure_out_source(record, stack, self.hass))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 99, in __init__
    self.root_cause = str(traceback.extract_tb(tb)[-1])
IndexError: list index out of range

[kevintuhumury]

I started noticing this issue ever since I upgraded to 0.88.1 using the Docker image.

2019-02-27 21:51:05 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out
2019-02-27 21:51:05 ERROR (MainThread) [asyncio] Unhandled error in exception handler
context: {'message': 'Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)', 'exception': TimeoutError(110, 'Operation timed out'), 'transport': <TCPTransport closed=False reading=False 0x6e9de030>, 'protocol': <uvloop.loop.SSLProtocol object at 0x6e7d7fb0>}
Traceback (most recent call last):
  File "uvloop/loop.pyx", line 2234, in uvloop.loop.Loop.call_exception_handler
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 110, in async_loop_exception_handler
    "Error doing job: %s", context['message'], **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1412, in error
    self._log(ERROR, msg, args, **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1519, in _log
    self.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1529, in handle
    self.callHandlers(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1591, in callHandlers
    hdlr.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 905, in handle
    self.emit(record)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 168, in emit
    _figure_out_source(record, stack, self.hass))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 99, in __init__
    self.root_cause = str(traceback.extract_tb(tb)[-1])
IndexError: list index out of range

Exactly the same error that @michael0731 is getting. It's occurring about every 10 minutes and it's filling up the logs. Quite annoying. Anyone have an idea what's causing this?

[e-budianto]

got this error message also running Pi3B+ with hassio docker.

Thu Feb 28 2019 11:12:07 GMT+0700 (Indochina Time)
Unhandled error in exception handler
context: {'message': 'Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)', 'exception': TimeoutError(110, 'Operation timed out'), 'transport': <TCPTransport closed=False reading=False 0x6fa7e600>, 'protocol': <uvloop.loop.SSLProtocol object at 0x6f544970>}
Traceback (most recent call last):
  File "uvloop/loop.pyx", line 2234, in uvloop.loop.Loop.call_exception_handler
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 110, in async_loop_exception_handler
    "Error doing job: %s", context['message'], **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1412, in error
    self._log(ERROR, msg, args, **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1519, in _log
    self.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1529, in handle
    self.callHandlers(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1591, in callHandlers
    hdlr.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 905, in handle
    self.emit(record)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 168, in emit
    _figure_out_source(record, stack, self.hass))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 99, in __init__
    self.root_cause = str(traceback.extract_tb(tb)[-1])
IndexError: list index out of range

[kevintuhumury]

As mentioned 2 days ago I got this error when I upgraded to 0.88.1. This was from 0.87.1 (so I never used 0.88.0). I upgraded to 0.88.2 and still had this issue.

So, today I decided to downgrade to 0.87.1. No issue at all, not even after an hour. From there I upgraded to 0.88.0 (a version I hadn't used previously) and after about 20 minutes I received the above error again. From that moment on I started to get that error every 10 minutes on the minute.

So, it's definitely something introduced in 0.88.0 what is causing this.

[sephrioth]

got this error message also running Pi3B+ with hassio docker.

Thu Feb 28 2019 11:12:07 GMT+0700 (Indochina Time)
Unhandled error in exception handler
context: {'message': 'Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)', 'exception': TimeoutError(110, 'Operation timed out'), 'transport': <TCPTransport closed=False reading=False 0x6fa7e600>, 'protocol': <uvloop.loop.SSLProtocol object at 0x6f544970>}
Traceback (most recent call last):
  File "uvloop/loop.pyx", line 2234, in uvloop.loop.Loop.call_exception_handler
  File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 110, in async_loop_exception_handler
    "Error doing job: %s", context['message'], **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1412, in error
    self._log(ERROR, msg, args, **kwargs)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1519, in _log
    self.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1529, in handle
    self.callHandlers(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 1591, in callHandlers
    hdlr.handle(record)
  File "/usr/local/lib/python3.7/logging/__init__.py", line 905, in handle
    self.emit(record)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 168, in emit
    _figure_out_source(record, stack, self.hass))
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 99, in __init__
    self.root_cause = str(traceback.extract_tb(tb)[-1])
IndexError: list index out of range

same error here.

[rvanmarkus]

Since the last upgrade (to 0.88.1), I also get the same errors (raspberry pi 3b hassos):

``Unhandled error in exception handler context: {'message': 'Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)', 'exception': TimeoutError(110, 'Operation timed out'), 'transport': <TCPTransport closed=False reading=False 0x55aae08518>, 'protocol': <uvloop.loop.SSLProtocol object at 0x7fa8ea09e8>} Traceback (most recent call last): File "uvloop/loop.pyx", line 2234, in uvloop.loop.Loop.call_exception_handler File "/usr/local/lib/python3.7/site-packages/homeassistant/core.py", line 110, in async_loop_exception_handler "Error doing job: %s", context['message'], **kwargs) File "/usr/local/lib/python3.7/logging/__init__.py", line 1412, in error self._log(ERROR, msg, args, **kwargs) File "/usr/local/lib/python3.7/logging/__init__.py", line 1519, in _log self.handle(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 1529, in handle self.callHandlers(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 1591, in callHandlers hdlr.handle(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 905, in handle self.emit(record) File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 168, in emit _figure_out_source(record, stack, self.hass)) File "/usr/local/lib/python3.7/site-packages/homeassistant/components/system_log/__init__.py", line 99, in __init__ self.root_cause = str(traceback.extract_tb(tb)[-1]) IndexError: list index out of range

[kevintuhumury]

Since I upgraded to 0.89.0 a couple days ago the above error went away. I however got a new error instead which also shows up every 10 minutes.

[homeassistant.core] Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out

This error is logged 3 times when it is triggered.

[gdschut]

Got this on 0.90.1

Mar 26 18:35:28 pi hass[2123]: 2019-03-26 18:35:28 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1750759568] Client exceeded max pending messages [2]: 512
Mar 26 18:35:28 pi hass[2123]: 2019-03-26 18:35:28 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1750759568] Client exceeded max pending messages [2]: 512

How to find out what this connection is which causes this error? Does it have anything to do with node-red?

[Pirol62]

Already received this error. Verison 0.90.2
Error doing job: Fatal error on transport TCPTransport (error status in uv_stream_t.read callback)
TimeoutError: [Errno 110] Operation timed out

[niek1992]

was having the same issues as above, read the thread and @metbril mentioned about the Darksky sensor. Validated my settings and removed redundant settings. haven't had a error in the log since.

[comatose-tortoise]

I don’t have Darksky and I’ve been getting this error for a long time, over many versions of HA.

[hristo-atanasov]

I see lots of people mentioning "Dark sky". I don't use it, but I had "yr" met. I had the same problem. It said I have some ssl problem, something like uvloop and these 512 max pending requests. I commented out the line with the sensor "yr" and for now it seems to be OK. If you have such sensor, try comment/remove it and see if it goes well and with no errors. :)

PS: "YR Simbol" comes pre-configured in all newly installed hassio instances in "configuration.yaml" as sensor and this is why you might even know you have it. Especially if you use LovelaceUI. 'YR' has badge that is visible in https://hassio_address/states .

[Pirol62]

Error in 0.91.4

Tue May 07 2019 16:48:21 GMT+0200 (Mitteleuropäische Sommerzeit)
Error doing job: Fatal error on transport
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 574, in uvloop.loop.SSLProtocol._do_shutdown
  File "/usr/local/lib/python3.7/ssl.py", line 767, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2605)

No Darksky

Error still relevant. I have it at least two times a day

[hristo-atanasov]

It was gone for one week, from my previous comment, and I still have it.

[Pirol62]

Slightly different but still valid in 0.95

In 0.94.x I cannot remember this issue.....

Error doing job: Fatal error on transport
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 574, in uvloop.loop.SSLProtocol._do_shutdown
  File "/usr/local/lib/python3.7/ssl.py", line 767, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2609)

[dolenec]

Same error in 0.96.3

[xeospeed]

Same error in 0.96.4

[sungla55guy]

same error in 0.96.5

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[MORZ1990]

Same error in 0.107.7