Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error doing job: SSL error errno:1 reason: KRB5_S_INIT #21270

Closed
garyak opened this issue Feb 21, 2019 · 32 comments
Closed

Error doing job: SSL error errno:1 reason: KRB5_S_INIT #21270

garyak opened this issue Feb 21, 2019 · 32 comments
Labels
core problem in dependency stale

Comments

@garyak
Copy link

garyak commented Feb 21, 2019 •
edited by awarecan
Loading

Getting this every few minutes after 88.0 installation:

2019-02-21 09:42:12 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: KRB5_S_INIT

Home Assistant release with the issue:
Hassio 88.0
HassOS 1.9

Last working Home Assistant release (if known):
Hassio 87.1

Operating environment (Hass.io/Docker/Windows/etc.):

RPi3B+, Hass.io

Component/platform:
unknown

Description of problem:
Logging these errors every few minutes.

Traceback (if applicable):

Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
  File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
  File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
  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)

Additional information:
My config network setup:

http:
  api_password: !secret http_password
  base_url: !secret http_base
  trusted_networks:
    - 192.168.3.0/24
    - 127.0.0.1
  ip_ban_enabled: true
  login_attempts_threshold: 5

Have a fixed IP, so no dns or encryption configured. Tried to move away from legacy auth a few releases ago, but got failed login attempts from my router IP.
@awarecan
Copy link
Contributor

so your base_url is http://12.34.56.78:8123? not https?

@awarecan
Copy link
Contributor

awarecan commented Feb 21, 2019 •
edited
Loading

May be related with aio-libs/aiohttp#3535

It seems caused by aiohttp client, therefore it is not matter if you host your sever in http or https. We have bunch of components are using aiohttp client communicate with third party services.

@garyak
Copy link
Author

garyak commented Feb 21, 2019

Yes. Base url is http://

@vinmar1
Copy link

vinmar1 commented Feb 22, 2019

I occasionally have this exact same error... Traceback is identical

Intel-NUC, Ubuntu 18.04.2 LTS, Current Docker, Home Assistant 0.88.0

@godinperson
Copy link

godinperson commented Feb 22, 2019 •
edited by MartinHjelmare
Loading

I don't know if it can help but I'm on Rpi3 Wifi and I'm trying to update from HassOS 2.8 to 2.10. This is what I get:

19-02-22 15:34:05 WARNING (MainThread) [hassio.hassos] Can't fetch versions from https://github.com/home-assistant/hassos/releases/download/2.10/hassos_rpi3-64-2.10.raucb: 
19-02-22 15:34:09 ERROR (MainThread) [asyncio] SSL error errno:1 reason: KRB5_S_INIT
protocol: <uvloop.loop.SSLProtocol object at 0x7f80f26978>
transport: <TCPTransport closed=False reading=False 0x558c64c058>
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
  File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
  File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
  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)

@jazzyisj
Copy link

jazzyisj commented Feb 24, 2019 •
edited
Loading

Same deal here. Rpi3 hardwired. Hassio 0.88.1
Trying to update HassOS from 1.13 (yeah I kinda fell behind).

Error from SU log.

19-02-24 04:46:41 INFO (MainThread) [hassio.hassos] Fetch OTA update from https://github.com/home-assistant/hassos/releases/download/2.10/hassos_rpi3-2.10.raucb
19-02-24 04:46:42 ERROR (MainThread) [asyncio] SSL error errno:1 reason: KRB5_S_INIT
protocol: <uvloop.loop.SSLProtocol object at 0x71a5a270>
transport: <TCPTransport closed=False reading=False 0x71a587f0>
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
  File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
  File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
  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)

Also getting similar error in HA log. Haven't determined what's triggering it yet.

2019-02-23 23:42:25 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: KRB5_S_INIT
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
  File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
  File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
  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)

@jazzyisj
Copy link

Huh. HassOS ended up updating to 2.10 despite the error...

@awarecan
Copy link
Contributor

This error message means although HA already notify the remote party the socket was closed, there was still some data sent to socket. It may not affect any function.

@jazzyisj
Copy link

Thanks for the explanation @awarecan!

@whiskerz007 whiskerz007 mentioned this issue Feb 25, 2019
Closed
@garyak
Copy link
Author

garyak commented Mar 6, 2019

Does this mean I need to update HassOS, currently 1.9, from the system page outside of the usual Hass.io update process?

@garyak
Copy link
Author

garyak commented Mar 10, 2019

Hass.io Supervisor @ 148
HassOS @ 2.10
HA 89.1

Error persists. Logged every two to four minutes.

@remontti
Copy link

remontti commented Mar 13, 2019 •
edited
Loading

I can not update here either

Hassio 0.89.2
Supervisor 148
HassOS 1.13

Error: 502: Bad Gateway

9-03-13 12:23:32 INFO (MainThread) [hassio.hassos] Fetch OTA update from https://github.com/home-assistant/hassos/releases/download/2.10/hassos_rpi3-2.10.raucb
19-03-13 12:28:32 WARNING (MainThread) [hassio.hassos] Can't fetch versions from https://github.com/home-assistant/hassos/releases/download/2.10/hassos_rpi3-2.10.raucb: 
19-03-13 12:28:32 ERROR (MainThread) [asyncio] SSL error errno:1 reason: KRB5_S_INIT
protocol: <uvloop.loop.SSLProtocol object at 0x71813490>
transport: <TCPTransport closed=False reading=False 0x71814600>
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
  File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
  File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
  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)

@hawaltie
Copy link

I also have the same problem every now and then,

Intel NUC
Ubuntu 18.04.2 LTS
Home assistant 0.89.2

Since release 0.86 I get all kinds of connectivity problems (hue bridge etc.). Don't kwow if it is related.

@warcanoid
Copy link

Same problems!

@garyak
Copy link
Author

garyak commented Mar 21, 2019

I'm sorry to report this error is still with me in HA 0.90.0, HassOS 2.1.

@tradenet
Copy link

It just appeared for the first time for me in HA 0.90.1 HassOS 2.11. Never seen it before until now.

@SeanPM5
Copy link
Contributor

SeanPM5 commented Mar 28, 2019

I encountered this same error when updating from HassOS 2.10 to 2.11 last night.

19-03-28 06:16:45 INFO (MainThread) [hassio.hassos] Fetch OTA update from https://github.com/home-assistant/hassos/releases/download/2.11/hassos_rpi3-2.11.raucb
19-03-28 06:16:45 ERROR (MainThread) [asyncio] SSL error errno:1 reason: KRB5_S_INIT
protocol: <uvloop.loop.SSLProtocol object at 0x71d07cf0>
transport: <TCPTransport closed=False reading=False 0x71a6d9e0>
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
  File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
  File "uvloop/sslproto.pyx", line 189, in uvloop.loop._SSLPipe.feed_ssldata
  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)
19-03-28 06:16:53 INFO (MainThread) [hassio.hassos] OTA update is downloaded on /data/tmp/hassos-2.11.raucb

It rebooted right after this and failed to come back up. Couldn't SSH into it either. After giving it ~45+ mins of being stuck I decided to pull power on my Pi. It did come back online thankfully and the system section says 2.11 so I guess the update did go through, but that was very scary.

@hristo-atanasov
Copy link
Contributor

Following. I have the same error in the logs .. hassio 0.89

@garyak
Copy link
Author

garyak commented Apr 4, 2019

Repetitive error message now appears in 0.91.0 as:

2019-04-04 11:25:48 ERROR (MainThread) [homeassistant.core] 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)

@tradenet
Copy link

tradenet commented Apr 4, 2019

Repetitive error message now appears in 0.91.0 as:

2019-04-04 11:25:48 ERROR (MainThread) [homeassistant.core] 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)

I have this issue as well.

@msauto
Copy link

msauto commented Apr 11, 2019

Repetitive error message now appears in 0.91.0 as:

2019-04-04 11:25:48 ERROR (MainThread) [homeassistant.core] 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)

Me Too! I recently installed the traccar add on in hassio 091 , didn't notice it until then. Could have been there and didn't see it, but pretty sure it wasn't. I had to add "ssl: true" and "verify_ssl: false" in the yaml setup to get it to communicate with hassio (dont use ssl). Not sure if this is relevant or not maybe it'll help someone way smarter than me figure this out. @frenck what do you think?

@GLEIPNIRS GLEIPNIRS mentioned this issue Apr 13, 2019
Closed
@garyak
Copy link
Author

garyak commented Apr 27, 2019

Repetitive error message continues in 0.92.1:

2019-04-27 09:17:36 ERROR (MainThread) [homeassistant.core] 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)

@philgree
Copy link

Also 93.1:

19-05-18 09:49:30 WARNING (MainThread) [hassio.hassos] Can't fetch versions from https://github.com/home-assistant/hassos/releases/download/2.12/hassos_ova-2.12.raucb:
19-05-18 09:49:30 ERROR (MainThread) [asyncio] Fatal error on transport
protocol: <uvloop.loop.SSLProtocol object at 0x7fb13d6db608>
transport: <TCPTransport closed=False reading=False 0x560fb16f7578>
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)
19-05-18 09:53:21 INFO (MainThread) [hassio.hassos] Fetch OTA update from https://github.com/home-assistant/hassos/releases/download/2.12/hassos_ova-2.12.raucb

@philgree
Copy link

I was ultimately able to update. I'm unsure that what I did actually contributed to it working but am sharing just in case it can help somebody else....

About my environment: I'm running HassOS inside a Proxmox VM on a NUC and was attempting to upgrade from HassOS 2.11 to 2.12.

I found that a simple reboot of the HassOS VM didn't make any difference to the problem but when I shutdown ALL Proxmox VMs and did a reboot of Proxmox itself before bringing HassOS back up again I was then able to update HassOS without error.

If anybody else has the same experience (or finds rebooting Proxmox DOESN'T work for them) please add a comment. In the meantime I'll be adding reboot of Proxmox to my troubleshooting repertoire for future problems.

@KavajNaruj
Copy link

@philgree I have similar problem, what do you mean with:

before bringing HassOS back up again

how do you exactly upgrade?

@garyak
Copy link
Author

garyak commented Jul 26, 2019 

2019-07-26 17:48:34 ERROR (MainThread) [homeassistant.core] 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 778, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2629)

Still going strong every 10 minutes or so in 96.5.

@gurbina93
Copy link

gurbina93 commented Aug 4, 2019 •
edited
Loading

Getting this error now and a few components stopped working. Basically some HA components are starting to fail randomly.

2019-08-04 20:09:45 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.plex
2019-08-04 20:09:48 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:09:49 ERROR (MainThread) [homeassistant.components.unifi] Error connecting to the UniFi controller at 192.168.0.222
2019-08-04 20:09:49 WARNING (MainThread) [homeassistant.config_entries] Config entry for unifi not ready yet. Retrying in 20 seconds.
2019-08-04 20:09:52 INFO (SyncWorker_15) [homeassistant.components.plex.media_player] Discovery configuration done (no token needed)
2019-08-04 20:09:52 INFO (SyncWorker_6) [homeassistant.components.plex.media_player] Discovery configuration done (no token needed)
2019-08-04 20:09:52 INFO (SyncWorker_6) [homeassistant.components.plex.media_player] Connected to: http://192.168.0.220:32400
2019-08-04 20:09:52 INFO (SyncWorker_15) [homeassistant.components.plex.media_player] Connected to: http://192.168.0.220:32400
2019-08-04 20:09:53 WARNING (SyncWorker_3) [homeassistant.components.tplink.switch] Could not read state for 192.168.0.163: Communication error
2019-08-04 20:10:19 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:10:20 ERROR (MainThread) [homeassistant.components.unifi] Error connecting to the UniFi controller at 192.168.0.222
2019-08-04 20:10:20 WARNING (MainThread) [homeassistant.config_entries] Config entry for unifi not ready yet. Retrying in 40 seconds.
2019-08-04 20:10:21 ERROR (MainThread) [homeassistant.core] 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 778, in unwrap
return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2629)
2019-08-04 20:10:50 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:10:50 INFO (MainThread) [hole] Response from *hole: 200
2019-08-04 20:11:03 INFO (MainThread) [homeassistant.components.switch] Setting up switch.unifi
**2019-08-04 20:11:11 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1876883152] Communication error
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/pyHS100/smartdevice.py", line 117, in _query_helper
request=request,
File "/usr/local/lib/python3.7/site-packages/pyHS100/protocol.py", line 47, in query
sock = socket.create_connection((host, port), timeout)
File "/usr/local/lib/python3.7/socket.py", line 727, in create_connection
raise err
File "/usr/local/lib/python3.7/socket.py", line 716, in create_connection
sock.connect(sa)
socket.timeout: timed out
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 121, in handle_call_service
connection.context(msg))
File "/usr/src/homeassistant/homeassistant/core.py", line 1150, in async_call
self._execute_service(handler, service_call))
File "/usr/src/homeassistant/homeassistant/core.py", line 1172, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 194, in handle_service
required_features
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 316, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call
await getattr(entity, func)(**data)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/tplink/switch.py", line 114, in turn_on
self.smartplug.turn_on()
File "/usr/local/lib/python3.7/site-packages/pyHS100/smartplug.py", line 158, in turn_on
self._query_helper("system", "set_relay_state", {"state": 1})
File "/usr/local/lib/python3.7/site-packages/pyHS100/smartdevice.py", line 120, in _query_helper
raise SmartDeviceException('Communication error') from ex
pyHS100.smartdevice.SmartDeviceException: Communication error
2019-08-04 20:11:17 INFO (SyncWorker_11) [homeassistant.components.miflora.sensor] Polling error
2019-08-04 20:11:17 INFO (SyncWorker_2) [homeassistant.components.miflora.sensor] Polling error Could not read data from Mi Flora sensor C4:7C:8D:6A:83:7E
2019-08-04 20:11:17 INFO (SyncWorker_14) [homeassistant.components.miflora.sensor] Polling error Could not read data from Mi Flora sensor C4:7C:8D:6A:83:7E
2019-08-04 20:11:17 INFO (SyncWorker_10) [homeassistant.components.miflora.sensor] Polling error Could not read data from Mi Flora sensor C4:7C:8D:6A:83:7E
2019-08-04 20:11:17 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1876883152] Communication error
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/pyHS100/smartdevice.py", line 117, in _query_helper
request=request,
File "/usr/local/lib/python3.7/site-packages/pyHS100/protocol.py", line 47, in query
sock = socket.create_connection((host, port), timeout)
File "/usr/local/lib/python3.7/socket.py", line 727, in create_connection
raise err
File "/usr/local/lib/python3.7/socket.py", line 716, in create_connection
sock.connect(sa)
socket.timeout: timed out
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 121, in handle_call_service
connection.context(msg))
File "/usr/src/homeassistant/homeassistant/core.py", line 1150, in async_call
self._execute_service(handler, service_call))
File "/usr/src/homeassistant/homeassistant/core.py", line 1172, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 194, in handle_service
required_features
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 316, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call
await getattr(entity, func)(**data)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/tplink/switch.py", line 114, in turn_on
self.smartplug.turn_on()
File "/usr/local/lib/python3.7/site-packages/pyHS100/smartplug.py", line 158, in turn_on
self._query_helper("system", "set_relay_state", {"state": 1})
File "/usr/local/lib/python3.7/site-packages/pyHS100/smartdevice.py", line 120, in _query_helper
raise SmartDeviceException('Communication error') from ex
pyHS100.smartdevice.SmartDeviceException: Communication error
2019-08-04 20:11:21 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:11:24 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1876883152] Communication error
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/pyHS100/smartdevice.py", line 117, in _query_helper
request=request,
File "/usr/local/lib/python3.7/site-packages/pyHS100/protocol.py", line 47, in query
sock = socket.create_connection((host, port), timeout)
File "/usr/local/lib/python3.7/socket.py", line 727, in create_connection
raise err
File "/usr/local/lib/python3.7/socket.py", line 716, in create_connection
sock.connect(sa)
socket.timeout: timed out
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 121, in handle_call_service
connection.context(msg))
File "/usr/src/homeassistant/homeassistant/core.py", line 1150, in async_call
self._execute_service(handler, service_call))
File "/usr/src/homeassistant/homeassistant/core.py", line 1172, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 194, in handle_service
required_features
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 316, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 337, in _handle_service_platform_call
await getattr(entity, func)(**data)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/tplink/switch.py", line 114, in turn_on
self.smartplug.turn_on()
File "/usr/local/lib/python3.7/site-packages/pyHS100/smartplug.py", line 158, in turn_on
self._query_helper("system", "set_relay_state", {"state": 1})
File "/usr/local/lib/python3.7/site-packages/pyHS100/smartdevice.py", line 120, in _query_helper
raise SmartDeviceException('Communication error') from ex
pyHS100.smartdevice.SmartDeviceException: Communication error
2019-08-04 20:11:26 WARNING (SyncWorker_3) [homeassistant.components.tplink.switch] Could not read state for 192.168.0.163: Communication error
2019-08-04 20:11:27 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.plant_battery is taking over 10 seconds
2019-08-04 20:11:52 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:12:23 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:12:54 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:13:25 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:13:26 INFO (MainThread) [homeassistant.components.automation] Executing NightLampOffIfNoMotion
2019-08-04 20:13:26 INFO (MainThread) [homeassistant.helpers.script] Script NightLampOffIfNoMotion: Running script
2019-08-04 20:13:26 INFO (MainThread) [homeassistant.helpers.script] Script NightLampOffIfNoMotion: Executing step call service
2019-08-04 20:13:54 INFO (SyncWorker_13) [homeassistant.components.miflora.sensor] Polling error
2019-08-04 20:13:55 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:14:26 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:14:57 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:15:03 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.brtemp_humidity is taking over 10 seconds
2019-08-04 20:15:28 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:15:59 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:15:59 INFO (MainThread) [hole] Response from *hole: 200
2019-08-04 20:16:22 WARNING (SyncWorker_13) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-08-04 20:16:30 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:16:32 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.brtemp_battery is taking over 10 seconds
2019-08-04 20:16:35 WARNING (SyncWorker_3) [homeassistant.components.tplink.switch] Could not read state for 192.168.0.163: Communication error
2019-08-04 20:17:01 WARNING (MainThread) [homeassistant.components.sensor] Updating mitemp_bt sensor took longer than the scheduled update interval 0:00:30
2019-08-04 20:17:09 WARNING (SyncWorker_6) [homeassistant.components.mitemp_bt.sensor] Polling error
2019-08-04 20:17:09 WARNING (SyncWorker_14) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:A5:8B
2019-08-04 20:17:32 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:A5:8B
2019-08-04 20:17:32 WARNING (SyncWorker_7) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:A5:8B
2019-08-04 20:17:42 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.brtemp_battery is taking over 10 seconds
2019-08-04 20:18:03 WARNING (SyncWorker_9) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:A5:8B
2019-08-04 20:18:03 WARNING (SyncWorker_15) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:A5:8B
2019-08-04 20:18:35 WARNING (SyncWorker_1) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:A5:8B
2019-08-04 20:18:35 WARNING (SyncWorker_0) [homeassistant.components.mitemp_bt.sensor] Polling error Could not read data from Mi Temp sensor 4C:65:A8:D5:A5:8B
2019-08-04 20:18:51 INFO (MainThread) [homeassistant.components.stream] Stopped stream workers.
2019-08-04 20:18:51 INFO (SyncWorker_8) [homeassistant.components.xiaomi_aqara] Shutting down Xiaomi Hub
2019-08-04 20:18:51 INFO (SyncWorker_8) [xiaomi_gateway] Closing multisocket
2019-08-04 20:18:51 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1876883152] Connection closed by client
2019-08-04 20:18:51 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.1874147504] Connection closed by client
2019-08-04 20:20:40 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for smartir 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.
2019-08-04 20:20:53 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for sonoff 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.

@pilot1981
Copy link

I have the same log error

@sirs2k
Copy link

sirs2k commented Aug 7, 2019

Been having a very similar traceback for a while

[homeassistant.core] 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 778, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2629)

@edif30
Copy link
Contributor

edif30 commented Aug 8, 2019 •
edited
Loading

Just started getting this error after 0.97.0 update.

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 778, in unwrap
    return self._sslobj.shutdown()
ssl.SSLError: [SSL: KRB5_S_INIT] application data after close notify (_ssl.c:2629)

This is actually being caused by the IQVIA component. Every time it tries to pull from the api it is failing due to some issue on the endpoint. #25657. As soon as I removed the IQVIA integration (both config.yaml and UI integration!!!!) the issue went away. Note: Don't expect to just remove or comment out the config.yaml and believe it will disable the component. You have to delete the integration as well in the UI. It's not documented so be aware.

@bbrendon bbrendon mentioned this issue Sep 1, 2019
Closed
@stale
Copy link

stale bot commented Nov 6, 2019

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.

@stale stale bot added the stale label Nov 6, 2019
@garyak garyak closed this as completed Nov 6, 2019
@garyak
Copy link
Author

garyak commented Nov 6, 2019

As of 0.101.2, There errors no longer appear in the HA log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
core problem in dependency stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests