Need assistance troubleshooting - unable to access webui. Issue with core?

Configuration
1

I keep having an issue where my HAOS system keeps going offline for no apparent reason. What I mean by that is, I can’t connect to the UI with the companion app or web. Alerts/automations don’t happen. I can SSH to the system just fine but I can’t issue any ‘ha core’ commands without them timing out.

I have the syslog add-on so my logs are going to graylog. I did see this which must be relevant:

homeassistant systemd: Started Process Core Dump (PID 216921/UID 0).
homeassistant homeassistant: [02:26:08] INFO: Home Assistant Core finish process exit code 256
homeassistant homeassistant: [02:26:08] INFO: Home Assistant Core finish process received signal 11

I’ve run this on a bare metal HP EliteDesk 800 G2 and had this same issue. I thought maybe it was a hardware issue so I installed proxmox and HAOS on top, according to this guide. I was expecting if there was a hardware issue, proxmox would die too. Well, proxmox is just fine but I still have the HAOS issue.

This most recent time it failed, I did see a log file with a .fault extension (which is odd because in the past this file was never generated). I will attach it here. Also unique to this most recent failure is the terminal/screen of the VM had what appears to be a dump.

I have a hunch that this might be related to my zooz USB stick (using USB pass-through in proxmox) but I have no way to prove it. If it comes down to it, I can remove the stick and let it run but I have a lot of lighting automations that run on zwave. I’m hoping there is something in the logs that would help prove my hunch.

At any rate, any assistance would be greatly appreciated. I’m sure I’m not supplying critical information so please let me know if I can provide anything else of value.

Screenshot 2024-10-04 071831
Screenshot 2024-10-04 0718311402×871 165 KB

Screenshot 2024-10-04 122320
Screenshot 2024-10-04 1223201401×878 153 KB

2

I can’t attach a text file and there are too many characters for a single post, so I uploaded the .fault file to pastebin: Fatal Python error: Segmentation faultThread 0x00007fb3f0abcb30 (most recent - Pastebin.com

3

I believe there is a new log file, one for each restart of the system. At the end of home-assistant.log.1 is the following:

2024-10-03 20:03:56.085 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:08:56.336 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:13:56.640 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:15:21.670 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [140411240957552] Jim from 192.168.40.2 (Home Assistant/2024.9.4-13806
2024-10-03 20:18:56.885 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:23:57.137 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:25:21.671 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [140410912369984] Jim from 192.168.0.93 (Home Assistant/2024.9.4-13806
2024-10-03 20:28:57.435 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:32:54.420 WARNING (MainThread) [aioesphomeapi.connection] bluetooth-proxy-1 @ 192.168.50.34: Connection error occurred: Ping response not received after 90.0
2024-10-03 20:32:55.033 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for bluetooth-proxy-1 @ 192.168.50.34: Error connecting to [AddrIn
2024-10-03 20:33:57.702 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:33:57.950 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:33:58.139 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:33:58.320 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:38:58.639 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:43:58.933 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:48:59.183 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:53:59.497 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 20:58:59.774 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 21:04:00.035 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 21:09:00.320 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 21:14:00.630 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 21:19:00.909 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket
2024-10-03 21:24:01.164 WARNING (MainThread) [homeassistant.components.simplisafe] Reconnecting to websocket

It looks like it just abruptly stops…

This is the version information for my system:

  • Core 2024.10.0
  • Supervisor 2024.09.1
  • Operating System 13.1
  • Frontend 20241002.2

Add-ons:

  • ESPHome
  • File Editor (disabled to see if this was the cause; it wasn’t)
  • Matter Server
  • Mosquito broker
  • OpenThread Border Router
  • Piper
  • rtl_433
  • rtl_433 MQTT Auto Discovery
  • SQLite Web
  • Syslog
  • Terminal & SSH
  • Whisper
  • Z-Wave JS UI

HACS Add-ons:

  • mini-graph-card
  • card-mod
  • ha-floorplan
  • Bambu Lab
  • Dual gauge card
  • BlueIris NVR
  • Google Theme
  • Life360
  • remote_syslog
4

Hi tredecim,

Do you use AMP,Alexa Media Player?
If you do…
PSA: Alexa Media Player v4.13.3 breaks all versions of Home Assistant.

5

Thanks for the tip, but I don’t use Alexa Media Player.

6

then I would look for something else crashing your syste., another Integration most likely.

7

Hi, of course you do: remove the stick and/or stop the integration that it’s using.
Other thing to try is booting in safe mode.

Of course your system will be crippled but at least you are narrowing it down until someone else has a better idea.