HA locks up every Sunday

Installation
1

Hi all

Firstly, apologies if this has been covered already.

Every Sunday night (between midnight and 1am) my HAOS hangs up. Ive tried connecting a vdu to my Pi3b but nothing displays. The only thing i can do is unplug it and plug it back in again to restart the Pi. This has been happening every Sunday since i installed HA (prob coming up 2 months). Ive wiped the sd card and done a clean install but it hasnt helped. Im very new to HA and have no idea whats causing it. The only thing i found in the Host log around the time of the crash last night was:

21:48:50 homeassistant systemd[1]: started notify NFS peers of a restart

00:15:52 homeassistant systemd-resolved[442]: clock change detected, flushing caches

01:22:23 homeassistant systemd-time-wait-sync[534]: adjtime state 5 status 40 time Mon 2025-03-03 00:15:52.338415 UTC

The last log at 01:22:23 is when I restarted the Pi.

Im using a 64gb Sandisk Ultra miniSD if it helps.

Any advice would be greatly appreciated.

2

Do you have a backup set to run at that time? Perhaps pi runs out of ram. pi3 is veeery underpowered for modern HA, at least Pi4 is desirable, even better pi5 or (best choice, cheaper than new pi5) used miniPC/ intel nuc or similar. And at minimum 2GB of ram, better 4GB (more doesn’t hurt, or course).

1 Like
3

Ive nothing set to run at that time. Since the clean install ive kept it barebones. Only automation i have is for a motion sensor controlled light.

4

Only thing that runs on Sunday is the auto repack of the db.

Even then, it only runs once every two weeks and only after the auto_purge completes after 4:12am, so the times don’t line up.

Can you run the recorder.purge with repack turned on to see if you can reproduce this issue manually?

5

Im new to this, how do i do that? :rofl:

6

Don’t worry, We’ve all been new to this at some point.

First things first, make sure you have a backup saved off the Pi. You can download it to your PC by clicking the 3 dots next to the backup > Download.
Nothing should break catastrophically, but this way you’re covered.

Next, go to Developer Tools and type in recorder. You should get an option as per below. Make sure the repack options is both ticked on the left and also has the switch toggled on the right, as per below.

image
image2075Ă—735 47 KB

Click “Perform Action” at the bottom and monitor your system to see if the same thing happens.

1 Like
7

So i did as you said. The “apply filter” was checked but the slide wasnt on, everything else was as you explained. Clicked perform action and got a green tick for about 1 second and that was it.

8

Forgot it’s Monday today, sorry. There might not be much to repack if it just ran yesterday.

Maybe give it a few days and try again?

9

Ive ordered a pi4 4gb and will try that as @Protoncek suggested incase it is a memory issue.

Thank you both for your help, i really appreciate it.

Ill still try the repack in a few days just to rule it out.

10

FYI you can monitor the memory use (and other important system resources) with this:

After a crash, restart and have a look a the CPU and memory use history graphs. Did either of them go nuts right before your crash?

Also the file /config/home-assistant.log.1 contains the system log from before the last restart. You can open this with a text editor. It may reveal problems that occurred before the crash.

1 Like
11

Thanks for this info, ill take a look at them in the morning and see if it reveals anything