Core: Fatal read error on socket transport

[olskar]

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):
3.5.3

Component/platform:
Unknown

Description of problem:
Every day I see this in the log, not sure what could be wrong?
People in the forum seem to have this as well, but i figured better to report here
https://community.home-assistant.io/t/recurring-errors-error-doing-job-fatal-read-error-on-socket-transport/28452

Expected:

Problem-relevant configuration.yaml entries and steps to reproduce:

1. 
   
   
   2.
   
3.

Traceback (if applicable):

2017-11-08 10:14:30 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

Additional info:

[mny24]

Same issues here.

[tinloaf]

You're probably using some platform that wants to connect to some thing on your LAN or the internet and that connection breaks occasionally. Without further information I don't think that it's possible to say where the error lies. Have you added a platform / component recently and then started seeing this error?

[imammedo]

I suspect problem is in http component and I managed to reproduce it reliably with bare config without anything except of http and sun component, but it should be also reproducible with default config
steps to reproduce:

1. start HA
2. connect from a laptop to HA and open history section
3. once graph is displayed, put the laptop into sleep mode
4. wait an hour
5. go to HA host and find TimeoutError in logs

From my observations timeout happens in 20 min after client goes to sleep,
and after error HA still believes that client is there and timeouts again after some time.

it seems HA isn't handling properly timeout conditon,
looking at homeassistant/components/websocket_api.py

@asyncio.coroutine
def handle(self):
    """Handle the websocket connection."""
    request = self.request
    wsock = self.wsock = web.WebSocketResponse()

it doesn't specify any timeout nor in any receive() calls, so eventually timeout inside of asyncio fires up.

here are links that might be of help:
1:
websocket lib
https://github.com/aaugustin/websockets/issues/110
https://github.com/aaugustin/websockets/commit/13f2e408707627260f2eed954bdec735f701daa5
2:
aiohttp lib
https://github.com/aio-libs/aiohttp/issues/2310
https://github.com/aio-libs/aiohttp/issues/1325

Adding receive_timeout like this

   wsock = self.wsock = web.WebSocketResponse(receive_timeout=10)

makes anonymous TimeoutError disappear and replaces it with a bunch of exceptions that are not handled in homeassistant/components/websocket_api.py (like cancellation and/or timeout) but with tracebacks showing where they are coming from.

PS:
I have not a clue how HA or any other used library works and don't know python as well,
so I'm not qualified to fix it. Hopefully maintainers will be able to fix it if it's the place where issue is.

========= my log =========

2017-12-29 22:13:51 INFO (MainThread) [homeassistant.components.http] Serving /api/websocket to x.x.x.x (auth: True)
2017-12-29 22:13:51 INFO (MainThread) [homeassistant.components.http] Serving /api/history/period/2017-12-28T23:00:00.000Z to x.x.x.x (auth: True)
2017-12-29 22:14:00 INFO (MainThread) [homeassistant.components.http] Serving /api/history/period/2017-12-28T23:00:00.000Z to x.x.x.x (auth: True)
2017-12-29 22:34:33 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2017-12-29 22:52:32 INFO (MainThread) [homeassistant.components.http] Serving /api/websocket to  x.x.x.x (auth: True)
2017-12-29 22:52:32 INFO (MainThread) [homeassistant.components.http] Serving /api/history/period/2017-12-28T23:00:00.000Z to  x.x.x.x (auth: True)
2017-12-29 23:09:32 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport

[dvilo]

Slightly different in v 0.60.1 after hibernating with web client open. Web server went down.

01-09 00:37:12 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 662, in _read_ready
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host

Log is set to Error only.

[jrkoiter]

0.65.2 having issue as well:

2018-03-17 13:15:37 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.6/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2018-03-17 13:15:37 INFO (MainThread) [homeassistant.core] Bus:Handling <Event system_log_event[L]: timestamp=1521288937.5074604, level=ERROR, message=Error doing job: Fatal read error on socket transport, exception=Traceback (most recent call last):
  File "/usr/lib/python3.6/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

[moskovskiy82]

Same with me. And since .64 can see it more often. Maybe some detailed logging can be introduced in future releases?

[andylebedev]

HA .66.1 on python 3.7

2018-04-09 23:02:12 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.broadlink_enterance is taking over 10 seconds
2018-04-09 23:02:14 ERROR (SyncWorker_5) [homeassistant.components.switch.command_line] Command failed: python2 /home/pi/python-broadlink/light.enterance.state.py
2018-04-09 23:34:45 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.broadlink_hall_enterance is taking over 10 seconds
2018-04-09 23:34:47 ERROR (SyncWorker_17) [homeassistant.components.switch.command_line] Command failed: python2 /home/pi/python-broadlink/light.hall-enterance.state.py
2018-04-09 23:44:46 ERROR (MainThread) [homeassistant.core] 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
2018-04-10 08:37:43 WARNING (MainThread) [homeassistant.core] Unable to find service sensor/turn_on
2018-04-10 08:37:43 WARNING (MainThread) [homeassistant.core] Unable to find service camera/turn_on
2018-04-10 08:37:43 WARNING (MainThread) [homeassistant.core] Unable to find service binary_sensor/turn_on
2018-04-10 08:40:46 WARNING (MainThread) [homeassistant.core] Unable to find service camera/turn_off
2018-04-10 08:40:46 WARNING (MainThread) [homeassistant.core] Unable to find service sensor/turn_off
2018-04-10 08:40:46 WARNING (MainThread) [homeassistant.core] Unable to find service binary_sensor/turn_off
2018-04-10 08:45:22 ERROR (MainThread) [homeassistant.core] 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)
TimeoutError: [Errno 110] Connection timed out
2018-04-10 08:56:46 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x65e85190> stalled during handshake
2018-04-10 08:56:46 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x65e85f10> stalled during handshake
2018-04-10 08:56:46 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x69212470> stalled during handshake
2018-04-10 08:56:46 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x691b0bd0> stalled during handshake
2018-04-10 08:56:46 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x69202170> stalled during handshake
2018-04-10 08:56:46 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x69202070> stalled during handshake
2018-04-10 08:56:47 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x691c6b70> stalled during handshake
2018-04-10 08:56:47 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x6dd3e810> stalled during handshake
2018-04-10 08:57:18 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x692121d0> stalled during handshake
2018-04-10 08:57:50 WARNING (MainThread) [asyncio] <asyncio.sslproto.SSLProtocol object at 0x65b2b6b0> stalled during handshake
2018-04-10 08:57:52 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 08:57:52 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 08:58:00 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 08:58:00 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 08:58:00 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 08:58:00 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 08:58:00 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 08:58:00 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 08:58:00 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 08:58:00 ERROR (zeroconf-Engine) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-04-10 09:04:13 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.broadlink_enterance is taking over 10 seconds
2018-04-10 09:04:15 ERROR (SyncWorker_10) [homeassistant.components.switch.command_line] Command failed: python2 /home/pi/python-broadlink/light.enterance.state.py
2018-04-10 10:27:51 ERROR (MainThread) [homeassistant.core] 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)
TimeoutError: [Errno 110] Connection timed out
2018-04-10 10:27:51 ERROR (MainThread) [homeassistant.core] 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)
TimeoutError: [Errno 110] Connection timed out
2018-04-10 10:27:51 ERROR (MainThread) [homeassistant.core] 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)
TimeoutError: [Errno 110] Connection timed out
2018-04-10 10:27:51 ERROR (MainThread) [homeassistant.core] 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)
TimeoutError: [Errno 110] Connection timed out
2018-04-10 10:27:51 ERROR (MainThread) [homeassistant.core] 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)
TimeoutError: [Errno 110] Connection timed out

[N3g4tivo]

Home Assistant 0.67.0

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

[hekm77]

HA 0.69.1

Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

[ReneTode]

i did get this kind of problems when i updated to 0.65.3 and still have the problems on 0.69.1

Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 724, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

and

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

also after some time all components start to take to much time
first that happens once in a while and slowly that increases untill HA almost stopps.

i didnt add any components in the time that the error started appearing.

ubuntu 17.10
python 3.6

[cicero200272]

Same here with HA 70.1. Log is flooded with errors like these:

2018-06-05 06:53:27 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

and sometimes

2018-06-05 06:50:44 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host

[hoangtuit]

Same on HA 0.72.1

Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

[moskovskiy82]

0.72 - still there. @balloob Can some debugging be introduced to point to the platform in question?

2018-07-01 19:49:18 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

[ReneTode]

the same errors appear in HADashboard.
this error is related to an open gui that somehow cant be reached.

i dont think it can be avoided, but i think there is a problem in the error handling.

[SelcouthGuy]

Same here.

Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

Only duckdns installed...
Home Assistant: 0.78.3
I hope @balloob or someone will take a look on this problem.

[balloob]

Please don't tag people to take a look.

[ReneTode]

but it would be nice if someone took notice of this issue.
it exist almost a year and it has to do with the connection between the HA and probably the frontend.

[SelcouthGuy]

Is it possible to turn off only information about this one specific issue from logs?
If no one at the moment can fix this problem, maybe it's possible to hide it. This is annoying to see it all the time.

[03397]

I have the exact same error on the latest version of HA.
The component that I am using that might create this is the owl intuition custom component.
https://github.com/custom-components/sensor.owlintuition

Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/asyncio/selector_events.py", line 723, in _read_ready
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

[ReneTode]

@03397 how did you conclude that it is that component?

[03397]

@ReneTode
I said it might I am not sure. The reason is that it is the only component that creates the following warnings

Update of sensor.owl_intuition_hotwater_ambient is taking over 10 seconds
3:15 PM util/async_.py (WARNING)
Update of sensor.owl_intuition_hotwater_temperature is taking over 10 seconds
3:14 PM util/async_.py (WARNING)
Update of sensor.owl_intuition_heating_battery_level is taking over 10 seconds
3:13 PM util/async_.py (WARNING)
Update of sensor.owl_intuition_hotwater_battery_level is taking over 10 seconds
3:12 PM util/async_.py (WARNING)
Update of sensor.owl_intuition_electricity_today is taking over 10 seconds
3:11 PM util/async_.py (WARNING)
Update of sensor.owl_intuition_hotwater_battery_level is taking over 10 seconds
3:10 PM util/async_.py (WARNING)
Update of sensor.owl_intuition_hotwater_radio is taking over 10 seconds
3:09 PM util/async_.py (WARNING)
You are using a custom component for sensor.owlintuition which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
3:08 PM loader.py (WARNING)

This component creates a listener on the home assistant that accepts the UDP traffic that it is send by the owl gateway. After talking with the developer he told me that he has trouble in order to sent the data in asynchronous mode.

[ReneTode]

hmm, im not saying its that component, but in the time i had the custom alexa mediaplayer, which gave the same warnings, i didnt have more errors.
and in the past year i had the errors of and on and had never warnings like that.

[03397]

@ReneTode
Perhaps you are right. I think that the developers should step in and let is know why this might be happening..
I just included my warnings since this might help.

[balloobbot]

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 :+1:

[SelcouthGuy]

This issue hasn't been resolved for months or years?
Do not close please.

[03397]

I have removed the component and I am still receiving the issue after a while

[varjagg]

Same issue with 0.84.6

[gdschut]

same issue on 0.90.1

Mar 26 19:03:07 pi hass[2123]: 2019-03-26 19:03:07 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Mar 26 19:03:07 pi hass[2123]: Traceback (most recent call last):
Mar 26 19:03:07 pi hass[2123]:   File "/usr/lib/python3.5/asyncio/selector_events.py", line 723, in _read_ready
Mar 26 19:03:07 pi hass[2123]:     data = self._sock.recv(self.max_size)
Mar 26 19:03:07 pi hass[2123]: TimeoutError: [Errno 110] Connection timed out
Mar 26 19:03:07 pi hass[2123]: 2019-03-26 19:03:07 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Mar 26 19:03:07 pi hass[2123]: Traceback (most recent call last):
Mar 26 19:03:07 pi hass[2123]:   File "/usr/lib/python3.5/asyncio/selector_events.py", line 723, in _read_ready
Mar 26 19:03:07 pi hass[2123]:     data = self._sock.recv(self.max_size)
Mar 26 19:03:07 pi hass[2123]: TimeoutError: [Errno 110] Connection timed out
Mar 26 19:03:07 pi hass[2123]: 2019-03-26 19:03:07 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Mar 26 19:03:07 pi hass[2123]: Traceback (most recent call last):
Mar 26 19:03:07 pi hass[2123]:   File "/usr/lib/python3.5/asyncio/selector_events.py", line 723, in _read_ready
Mar 26 19:03:07 pi hass[2123]:     data = self._sock.recv(self.max_size)
Mar 26 19:03:07 pi hass[2123]: TimeoutError: [Errno 110] Connection timed out

[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.

[03397]

Problem still there on version 0.95.4

[ReneTode]

i also still got the problem. on all versions untill now.

[snakuzzo]

Same problem con 0.96.5

[SelcouthGuy]

snakuzzo, renetode, 03397.
Could you please try to disable your configurator for some time and let us know if error still appears in logs?

sudo systemctl stop home-assistant-configurator.service (or however you have configured it to running in background)
sudo systemctl disable home-assistant-configurator.service

in HA configuration.yaml comment configurator under panel_iframe

  #panel_iframe:
    #configurator:
      #title: Configurator
      #icon: mdi:wrench
      #url: !secret url_configurator
      #require_admin: true

and restart HA: sudo systemctl restart [email protected]

[snakuzzo]

I have no home-assistant-configurator service configured

pi@snakeberry:/home/homeassistant/.homeassistant $ cat configuration.yaml | grep configurator
pi@snakeberry:/home/homeassistant/.homeassistant $
pi@snakeberry:/home/homeassistant/.homeassistant $
pi@snakeberry:/home/homeassistant/.homeassistant $ ps -ef | grep homeassistant
homeass+   532     1  4 00:25 ?        00:29:06 /srv/homeassistant/bin/python3.7 /srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant
pi        3489 26458  0 10:57 pts/0    00:00:00 grep --color=auto homeassistant

[SelcouthGuy]

Uhym... sorry, I thought it may help. I have disabled configurator in my setup and error disappeared for one day and later I have reinstalled HA and right now I'm using fresh installation with HAproxy with no errors.
Looks like it was just coincidence...

[ReneTode]

no configurator here also.
and no HA service also ;)

[electrofloat]

Still happening in 0.100.2

[electrofloat]

Still happening in 0.101.1

[electrofloat]

Still happening in 0.102

[princehaku]

found a way to fix this.
in windows 10 use admin command prop.
type netsh winsock reset and restart

[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.

[03397]

107.7 version the problem still persists.

[shudack]

109.6 version the problem still persists...

Traceback (if applicable):

2020-05-14 15:06:54 ERROR (MainThread) [homeassistant.core] 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 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2020-05-14 15:08:34 ERROR (MainThread) [homeassistant.core] 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 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2020-05-14 15:11:28 ERROR (MainThread) [homeassistant.core] 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 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2020-05-14 15:11:57 ERROR (MainThread) [homeassistant.core] 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 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2020-05-14 15:13:35 ERROR (MainThread) [homeassistant.core] 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 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2020-05-14 15:15:15 ERROR (MainThread) [homeassistant.core] 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 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out

[bvansambeek]

I did not update for a while (was sitting on something around 0.90) and was scared that the update would break a lot of stuff.
So I started fresh, which I wanted to do to anyways (without using snapshot to restore my install).
I am on 0.105.5 with Supervisor 222 and HassOS 3.11 on a Windows laptop in VirtualBOX.
I furthermore added Home Assistant to my office on a Raspberry Pi 3B+ (i think), which is on version 0.108.6 with Supervisor 222 and HassOS 3.13.
Both do not have this error.

[shudack]

@bvansambeek I created a new venv with Python 3.7.5 and also do not have this error.

[snakuzzo]

still happening on 0.110.4

2020-05-29 16:03:32 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2020-05-29 20:05:37 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host
2020-05-29 20:05:42 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host
2020-05-29 21:37:46 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host
2020-05-29 21:37:46 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host
2020-05-29 21:37:52 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host
2020-05-29 22:31:53 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host
2020-05-29 22:32:24 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 801, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
OSError: [Errno 113] No route to host

[jugla]

Hello,
I got this error
2020-06-22 19:46:08 INFO (SyncWorker_18) [root] Sending handshake.
2020-06-22 19:46:13 ERROR (MainThread) [homeassistant.core] Error doing job: Fatal read error on socket transport
Traceback (most recent call last):
File "/usr/lib/python3.7/asyncio/selector_events.py", line 801, in _read_ready__data_received
data = self._sock.recv(self.max_size)
TimeoutError: [Errno 110] Connection timed out
2020-06-22 19:46:19 INFO (SyncWorker_18) [root] Sending handshake.

(My HA version is Home Assistant 0.111.4)

arch | armv7l
-- | --
dev | false
docker | false
hassio | false
installation_type | Home Assistant Core
os_name | Linux
os_version | 4.19.118-v7l+
python_version | 3.7.3
timezone | Europe/Paris
version | 0.111.4
virtualenv | true

[abdalians]

I get the same thing..

2020-09-06 22:46:31 ERROR (MainThread) [homeassistant] 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 801, in _read_ready__data_received data = self._sock.recv(self.max_size) TimeoutError: [Errno 110] Connection timed out