Illegal instruction trying to start hass #94228
Comments
lionslair
changed the title
|
I have the same error when upgrading Core from 2023.5.4 to 2023.6.0. |
|
I have decided to migrate to the docker version. Have ported over lost nothing yet. |
|
Same issue here: Fatal Python error: Illegal instruction Thread 0x00007f501dcd66c0 (most recent call first): Thread 0x00007f501e7d76c0 (most recent call first): Thread 0x00007f5038ff96c0 (most recent call first): Thread 0x00007f50397fa6c0 (most recent call first): Thread 0x00007f5039ffb6c0 (most recent call first): Thread 0x00007f503a7fc6c0 (most recent call first): Thread 0x00007f503affd6c0 (most recent call first): Thread 0x00007f503b7fe6c0 (most recent call first): Thread 0x00007f5040b136c0 (most recent call first): Thread 0x00007f50413146c0 (most recent call first): Current thread 0x00007f5044e39040 (most recent call first): Extension modules: _cffi_backend, multidict._multidict, yarl._quoting_c, ciso8601, aiohttp._helpers, aiohttp._http_writer, aiohttp._http_parser, aiohttp._websocket, charset_normalizer.md, frozenlist._frozenlist, ulid_transform._ulid_impl, markupsafe._speedups, yaml._yaml, PIL._imaging, simplejson._speedups, sqlalchemy.cyextension.collections, sqlalchemy.cyextension.immutabledict, sqlalchemy.cyextension.processors, sqlalchemy.cyextension.resultproxy, sqlalchemy.cyextension.util, greenlet._greenlet (total: 21) |
|
Looking like it was not just a me thing |
|
The same. Fatal Python error: Illegal instruction Thread 0x00007f6789ffb700 (most recent call first): Thread 0x00007f678a7fc700 (most recent call first): Current thread 0x00007f678affd700 (most recent call first): Thread 0x00007f678b7fe700 (most recent call first): Thread 0x00007f6790b40700 (most recent call first): Thread 0x00007f6791341700 (most recent call first): Thread 0x00007f6794987280 (most recent call first): Extension modules: _cffi_backend, multidict._multidict, yarl._quoting_c, ciso8601, aiohttp._helpers, aiohttp._http_writer, aiohttp._http_parser, aiohttp._websocket, charset_normalizer.md, frozenlist._frozenlist, ulid_transform._ulid_impl, markupsafe._speedups, yaml._yaml (total: 13) |
|
I might have an answer on why we get this error. In HA 2023.6.0 the orjson dependency is updated from 3.8.10 to 3.8.12 and it seems that orjson changed the wheel in 3.8.11 to require x86-64-v2. My (old) CPU only supports x86-64-v1 and other people also had that issue with orjson so they reverted that requirement in 3.8.14. See here for more info. |
|
ah. I thought it might be linked to wheel. I remember when it went from 3.9 to 3.10 I had some funny issues to. This time just could not work it out so switched to docker. |
|
I can confirm that if I upgrade Home Assistant Core to 2023.6.1 and I manually upgrade orjson to the latest version available, hass no longer crashes. However, it has numerous other problems. I should have manually updated orjson to 3.8.14 rather than latest to test this. I'll try that at some point today... |
This helps, but after restarting hass, orjson is updated to version 3.8.12 again and hass starts again with an error. |
|
Not really surprising, but disappointing, that it will auto update after restart. Let's hope that they can update the home assistant dependency of orjson to at least 3.8.14 or higher soon. |
|
I ran into the same issue on a AMD Athlon II X4 640 CPU. I can confirm that orjson 3.8.14 does fix the issue. Restarting Home Assistant did NOT downgrade the lib from 3.8.14 to 3.8.12 for me. |
|
Same problem for me and upgrading manually to orjson 3.8.14 fix it ! |
|
It did it for me too thanks a lot doudz
pulseaudio --start ( need for audio running sox) |
|
Upgrading orjson to 3.8.14 allowed me to start Home Assistant, however there were some errors with integrations like Cloud, SmartThings etc. I'd have tried a restart to see if that would fix those, however orjson was auto-downgraded to 3.8.12 so Home Assistant wouldn't start more than once. For now I've downgraded to 2023.5.4 and will wait for an official fix - there's nothing in 2023.6 I need badly enough to go further into the rabbit hole. |
Newer versions also fit for my instance: |
|
I was getting the "Illegal instruction" error too. I spent the last few days debugging and finally got it working. I'm guessing other people getting this error are finding this thread, so I'll summarize what I learned and what worked. Some context: I was updating the The issue: running the following code Produces the error I tried a bunch of things (which didn't work) so I started digging into the source code to figure out where this error message is coming from. Eventually I determined the error is produced upon running this line (of python code): import jwtwhich is from the Key takeaway so far: if you're getting the "Illegal instruction" error, try running I had version 2.5 of pyjwt. I tried installing a bunch of different (earlier and later) versions, but they all produced the same error. Then I tried a different python virtual environment and found that pyjwt worked there, so I decided to make a whole new virtual environment. Since I was running Python 3.9 before, I decided it was a good time to upgrade to 3.10. I used Then I tried
Since maturin is a tool for building and publishing Rust-based Python packages, I wanted to try upgrading rust but I couldn't figure out how to upgrade the existing one on my rpi. So instead I installed a new one. I don't know much about rust, but apparently "rust" and "rustup" both install the rust compiler but rustup is more developer-oriented. Following standard installation procedure, I used Finally, running Final takeaways:
Hope this helps someone! |
|
Andy
the trick I use is putting the install of 3.8.14 everytime I was starting HA .
Please note since about a week it seem the uprgrade is holding therefore I commented out the orjson install as follows. Might be you will witness the same result yourself and dont have to resort to same solution .
Here is my startup routine HAstart.sh :
pulseaudio --start ( needed cause I use recording of my voices to hook with ALEXA )
#python3 -m venv . ( needed only once when I install python 3.10 )
source bin/activate
#python3 -m pip install orjson==3.8.14 ( early install orjson at each startup dont seem to be needed anymore )
hass
GiMiSa
Le mardi 20 juin 2023 à 05 h 05 min 52 s HAE, Andy ***@***.***> a écrit :
Upgrading orjson to 3.8.14 allowed me to start Home Assistant, however there were some errors with integrations like Cloud, SmartThings etc.
I'd have tried a restart to see if that would fix those, however orjson was auto-downgraded to 3.8.12 so Home Assistant wouldn't start more than once.
For now I've downgraded to 2023.5.4 and will wait for an official fix - there's nothing in 2023.6 I need badly enough to go further into the rabbit hole.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
@skylogic004 I get neither the jwt nor maturin errors, and both orjson 3.1.12 (HA requirement) and 3.8.14 (needed to fix the illegal instruction error and allow HA 2023.6 to start) install just fine, so I think these may be errors related to your specific environment. @gimisa Yes, having orjson upgrade at each start-up to 3.8.14 should work, however this is the rabbit hole I was referring to. Firstly I'd need to come up with some sort of custom start-up, like your HAstart.sh. I don't like custom fixes unless they are absolutely necessary and I currently use HA Core as provided by the HA team, this would introduce non-standard complexity that I'd like to avoid. Secondly, as I mentioned before, even when HA starts using 3.8.14 I was seeing errors in other in various integrations, likely caused by the fact that I was using a newer version of orjson than HA requires. I could go down both these routes to get HA 2023.6 working, and I may or may not be successful, but I'd rather see the underlying problem solved properly. The second issue in particular could take an unknown amount of work/time to fix (and a fix would not be guaranteed) so that's a path I won't go down. I've just tried upgrading to 2023.6.3 (latest) and the problem is still there. I'll try again when 2023.7 comes out next week. Hopefully one of the HA Core developers will take a look at this - anyone know how best to bring it to their attention? |
|
Please try 2023.7.0b0 it has orjson 3.9.1 |
|
Installed 2023.7.0b0 and it seems to be about the same as when I forced orjson 3.8.14 to install. There are numerous components that fail, namely cloud, tts.google.translate, mobile_app, and default_config. |
|
I agree totaly with you . I currently use HA Core as provided by the HA team too under ubuntu 22.04 operating system updated each time of install new HA core . One reason to use core is to give HA developpers feedback on their changes . I too notice warning on integration that use to work with 3.9 python .Hoping our comments are helpfulll if not to developpers at least to other core users.
The report channel for developpers is : https://github.com/home-assistant/core/issues
GiMiSa
Le jeudi 29 juin 2023 à 07 h 58 min 33 s HAE, Andy ***@***.***> a écrit :
@skylogic004 I get neither the jwt nor maturin errors, and both orjson 3.1.12 (HA requirement) and 3.8.14 (needed to fix the illegal instruction error and allow HA 2023.6 to start) install just fine, so I think these may be errors related to your specific environment.
@gimisa Yes, having orjson upgrade at each start-up to 3.8.14 should work, however this is the rabbit hole I was referring to.
Firstly I'd need to come up with some sort of custom start-up, like your HAstart.sh. I don't like custom fixes unless they are absolutely necessary and I currently use HA Core as provided by the HA team, this would introduce non-standard complexity that I'd like to avoid.
Secondly, as I mentioned before, even when HA starts using 3.8.14 I was seeing errors in other in various integrations, likely caused by the fact that I was using a newer version of orjson than HA requires.
I could go down both these routes to get HA 2023.6 working, and I may or may not be successful, but I'd rather see the underlying problem solved properly.
The second issue in particular could take an unknown amount of work/time to fix (and a fix would not be guaranteed) so that's a path I won't go down.
I've just tried upgrading to 2023.6.3 (latest) and the problem is still there. I'll try again when 2023.7 comes out next week.
Hopefully one of the HA Core developers will take a look at this - anyone know how best to bring it to their attention?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
|
| | |
|
|
|
| |
Issues · home-assistant/core
:house_with_garden: Open source home automation that puts local control and privacy first. - Issues · home-assis...
|
|
|
|
|
I installed 2023.7.0b5 today and all issues appear to be resolved in this version. |
|
Thanks for confirming |
|
I just upgraded to 2023.7.1 to see if this was fixed. On restarting HA hung. Restarting using sysctl from the command line worked, but I had errors just like these:
A further soft restart, and (so far) things seem back to normal 🤞 Realise this is closed, and this doesn't change that, but posting in case someone gets to the first stage and thinks of reverting to 2023.5 - it might be worth a further soft restart before you do. |
The problem
I am trying to upgrade to 2023.6.0 using the core installation. I have been running all previous installs via core with no issues.
I was already running 2023.5.4 on python3.11
What version of Home Assistant Core has the issue?
2023.6.0
What was the last working version of Home Assistant Core?
2023.5.4
What type of installation are you running?
Home Assistant Core
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
This is the contents of home-assistant.log.fault
Fatal Python error: Illegal instruction
Current thread 0x00007f664bfff700 (most recent call first):
File "/srv/homeassistant/.virtualenv/lib/python3.11/site-packages/homeassistant/util/json.py", line 68 in load_json
File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58 in run
File "/usr/lib/python3.11/concurrent/futures/thread.py", line 83 in _worker
File "/usr/lib/python3.11/threading.py", line 975 in run
File "/usr/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
File "/usr/lib/python3.11/threading.py", line 995 in _bootstrap
Thread 0x00007f6650bb2700 (most recent call first):
File "/usr/lib/python3.11/logging/handlers.py", line 1528 in dequeue
File "/usr/lib/python3.11/logging/handlers.py", line 1579 in _monitor
File "/usr/lib/python3.11/threading.py", line 975 in run
File "/usr/lib/python3.11/threading.py", line 1038 in _bootstrap_inner
File "/usr/lib/python3.11/threading.py", line 995 in _bootstrap
Thread 0x00007f6654011740 (most recent call first):
File "/usr/lib/python3.11/selectors.py", line 468 in select
File "/usr/lib/python3.11/asyncio/base_events.py", line 1884 in _run_once
File "/usr/lib/python3.11/asyncio/base_events.py", line 607 in run_forever
File "/usr/lib/python3.11/asyncio/base_events.py", line 640 in run_until_complete
File "/srv/homeassistant/.virtualenv/lib/python3.11/site-packages/homeassistant/runner.py", line 179 in run
File "/srv/homeassistant/.virtualenv/lib/python3.11/site-packages/homeassistant/main.py", line 214 in main
File "/srv/homeassistant/.virtualenv/bin/hass", line 8 in
Extension modules: _cffi_backend, multidict._multidict, yarl._quoting_c, ciso8601, aiohttp._helpers, aiohttp._http_writer, aiohttp._http_parser, aiohttp._websocket, charset_normalizer.md, frozenlist._frozenlist, ulid_transform._ulid_impl, markupsafe._speedups, yaml._yaml (total: 13)
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
I can rollback to 2023.5.4 no issues
The text was updated successfully, but these errors were encountered: