search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.31k stars 30.26k forks source link

2021.9.0 - causing my Pi3 to restart over & over ? #55541

Closed dazmc79 closed 3 years ago

dazmc79 commented 3 years ago

The problem

Since updating to the latest core version 2021.8.0 my Pi3 is stuck in a restarting loop. I dont know enough tricks to stop this cycle of restarting. Any help would be apreciated . . .

What is version of Home Assistant Core has the issue?

2021.9.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

?

Link to integration documentation on our website

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

ludeeus commented 3 years ago

Step1: Disable all custom integrations if any (renaming the custom_components directory effectively does this) Step2: Get logs from before the restart Step3: List all used integrations

ludeeus commented 3 years ago

You forgot step 1

dazmc79 commented 3 years ago

Hopefully stopped HACS this time . . . .

Logs:-

2021-09-01 22:14:12 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly 2021-09-01 22:14:12 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=359 from 2021-09-01 21:13:14.184810) 2021-09-01 22:14:23 ERROR (MainThread) [homeassistant.setup] Setup failed for adaptive_lighting: Integration not found. 2021-09-01 22:14:23 ERROR (MainThread) [homeassistant.setup] Setup failed for hacs: Integration not found. 2021-09-01 22:14:23 ERROR (MainThread) [homeassistant.config] Platform error: climate - Integration 'badnest' not found. 2021-09-01 22:14:24 ERROR (MainThread) [homeassistant.setup] Setup failed for badnest: Integration not found. 2021-09-01 22:14:25 ERROR (MainThread) [homeassistant.config] Platform error: sensor - Integration 'zwift' not found. 2021-09-01 22:14:25 ERROR (MainThread) [homeassistant.config] Platform error: sensor - Integration 'zwift' not found.

dazmc79 commented 3 years ago

Step 3 - Integrations

Adaptive Lighting Apple TV Wemo Broadlink C02 Signal deConz Google Cast Home Assistant iOS Supervisor HASS Bridge IFTTT Webhook Mobile App Mosquitto Broker Shelly Samsung TV

arjansiemons commented 3 years ago

Same issue here. Some more reports of reboot loops in the release notes discussion too.

ludeeus commented 3 years ago

@dazmc79 can you post more of your logs?

dazmc79 commented 3 years ago

thats all I can get before it restarts ?

l0wl3vel commented 3 years ago

I just reimaged my RPI3 with a fresh installation to restore a cloud backup and it lets me go through the initial setup and then crash-loops as well. From what I have read in the release notes discussion there seems to be a problem with the new release, at least for the RPI 3.

How can I downgrade when my system does not boot?

bdraco commented 3 years ago

I just did a fresh RPi3 install to 2021.9.0 and everything was ok for me so it could be a specific integration causing the problem.

dazmc79 commented 3 years ago

I just reimaged my RPI3 with a fresh installation to restore a cloud backup and it lets me go through the initial setup and then crash-loops as well. From what I have read in the release notes discussion there seems to be a problem with the new release, at least for the RPI 3.

How can I downgrade when my system does not boot?

I seem to be having the same poblem - I've flashed a fresh copy of Hassio to my Pi3 & cant even get a fresh install to work. I have a snapshot ready to go but cant get home assistant to run at all. Trying again now . . .

dazmc79 commented 3 years ago

I just reimaged my RPI3 with a fresh installation to restore a cloud backup and it lets me go through the initial setup and then crash-loops as well. From what I have read in the release notes discussion there seems to be a problem with the new release, at least for the RPI 3. How can I downgrade when my system does not boot?

I seem to be having the same poblem - I've flashed a fresh copy of Hassio to my Pi3 & cant even get a fresh install to work. I have a snapshot ready to go but cant get home assistant to run at all. Trying again now . . .

2nd attempt & same thing. After I start the onboarding Process - i.e filling in username & password. The reboot cycle starts. I cant even get to the second step of naming my home ?

matphillips commented 3 years ago

Came here to look for/report issue, glad it's not just me. Pi3, same looping issue. Currently cant access the dashboard or even SSH into the device, so cant get any logs or change any settings. Headless device and I dont have a monitor or keyboard for it (damn laptops!). Anything I can do by accessing the SD card directly?

nickrout commented 3 years ago

[S]Try renaming the custom_components directory (by plugging the SD card into another computer). That will rule out any custom components being responsible.[/S]

Probably don't bother with that, see @cogneato 's post straight after mine.

cogneato commented 3 years ago

I've updated a pi3b+ from a clean 2021.7 with default config (no added integrations) to 2021.9 and the core container/frontend does restart endlessly. The system itself does not reboot. Trying to gather further information.

matphillips commented 3 years ago

Plugged the SD into a ubuntu box, mounts four drives (hassos-data, hassos-kernel (x2) and hassos-overlay) Found the home assistant directory, so at least grabbed a copy of the backup files, but I can find no custom_components directory. Dont believe I ever had one.

The only thing in the logs that seems interesting is the warning for hose assistant.components.recorder.util about sqlite3 database as already mentioned. Is it worth moving the home-assistant_v2.db file somewhere else and seeing what happens? Does the db contain just logging data or is it the core of the settings and stuff?

bdraco commented 3 years ago

The database likely won't be too useful in tracking this down.

matphillips commented 3 years ago

found a journal file in hassos-data/logs that seems to show python3 crashing, happens multiple times in the one log file. Snippet is:

Sep 02 07:49:04 homeassistant a4773a23dc96[452]: 2021-09-02 07:49:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.espho>
Sep 02 07:49:04 homeassistant a4773a23dc96[452]: 2021-09-02 07:49:04 INFO (MainThread) [homeassistant.components.switch] Setting up switch.espho>
Sep 02 07:49:04 homeassistant a4773a23dc96[452]: 2021-09-02 07:49:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.espho>
Sep 02 07:49:04 homeassistant a4773a23dc96[452]: 2021-09-02 07:49:04 INFO (MainThread) [homeassistant.components.light] Setting up light.esphome
Sep 02 07:49:04 homeassistant a4773a23dc96[452]: 2021-09-02 07:49:04 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binar>
Sep 02 07:49:04 homeassistant a4773a23dc96[452]: 2021-09-02 07:49:04 INFO (MainThread) [homeassistant.components.switch] Setting up switch.espho>
Sep 02 07:49:04 homeassistant a4773a23dc96[452]: 2021-09-02 07:49:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.espho>
Sep 02 07:49:04 homeassistant a4773a23dc96[452]: 2021-09-02 07:49:04 INFO (MainThread) [homeassistant.setup] Setting up automation
Sep 02 07:49:05 homeassistant audit[8122]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=8122 comm="python3" exe="/>
Sep 02 07:49:05 homeassistant kernel: audit: type=1701 audit(1630536545.086:266): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pi>
Sep 02 07:49:05 homeassistant kernel: warn_alloc: 16 callbacks suppressed
Sep 02 07:49:05 homeassistant kernel: python3: page allocation failure: order:7, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null)>
Sep 02 07:49:05 homeassistant kernel: CPU: 3 PID: 8168 Comm: python3 Tainted: G         C        5.10.17-v8 #1
Sep 02 07:49:05 homeassistant kernel: Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
Sep 02 07:49:05 homeassistant kernel: Call trace:
Sep 02 07:49:05 homeassistant kernel:  dump_backtrace+0x0/0x1b0
Sep 02 07:49:05 homeassistant kernel:  show_stack+0x20/0x70
Sep 02 07:49:05 homeassistant kernel:  dump_stack+0xec/0x154
Sep 02 07:49:05 homeassistant kernel:  warn_alloc+0xf8/0x170
Sep 02 07:49:05 homeassistant kernel:  __alloc_pages_slowpath.constprop.0+0xb74/0xba0
Sep 02 07:49:05 homeassistant kernel:  __alloc_pages_nodemask+0x2a0/0x320
Sep 02 07:49:05 homeassistant kernel:  kmalloc_order+0x40/0xa0
Sep 02 07:49:05 homeassistant kernel:  kmalloc_order_trace+0x34/0x140
Sep 02 07:49:05 homeassistant kernel:  __kmalloc+0x3e4/0x440
Sep 02 07:49:05 homeassistant kernel:  __regset_get+0xa0/0x110
Sep 02 07:49:05 homeassistant kernel:  regset_get_alloc+0x1c/0x30
Sep 02 07:49:05 homeassistant kernel:  elf_core_dump+0x3f0/0xd60
Sep 02 07:49:05 homeassistant kernel:  do_coredump+0x5bc/0xfc0
Sep 02 07:49:05 homeassistant kernel:  get_signal+0x534/0x840

Is this work pursuing?

bdraco commented 3 years ago

I have the same revision on my test RPi3: Raspberry Pi 3 Model B Plus Rev 1.3

bdraco commented 3 years ago

Is this worth pursuing?

Yes, if you can get full debug logs turned on and captured up to the point where the crash happens it might help us figure out where

bdraco commented 3 years ago

Did any core.* files get written to the disk?

bdraco commented 3 years ago

It looks like its happening right after Sep 02 07:49:04 homeassistant a4773a23dc96[452]: 2021-09-02 07:49:04 INFO (MainThread) [homeassistant.setup] Setting up automation

Can you try moving away/renaming your automations.yaml file?

Edit: and creating an empty automations.yaml to allow startup to proceed normally

matphillips commented 3 years ago

no core files that I can find, only .journal files in that folder. I have the full file but it's over 800k, I can give you the full thing or try pastebin or something? automations.yaml caught my eye too. I can remove the file and put the SD back in the pi and see if it improves things. Will do that now.

matphillips commented 3 years ago

With automations gone, the system is booted, but into safe mode. This warning on the web page: 2021-09-02 09:08:31 ERROR (MainThread) [homeassistant.bootstrap] Failed to parse configuration.yaml: in "/config/configuration.yaml", line 10, column 13: Unable to read file /config/automations.yaml.. Activating safe mode

I guess I should have left a blank file there! Should I go ahead and remove the reference to the file in configuration.yaml, or is there anything useful I can do in this state to assist diagnosis? Thanks.

bdraco commented 3 years ago

Its good to know it starts up ok in safe mode.

Creating an empty automations.yaml should allow it to start back up normally. Sorry I didn't mention that in the original post.

matphillips commented 3 years ago

I should have expected it, but at least it's a diag step! Still cant ssh in, but can access the terminal from the web admin page "Terminal & SSH" (which does not work correctly in Safari, btw, text is invisible). I used that to create a blank automations.yaml file (quicker than removing the SD card again) and then used Configuration|Server Controls to check configuration validation, which passed, so I hit restart in Server Management to see if that would be enough.

System came online briefly (one of my esp nodes beeps when it reconnects, and it beeped) the web console also was showing messages about each module starting up and eventually the 'Started' message, but then it went boom right away with a 'connection lost...' message.

Then it repeats, I see the messages in the web console about services starting up, and then the connection lost message.

quorn23 commented 3 years ago

Tried it with an empty automations.yaml still restarting. If i try to trigger a core rebuild i get hit with a 404

`➜ ~ ha core rebuild Processing... Done.

Error: 404 Client Error for http+docker://localhost/v1.41/containers/create?name=homeassistant: Not Found ("No such image: ghcr.io/home-assistant/raspberrypi3-64-homeassistant:2021.9.0") `

Edit: seems like it has been pulled https://community.home-assistant.io/t/2021-9-0-more-energy-usb-discovery-template/334830/89

matphillips commented 3 years ago

Managed to catch the supervisor logs in the webpage for the brief moment that the system is responding: 

21-09-02 09:35:25 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2
21-09-02 09:35:25 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor
21-09-02 09:35:25 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface io.hass.os
21-09-02 09:35:26 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.systemd1
21-09-02 09:35:26 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.login1
21-09-02 09:35:26 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.hostname1
21-09-02 09:35:27 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.timedate1
21-09-02 09:35:27 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.NetworkManager
21-09-02 09:35:27 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface de.pengutronix.rauc
21-09-02 09:35:27 INFO (MainThread) [supervisor.host.info] Updating local host information
21-09-02 09:35:28 INFO (MainThread) [supervisor.host.services] Updating service information
21-09-02 09:35:28 INFO (MainThread) [supervisor.host.network] Updating local network information
21-09-02 09:35:30 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-09-02 09:35:30 INFO (MainThread) [supervisor.host.manager] Host information reload completed
21-09-02 09:35:30 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
21-09-02 09:35:30 INFO (MainThread) [supervisor.host.services] Reloading local service hassos-apparmor.service
21-09-02 09:35:31 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-dns with version 2021.06.0
21-09-02 09:35:31 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
21-09-02 09:35:31 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning hassio_dns application
21-09-02 09:35:34 INFO (SyncWorker_1) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/aarch64-hassio-dns with version 2021.06.0 - 172.30.32.3
21-09-02 09:35:34 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
21-09-02 09:35:34 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-audio with version 2021.07.0
21-09-02 09:35:34 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin
21-09-02 09:35:34 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning hassio_audio application
21-09-02 09:35:37 INFO (SyncWorker_0) [supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/aarch64-hassio-audio with version 2021.07.0 - 172.30.32.4
21-09-02 09:35:37 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-cli with version 2021.08.1
21-09-02 09:35:37 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
21-09-02 09:35:38 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning hassio_cli application
21-09-02 09:35:41 INFO (SyncWorker_1) [supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/aarch64-hassio-cli with version 2021.08.1 - 172.30.32.5
21-09-02 09:35:41 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-observer with version 2021.06.0
21-09-02 09:35:41 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-multicast with version 2021.04.0
21-09-02 09:35:41 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin
21-09-02 09:35:41 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning hassio_multicast application
21-09-02 09:35:44 INFO (SyncWorker_1) [supervisor.docker.multicast] Starting Multicast homeassistant/aarch64-hassio-multicast with version 2021.04.0 - Host
21-09-02 09:35:44 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-09-02 09:35:49 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/raspberrypi3-64-homeassistant with version 2021.9.0
21-09-02 09:35:49 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 1 Home Assistant secrets
21-09-02 09:35:49 INFO (MainThread) [supervisor.hassos] Detect Home Assistant Operating System 6.2 / BootSlot A
21-09-02 09:35:50 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_exclude' is deprecated, 'backup_exclude' should be used instead. Please report this to the maintainer of deCONZ
21-09-02 09:35:50 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_post' is deprecated, 'backup_post' should be used instead. Please report this to the maintainer of MariaDB
21-09-02 09:35:50 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_pre' is deprecated, 'backup_pre' should be used instead. Please report this to the maintainer of MariaDB
21-09-02 09:35:51 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot' is deprecated, 'backup' should be used instead. Please report this to the maintainer of UniFi Controller
21-09-02 09:35:52 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_exclude' is deprecated, 'backup_exclude' should be used instead. Please report this to the maintainer of AdGuard Home
21-09-02 09:35:52 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_exclude' is deprecated, 'backup_exclude' should be used instead. Please report this to the maintainer of ESPHome
21-09-02 09:35:52 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository
21-09-02 09:35:52 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository
21-09-02 09:35:55 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_exclude' is deprecated, 'backup_exclude' should be used instead. Please report this to the maintainer of deCONZ
21-09-02 09:35:55 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_post' is deprecated, 'backup_post' should be used instead. Please report this to the maintainer of MariaDB
21-09-02 09:35:55 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_pre' is deprecated, 'backup_pre' should be used instead. Please report this to the maintainer of MariaDB
21-09-02 09:35:56 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot' is deprecated, 'backup' should be used instead. Please report this to the maintainer of UniFi Controller
21-09-02 09:35:56 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_exclude' is deprecated, 'backup_exclude' should be used instead. Please report this to the maintainer of AdGuard Home
21-09-02 09:35:57 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_exclude' is deprecated, 'backup_exclude' should be used instead. Please report this to the maintainer of ESPHome
21-09-02 09:35:57 INFO (MainThread) [supervisor.store] Loading add-ons from store: 63 all - 63 new - 0 remove
21-09-02 09:35:57 INFO (MainThread) [supervisor.addons] Found 9 installed add-ons
21-09-02 09:35:57 INFO (SyncWorker_3) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-configurator with version 5.3.3
21-09-02 09:35:57 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to esphome/esphome-hassio-aarch64 with version 2021.8.2
21-09-02 09:35:57 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/log-viewer/aarch64 with version 0.11.1
21-09-02 09:35:57 INFO (SyncWorker_5) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-mosquitto with version 6.0.1
21-09-02 09:35:57 INFO (SyncWorker_6) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-ssh with version 9.1.3
21-09-02 09:35:57 INFO (SyncWorker_4) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/portainer/aarch64 with version 1.5.1
21-09-02 09:35:57 INFO (SyncWorker_2) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-check_config with version 3.8.0
21-09-02 09:35:57 INFO (SyncWorker_7) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/node-red/aarch64 with version 9.2.1
21-09-02 09:35:57 INFO (SyncWorker_3) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-samba with version 9.5.1
21-09-02 09:35:57 INFO (MainThread) [supervisor.backups.manager] Found 8 backup files
21-09-02 09:35:57 INFO (MainThread) [supervisor.discovery] Loaded 1 messages
21-09-02 09:35:57 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions
21-09-02 09:35:57 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.SETUP
21-09-02 09:35:57 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-09-02 09:35:57 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
21-09-02 09:35:58 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-02 09:35:58 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - CoreState.SETUP
21-09-02 09:35:58 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
21-09-02 09:35:58 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-02 09:35:58 INFO (MainThread) [__main__] Running Supervisor
21-09-02 09:35:58 INFO (MainThread) [supervisor.hassos] Rauc: A - marked slot kernel.0 as good
21-09-02 09:35:58 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
21-09-02 09:35:58 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 1 add-ons
21-09-02 09:35:59 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_core_mosquitto application
21-09-02 09:36:02 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-mosquitto with version 6.0.1
21-09-02 09:36:07 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' starting 1 add-ons
21-09-02 09:36:07 INFO (SyncWorker_6) [supervisor.docker.interface] Cleaning addon_core_ssh application
21-09-02 09:36:11 INFO (SyncWorker_6) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-ssh with version 9.1.3
21-09-02 09:36:13 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
21-09-02 09:36:17 INFO (MainThread) [supervisor.core] Start Home Assistant Core
21-09-02 09:36:17 INFO (SyncWorker_7) [supervisor.docker.interface] Starting homeassistant
21-09-02 09:36:17 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-09-02 09:36:42 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.STARTUP
21-09-02 09:36:42 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-02 09:36:52 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-09-02 09:37:23 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.STARTUP
21-09-02 09:37:23 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-02 09:37:57 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.STARTUP
21-09-02 09:37:57 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-02 09:38:29 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.STARTUP
21-09-02 09:38:29 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-09-02 09:38:58 ERROR (MainThread) [supervisor.homeassistant.api] Error on call http://172.30.32.1:8123/api/config: Server disconnected
cogneato commented 3 years ago

Here's dmesg output which I attempted to capture between restarts of HA Core dmesg.txt

blubbel42 commented 3 years ago

Maybe it is of any use: I run Home Assistant on a RPi 3B, did the upgrade and it runs fine.

Came up fine on the first try, did some reboots since then to adapt a few sensor things. My Install contains a bunch of custom_integrations as well

balloob commented 3 years ago

For people experiencing crashes, please let us know:

Bert-R commented 3 years ago

I was facing continuous Core restarts on a Raspberry Pi 3B+ with 1GB RAM, 64-bit. Now I've reverted to 2021.8.8

freddieleeman commented 3 years ago

Same issue on a Hardkernel ODROID-C2 (4 x ARM Cortex-A53 1.5GHz 64bit ARMv8 Architecture with 2Gbyte DDR3 SDRAM)

aktim24459 commented 3 years ago

Same issue here on 2 hardkernel ODROID-C2 systems

Masteroshi430 commented 3 years ago

Raspberry Pi 3B with 1GB RAM, 64-bit. I've now reverted to 2021.8.8, everything is fine.

javmorin commented 3 years ago

@ludeeus is there a pointer/instructions you can provide here for how to get this onto a raspberry pi that is stuck looping? I am running on HAOS.

ludeeus commented 3 years ago

Join the discord server

jasonbouknight commented 3 years ago

How does this bug escape regression testing?

balloob commented 3 years ago

@jasonbouknight because you didn't test it on a Raspberry Pi 3 running 64-bit Hass OS with 1GB of RAM. Pleas do better for the next release.

agners commented 3 years ago

How does this bug escape regression testing?

I think we were a bit unlucky here: Its very rare that something breaks that hard on only a few platforms. It seems that low memory/older ARM based platforms were affected. Devs which run nightly/betas usually run higher end setups, which were not affected.

Yes its true we don't run full stack tests on ~15+ platforms. We are waiting that somebody builds that test setup :wink:

Also it has been on beta channel, so it seems that nobody runs the setup using beta/cared to report...

Edit: Btw, it seems that this tracks back to a bug in stable Alpine (which is surprising to me given the popularity). So you might want to ask that question Alpine devs (hint: don't!)

dfederm commented 3 years ago

Yes its true we don't run full stack tests on ~15+ platforms. We are waiting that somebody builds that test setup 😉

I completely understand not being able to test every single platform. However, a Pi 3b+ seems super common and explicitly well-documented (Pi 4 is probably the "default" now, but tons of people like myself who got set up before the 4 was released exist) so would seem like it should be a primary scenario. Especially for OS setups, it seems like testing should be pretty thorough since those are the more "hands-off" users who expect things to just kinda work.

Based on this, I'd strongly recommend adding the Pi 3b+ in the testing. If its a funding issue, I'm such someone could donate or buy y'all a Pi 3b+ to test with. Actually setting up the device for automated testing is probably a little out of scope for an average user though and would need devs to assist with that.

An alternate but IMHO way less desirable path would be to remove language regarding the Pi 3b+ and perhaps even announce its degraded status in favor of the Pi 4 or other hardware. At least then users such as myself would know we're in a "supported but kinda legacy and not really recommended anymore" scenario.

araczkowski commented 3 years ago

users who expect things to just kinda work.

or never satisfied users who just expect top quality for free

I'm such someone could donate or buy y'all a Pi 3b+ to test with.

really.. wow - you far too kind... maybe I will send you my device to test?

BTW don't take this personally. I'm just 100% sympathizing with HA team :peace_symbol:

VictoriousCupid commented 3 years ago

@dfederm well set up a rpi 3 and join the beta channel... better yet, set up every version of rpi 3. and of course report back every detail.

balloob commented 3 years ago

Locking because this issue has been resolved. Thanks everyone for helping figuring out the cause. 2021.9.1 will be released shortly and include the fix.