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/reload when Storage for Backups is defined #122110

Closed
donburch888 opened this issue Jul 18, 2024 · 21 comments
Closed

Failed to to call /backups/reload when Storage for Backups is defined #122110

donburch888 opened this issue Jul 18, 2024 · 21 comments

Comments

@donburch888
Copy link

donburch888 commented Jul 18, 2024

The problem

When "Storage" is configured for Backup (using CIFS protocol), the Backups page shows "You don't have any backups yet." whether I use local data disk or the Storage
image

and generates errors in the Home Assistant Core log:

Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:615
integration: Home Assistant Supervisor (documentation, issues)
First occurred: 10:51:49 am (9 occurrences)
Last logged: 11:28:19 am

Timeout on /backups/reload request
Timeout on /backups request
Timeout on /host/info request
Timeout on /addons request

and

Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:135
integration: Home Assistant Supervisor (documentation, issues)
First occurred: 10:51:49 am (9 occurrences)
Last logged: 11:28:19 am

Failed to to call /backups/reload -
Failed to to call /backups -
Failed to to call /host/info -
Failed to to call /addons -

If I delete the Storage entry for Backup, the problem is resolved.
image

What version of Home Assistant Core has the issue?

core-2024.7.2

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

No response

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

@jsco2t
Copy link

jsco2t commented Jul 18, 2024

Having a similar issue. Backups are being created - but the listing for backups does not show-up. In my case I have backups being stored on a samba/network share. I have verified the backups are created (by looking at the network share). However I cannot list them in the HA backup web UI.

Reported error in log was:

Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:615
integration: Home Assistant Supervisor ([documentation](https://www.home-assistant.io/integrations/hassio), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+hassio%22))
First occurred: 11:08:11 AM (7 occurrences)
Last logged: 11:11:44 AM

    Timeout on /backups/reload request
    Timeout on /host/info request
    Timeout on /backups request

@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)

@mazzy89
Copy link
Contributor

mazzy89 commented Aug 3, 2024

Same here. I cannot anymore list backups

@xmattex73
Copy link

Same here. only for network device. Local Backups are running and display

@boinjoe
Copy link

boinjoe commented Aug 25, 2024

same at my HA. No backup will be listed.
Failure in protokoll:
Failed to to call /backups/reload -
Failed to to call /host/info -
Failed to to call /backups -
Failed to to call /addons -

@NordFreak
Copy link

I also have this problem and it can be reproduced. If there are few backups on my NAS, it can load them. If there are significantly more than 10 available, nothing is displayed. As in the screenshot from the creator.

@bronkoo
Copy link

bronkoo commented Oct 17, 2024

Exactly the same here, backups created on cifs storage server but not listed...

Core 2024.10.2
Supervisor 2024.10.2
Operating System
Frontend 20241002.3

(enhanced)
`Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:135
integration: Home Assistant Supervisor (documentation, issues)
First occurred: October 31, 2024 at 4:59:22 PM (10 occurrences)
Last logged: 8:56:38 PM

Failed to to call /backups/reload -
Failed to to call /host/info -
Failed to to call /backups -
Failed to to call /addons -`

@uneart
Copy link

uneart commented Nov 3, 2024

Same issues here, also with CIFS network storage on a NAS.

Logger: homeassistant.components.hassio
Quelle: components/hassio/websocket_api.py:135
Integration: Home Assistant Supervisor ([Dokumentation](https://www.home-assistant.io/integrations/hassio), [Probleme](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+hassio%22))
Erstmals aufgetreten: 10:33:25 (67 Vorkommnisse)
Zuletzt protokolliert: 10:45:52

Failed to to call /addons -
Failed to to call /backups/reload -
Failed to to call /backups -
Failed to to call /host/info -
Failed to to call /network/info -

System info

  • Core 2024.10.4
  • Supervisor 2024.10.3
  • Operating System 13.2
  • Frontend 20241002.4

@bronkoo
Copy link

bronkoo commented Nov 3, 2024

I would like to escalate, given to the fact, on productive setups backup storage will be on network storages, like cifs.

@NordFreak
Copy link

I would like to escalate, given to the fact, on productive setups backup storage will be on network storages, like cifs.

It's annoying, that's correct. But escalate? The basic function is there, the backup works.

It's just that when restoring, you have to take the detour and get the file from the storage location and upload it via WebUI during the restore.

And in a productive environment, you don't usually do that many restores ;-)

@bronkoo
Copy link

bronkoo commented Nov 5, 2024

It's just that when restoring, you have to take the detour and get the file from the storage location and upload it via WebUI during the restore.

For sure, but the idea of HA backup workflow is broken... no more, but no less either.

@noah-be
Copy link

noah-be commented Nov 7, 2024

Same issue with FritzNAS. The backup tab becomes unusable if there are more than a few backups in the folder.

@Cust0mC0d3z
Copy link

Some issue (since months) on my SMB share on my QNAP NAS. Backups are being created, but the list is not loading - even after hours of waiting.

@johnbubak
Copy link

Same here.
Ple help us

@bronkoo
Copy link

bronkoo commented Dec 14, 2024

It seems we have to go with this issue into the next year too...

Core 2024.12.3
Supervisor 2024.11.4
Operating System
Frontend 20241127.8

@IGNWoudenberg
Copy link

We do got a new screen that is loading forever and i’m missing the three little dots for reloading in the upper right corner.
IMG_0807

@bronkoo
Copy link

bronkoo commented Dec 14, 2024

Same here, and because of the dots missing it it's no more possible to change backup target here...

@IGNWoudenberg
Copy link

Same here, and because of the dots missing it it's no more possible to change backup target here...

Indeed, perhaps one more reason to deep dive on this for the team. Of perhaps better open a new issue?

@bronkoo
Copy link

bronkoo commented Dec 14, 2024

Of perhaps better open a new issue?

yes, we should...

@IGNWoudenberg
Copy link

Of perhaps better open a new issue?

yes, we should...

Created #133350

@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