Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Snapshot.stale errors in log
See original GitHub issueI’m on Hass.io, the latest version using this addon 0.99.0 and am using lets encrypt ssl certificates. I get the following errors in the hass.io system log at reboot:
19-11-25 11:02:01 ERROR (MainThread) [hassio.homeassistant] Error on call https://172.30.32.1:8123/api/states/binary_sensor.snapshots_stale: Cannot connect to host 172.30.32.1:8123 ssl:None [Connection refused]
19-11-25 11:02:01 ERROR (MainThread) [hassio.api.proxy] Error on API for request states/binary_sensor.snapshots_stale
I’ve tried enabling and disabling ssl in the config of this addin, no change in the log.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Cluster goes down with snapshot and stale file handle errors
Problem. Your cluster is unstable where vemkd keeps exiting. In the Primary host's lim log you see errors like the following.
Read more >Break Fix: Clearing stale or orphaned Microsoft VSS snapshots
Snapshots are failing due to a space constraint on the protected asset. This may be a result of stale or orphaned snapshots, often...
Read more >Snapshots display Stale NFS file handle message
Issue. When a volume is mounted via Network File System (NFS), the first snapshot is taken without issue. However, when the snapshot is ......
Read more >Inconsistent or stale NetBackup snapshot catalog image for ...
NetBackup operations performed on a catalog image fail as there is no snapshot associated with that image. The following is a list of...
Read more >1344729 - Stale file handles in /mnt/l10n_shared/.snapshot
.snapshot is a magical directory in NetApp that shows snapshots of the NFS datastore. When snapshots go away / age off, they're removed...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The addon doesn’t communicate with Home Assistant over the network, it uses a proxy that Hass.io provides. The detalils of how this works are here. The error you’re seeing:
Means that Hass.io is unable to communicate with Home Assistant on behalf of the addon. Normally this is because Home Assistant is restarting or just booting up and can be ignored. Hass.io doesn’t expose a way for my addon to check to see if Home Assistant is running or not, so the only way to see if its available is to send a request, which will cause this error to be displayed when it is down.
The reason the addon attempts to contact Home Assistant at all is to publish the staleness sensor and send notifications if backup fails. If you want to get rid of this error message, entirely, the only way is to disable those sensors
Sounds good, let me know if something doesn’t look right.