Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to to call /backups/new/full - An error occurred while making backup #133038

Closed
Revilo91 opened this issue Dec 12, 2024 · 13 comments
Closed

Comments

@Revilo91
Copy link

The problem

The following error message appears in my logs when I start a backup:

2024-12-12 13:19:51.607 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /backups/new/full - An error occurred while making backup, check job '7bbb366934e54d89b6656f7ceb507102' or supervisor logs for details

Restarting doesn't help.

Backup was created under "Create backup" -> "Full backup" (without password protection). A drive path is used to store the backups.

What version of Home Assistant Core has the issue?

core-2024.12.2

What was the last working version of Home Assistant Core?

core-2024.1x.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Backup

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration (hassio) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of hassio can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign hassio Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


hassio documentation
hassio source
(message by IssueLinks)

@wepster
Copy link

wepster commented Dec 12, 2024

Same problem here

@Neelixx
Copy link

Neelixx commented Dec 12, 2024

Same problem: backup doesn't work since update to core 2024.12.2

@agners
Copy link
Member

agners commented Dec 12, 2024

Hm, works for me with Core 2024.12.2 and Supervisor 2024.11.4. Are you on the beta channel? Can you share the Supervisor logs?

@Revilo91
Copy link
Author

Sure, i'm in beta channel.

here is a partial supervisor log:

2024-12-12 13:11:49.400 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqtt'
2024-12-12 13:11:49.848 INFO (MainThread) [supervisor.auth] Successful login for 'mqtt'
2024-12-12 13:19:09.671 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-12-12 13:19:09.761 INFO (MainThread) [supervisor.backups.manager] Found 9 backup files
2024-12-12 13:19:09.832 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/mounts/Backup/1ee0a25f.tar: "filename './backup.json' not found"
2024-12-12 13:19:11.269 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/mounts/Backup/b662b5ed.tar: "filename './backup.json' not found"
2024-12-12 13:19:11.534 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/mounts/Backup/68fcb0f7.tar: "filename './backup.json' not found"
2024-12-12 13:19:20.951 INFO (MainThread) [supervisor.backups.manager] Backup 8906b37f starting stage addon_repositories
2024-12-12 13:19:20.951 INFO (MainThread) [supervisor.backups.manager] Backup 8906b37f starting stage docker_config
2024-12-12 13:19:20.951 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug 8906b37f
2024-12-12 13:19:21.389 INFO (MainThread) [supervisor.backups.manager] Backup 8906b37f starting stage home_assistant
2024-12-12 13:19:51.409 ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.
2024-12-12 13:27:18.379 INFO (MainThread) [supervisor.backups.manager] Found 10 backup files
2024-12-12 13:27:18.412 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/backup/8906b37f.tar: "filename './backup.json' not found"
2024-12-12 13:27:18.438 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/mounts/Backup/1ee0a25f.tar: "filename './backup.json' not found"
2024-12-12 13:27:19.051 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/mounts/Backup/68fcb0f7.tar: "filename './backup.json' not found"
2024-12-12 13:27:19.069 ERROR (MainThread) [supervisor.backups.backup] Can't read backup tarfile /data/mounts/Backup/b662b5ed.tar: "filename './backup.json' not found"
2024-12-12 13:29:05.695 INFO (MainThread) [supervisor.backups.manager] Backup edab444a starting stage addon_repositories
2024-12-12 13:29:05.695 INFO (MainThread) [supervisor.backups.manager] Backup edab444a starting stage docker_config
2024-12-12 13:29:05.696 INFO (MainThread) [supervisor.backups.manager] Creating new full backup with slug edab444a
2024-12-12 13:29:05.722 INFO (MainThread) [supervisor.backups.manager] Backup edab444a starting stage home_assistant
2024-12-12 13:29:35.738 ERROR (MainThread) [supervisor.homeassistant.module] Preparing backup of Home Assistant Core failed. Check HA Core logs.
2024-12-12 13:43:35.815 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2024-12-12 13:43:35.815 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2024-12-12 13:43:35.817 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2024-12-12 13:43:35.822 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server

@LinuxUnix80
Copy link

Same here

@wepster
Copy link

wepster commented Dec 13, 2024

Mine problem solved itself. Thanks to glances i saw there was python3 using a lot of cpu. I assume it was some kind of maintenance task, perkaps database purge or something. After some time cpu load dropped back to normal level and at this point i was able to create backup and for now it works fine

@yve1701
Copy link

yve1701 commented Dec 13, 2024

same here. But does not solved itself.

@RHAD1969
Copy link

RHAD1969 commented Dec 14, 2024

Mine problem solved itself. Thanks to glances i saw there was python3 using a lot of cpu. I assume it was some kind of maintenance task, perkaps database purge or something. After some time cpu load dropped back to normal level and at this point i was able to create backup and for now it works fine

Can you specify "some time" and "a lot of CPU"? I'm running against the same issue (30% CPU, 2 hours). The backup leaves a file 10.240 bytes large. I'm wandering if and how long I have to wait it out.

@wepster
Copy link

wepster commented Dec 14, 2024

It was about 40% cpu usage for at least hour and a half. But it was on HP T630 (so cpu is AMD GX-420G) . If you have different hardware it can be faster/slower.
i belive (correct me if im wrong) that this is some kind of retroactive process where HA calculates statistics and/or aggregates data for period of time between when backup was made (the one i was restoring from) and now.

@bluduk01
Copy link

I too am experiencing this issue. I just updated to 2024.12.3 and it had made no change. I can make a partial backup and select everything but core and the backup will complete smoothly. It seems when I attempt to backup core only or a full backup is when I get the error.

I am running in VMware.

@bluduk01
Copy link

Just an update. I stopped core via SSH and deleted the database. Backups were once again possible however not an ideal sittuation.

#126579 (comment)

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants