Permanent thaw-freeze-sessions

How can I get rid of this:

2026-03-18 14:26:34.882 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage home_assistant
2026-03-18 14:26:58.157 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage addons
2026-03-18 14:27:04.928 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage home_assistant
2026-03-18 14:27:04.931 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage addons
2026-03-18 14:27:26.314 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage home_assistant
2026-03-18 14:27:48.489 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage addons
2026-03-18 14:27:51.574 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage home_assistant
2026-03-18 14:27:51.576 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage addons
2026-03-18 14:28:15.796 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage home_assistant
2026-03-18 14:28:38.290 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage addons
2026-03-18 14:28:39.932 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/logs/follow access from a0d7b954_ssh
2026-03-18 14:28:44.329 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage home_assistant
2026-03-18 14:28:44.346 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage addons
[...]
2026-03-18 14:42:14.396 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage home_assistant
2026-03-18 14:42:40.259 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage addons
2026-03-18 14:42:44.602 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage home_assistant
2026-03-18 14:42:44.604 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage addons
2026-03-18 14:43:05.592 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage home_assistant
2026-03-18 14:43:30.535 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage addons
2026-03-18 14:43:37.643 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage home_assistant
2026-03-18 14:43:37.645 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage addons
2026-03-18 14:43:45.434 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2026-03-18 14:44:02.431 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage home_assistant
2026-03-18 14:44:26.767 INFO (MainThread) [supervisor.backups.manager] Freeze starting stage addons
2026-03-18 14:44:33.252 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage home_assistant
2026-03-18 14:44:33.254 INFO (MainThread) [supervisor.backups.manager] Thaw starting stage addons
[...]

What I have done so far:

  1. Deactivated Backup
  2. Restarted Homeassistant
  3. Restarted Supervisor

What is causing those freezes every ~15 minutes and how do I get rid of it?

I’m thinking there’s still a slow backup running. Shutting backups off might not stop a currently running one, not sure.
Boot into safe mode and see what it does.

Is this a VM? Are you replicating/snapshotting it or backing it up?

How do I see what it does in safe mode?
What can I see in safe mode that I cannot see right now?

Yes, it’s a vm on Proxmox.
But why would it cause HA to freeze/thaw? And what does the backup manage have to do with it?

Edit: Looks like it is indeed triggered by the replication. But why does it do that? How can I prevent that?

It’s triggered by qemu’s fsfreeze and makes sure your snapshots/backups are consistent. You want that to happen. What’s your issue with it?

The problem: It apparently causes the system to, well, stop for a moment - which subsequently causes issues.
Actually: I run the database externally, so I do not see any harm in haveing not 100% consistent data (if this would even really happen).

If you are running the db externally you could try disabling the qemu agent:

1 Like

Replication is using zfs snapshots. In order to take a snapshot you have to freeze the underlying VM. How frequently are you replicating? I’m using every 2 hours on my home assistant production server and don’t have this issue.

I have 3 nodes to replicate to and I was hoping that more frequent replications would have a lower impact because there is less to transfer.
But that is apparently not true because I didn’t expect the whole machine to freeze (ever so briefly) because of this.

I will indeed try to disable the qemu-agent in the hope that this solves my issue without creating new problems.

Edit: Disabling qemu-agent seems to do the trick, @fleskefjes - thank you!

1 Like

Late getting back, but safe mode leaves it running with only core stuff, so if it’s something external it should stop and you know to look at the custom or app stuff. If it continues you look at core stuff. Splits your problem in half, helps guide you.

Summary:

Disabling qemu-agent seems to do the trick.
The freeze-thaw spam is completely gone.

I do not see any negative side effects.

Thank you every for you really helpful replies. Much appreciated!