Core update failed...july is rolling back

Good morning!

Since my first install last year, never been able to core update easily. For 06-1 I was able to update in safe mode+CLI. However, july update always roll back. How can I check what is going on, maybe a plugin or integration is blocking it?

What log and and to access it?

thanks!!

How much free space do you have on your system? Also, what system (hardware specs) are you running?

42% used storage out of 32GB

Ok so that’s not it. Care to answer my other question?

Also, can you see anything in the core logs?

Sure, I run a RASPi4 1G with Zigbee USB stick AMber ready Model 07
CORE log seems to be reset after roll back

2024-07-05 17:06:58.728 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-07-05 17:06:58.735 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-07-05 17:06:58.743 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dwains_dashboard which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-07-05 17:07:00.390 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly

2024-07-05 17:07:00.624 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=84 from 2024-07-05 15:48:49.928584)

2024-07-05 17:07:10.822 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration ‘hacs’ accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at Issues · hacs/integration · GitHub

2024-07-05 17:07:14.804 WARNING (MainThread) [alexapy.helpers] alexaapi.get_devices((<alexapy.alexalogin.AlexaLogin object at 0x7f8feac650>,), {}): A connection error occurred: An exception of type KeyError occurred. Arguments:

(‘[email protected]’,)

2024-07-05 17:07:14.817 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API:

2024-07-05 17:07:25.419 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration ‘hacs’ accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at Issues · hacs/integration · GitHub

And is moved to home-assistant.log.1, so that will tell you more.

1 Like

content of home-assistant.log.1
2024-07-05 19:40:05.989 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if>
2024-07-05 19:40:05.997 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you ex>
2024-07-05 19:40:06.005 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dwains_dashboard which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable >
2024-07-05 19:40:07.715 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2024-07-05 19:40:08.206 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=86 from 2024-07-05 21:41:04.785733)
2024-07-05 19:40:18.099 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration ‘hacs’ accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should b>
2024-07-05 19:40:22.290 WARNING (MainThread) [alexapy.helpers] alexaapi.get_devices((<alexapy.alexalogin.AlexaLogin object at 0x7f7041ae70>,), {}): A connection error occurred: An exception of type KeyError occurred. Arguments:
(‘[email protected]’,)
2024-07-05 19:40:22.374 ERROR (MainThread) [custom_components.alexa_media] Error fetching alexa_media data: Error communicating with API:
2024-07-05 19:40:35.030 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration ‘hacs’ accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be upd>
2024-07-05 19:40:50.149 WARNING (MainThread) [alexapy.helpers] alexaapi.get_devices((<alexapy.alexalogin.AlexaLogin object at 0x7f7041ae70>,), {}): A connection error occurred: An exception of type KeyError occurred.

Arguments:
(‘[email protected]’,)
2024-07-05 20:26:38.990 ERROR (MainThread) [homeassistant.components.ipp.coordinator] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server.

After several try i got this log:

Home Assistant Core

2024-07-05 21:51:41.295 WARNING (MainThread) [homeassistant.setup] Setup of hassio is taking over 10 seconds.

2024-07-05 21:51:41.966 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /core/info request

2024-07-05 21:51:41.968 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/info request

2024-07-05 21:51:41.969 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /info request

2024-07-05 21:51:41.969 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /host/info request

2024-07-05 21:51:41.970 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /resolution/info request

2024-07-05 21:51:41.970 ERROR (MainThread) [homeassistant.components.hassio.issues] Failed to update supervisor issues: HassioAPIError()

2024-07-05 21:51:41.974 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/options request

2024-07-05 21:51:41.975 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /ingress/panels request

2024-07-05 21:51:41.975 ERROR (MainThread) [homeassistant.components.hassio.addon_panel] Can’t read panel info:

2024-07-05 21:51:41.976 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /store request

2024-07-05 21:51:41.977 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /os/info request

2024-07-05 21:51:41.977 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /network/info request

2024-07-05 21:51:41.980 WARNING (MainThread) [homeassistant.components.hassio] Can’t read Supervisor data:

I haven tried several times to update even in safe mode and with CLI, last time log and log1 were empty. Is there another way to know what failed?

Hmm, 1G of RAM is abysmally low considering the number of custom integrations you’re running. You probably also have a few built in integrations too (zigbee at the very least, from what I can see). If you’re also running addons, the load is even higher.

My 4GB RAM installation with around 20 custom+built in integrations and 5 running addons hovers at around 27% usage when idling, so roughly over 1GB. This jumps up substantially during an update, so I hope you can see where I’m going with this…

Basically, everything seems to be pointing towards too much load for the hardware you’re using. When RAM gets full, it will start using SWAP (whatever is left of your already low 32GB storage). During an update, it will eat up all the RAM and SWAP you have available and run into issues.

I could suggest increasing the SWAP file size, but that’s gonna run you into 2 issues - you’ll have even less storage space available and you’re gonna wear out that poor SD card in no time.

You could also try debugging to see if the issue is being caused by an integration, but that means installing yet more integrations and ballooning the logs. It’ll probably make your problem worse.

My advice: given that you’ve been seeing problems with updates since day 1, things will only get worse for you in the future as you add more stuff. Just bite the bullet and get better hardware. Something with 4GB Ram and at least 64GB storage (ideally SSD) will be more than enough for the foreseeable future.
It doesn’t necessarily have to be a Pi - there’s plenty of threads here suggesting to buy a used small PC or old laptop if budget is an issue.

In the meantime, please make sure to store a local copy of your backups so you’ll have them handy when you want to restore after reinstallation.

(Apologies for the long post - I wanted to be as clear as possible)

1 Like

Thanks’ for the suggestions. I will investigate the memory and storage, maybe trying to disable integration.