-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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.
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
AttributeError: 'NoneType' object has no attribute 'get_extra_info' #9762
Comments
I see these messages as well. 0.56dev and older versions too |
Same error. Also SSL configured (not using self signed tho).. |
Same here...
|
Same here, Python 3.6.0 |
Same also.
|
Still present in 0.56.2 :( |
I have the same errors |
Can also confirm same issue still exist in 0.56.2 |
Seems to fix the issue : https://github.com/python/cpython/pull/525/files |
Slightly different now.. AttributeError: 'NoneType' object has no attribute 'ssl_object' Traceback (most recent call last):
Nov 01 17:39:57 Carlo-Pi hass[468]: File "/usr/local/lib/python3.6/asyncio/events.py", line 127,
in _run
Nov 01 17:39:57 Carlo-Pi hass[468]: self._callback(*self._args)
Nov 01 17:39:57 Carlo-Pi hass[468]: File "/usr/local/lib/python3.6/asyncio/sslproto.py", line 666
, in _process_write_backlog
Nov 01 17:39:57 Carlo-Pi hass[468]: self._on_handshake_complete(exc)
Nov 01 17:39:57 Carlo-Pi hass[468]: File "/usr/local/lib/python3.6/asyncio/sslproto.py", line 580
, in _on_handshake_complete
Nov 01 17:39:57 Carlo-Pi hass[468]: sslobj = self._sslpipe.ssl_object
Nov 01 17:39:57 Carlo-Pi hass[468]: AttributeError: 'NoneType' object has no attribute 'ssl_object' |
I can confirm that it fixes the issue @jinjeul No idea how to get this into home assistant, since it seems to be a bug in python? |
@balloob what do you think? |
this is my current solution:
|
This is the fix for the error ? #10741 |
I'm still receiving this error on 0.59.1 running Hassbian on a Pi 3:
|
HA 0.59.2
|
HA 0.60 Same here:
|
Daehnie, |
same error
|
I'm seeing this error as well, but I'm still on python 3.5. I'll try upgrading to 3.6 and see if that solves it (using this thread to guide my installation). HA 0.61 Tue Jan 16 2018 15:20:03 GMT-0800 (PST)
|
I've updated my system to use Python 3.6 and I'm still getting the error. After further investigation -- if I'm reading github correctly -- it appears you need Python v3.7.0a1 or higher to get the fix commit for this issue: |
I bit the bullet and manually changed the sslproto.py file. Fixed the issue for me. These were my steps on a raspberry pi (stretch) and python 3.6:
|
I'm on a Raspberry Pi running Stretch and Python 3.5. I tried @donkawechico's fix and received the following error:
Do we really need to upgrade to 3.6 to resolve this issue? |
Please don't post without new info. Use subscribe button and thumbs up the original post. |
I can confirm it is upstream issue - https://bugs.python.org/issue29742 For Python 3.5 it is fixed in "Python 3.5.4 release candidate 1" onward. For Debian / Raspbian, I decided not to upgrade default Python yet (3.5.3 in Stretch now), updating only @aaronwolen try to replace |
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 👍 |
I dont have this error msg anymore. So think this issue is fixed and can be closed? :) |
I have this error still appearing in the log...
|
Same here on 0.70.1
|
Same for me to, 0.72
|
I've been getting this a lot in 0.72 and 0.73.
Using nginx as a reverse proxy. Not sure if that would be related? |
Getting the same with 0.74.2. Not using nginx, but do use a self signed certificate. Happens when I reload the page in Chrome 68.0.3440.
|
some extra info:
|
asyncio issue (sslproto.py) has been fixed in Python 3.5.4, 3.6.2, 3.7.0. Any version below those will have this issue. The workaround is applying following patch (v3.5.3): diff --git a/Lib/asyncio/sslproto.py b/Lib/asyncio/sslproto.py
index 7ad28d6aa008..ab7ff0bf93d0 100644
--- a/Lib/asyncio/sslproto.py
+++ b/Lib/asyncio/sslproto.py
@@ -543,8 +543,10 @@ def eof_received(self):
def _get_extra_info(self, name, default=None):
if name in self._extra:
return self._extra[name]
- else:
+ elif self._transport is not None:
return self._transport.get_extra_info(name, default)
+ else:
+ return default
def _start_shutdown(self):
if self._in_shutdown: Home-assistant is unable to fix the issue. I am going to close this issue. |
Home Assistant release (
hass --version
):0.54
Python release (
python3 --version
):3.7
Component/platform:
unknown
Description of problem:
My log get spammed with messages like this.
Expected:
Possibility to ignore http/tls errors. No AttributeError
Traceback (if applicable):
Additional info:
I guess the connection attempt is from a port check or something like this.
The text was updated successfully, but these errors were encountered: