search

sabeechen / hassio-google-drive-backup

Automatically create and sync Home Assistant backups into Google Drive
MIT License
3.12k stars 189 forks source link

Every backup is stored locally, filling up disk, while add-on says there are no local backup. #999

Closed napalmz closed 6 months ago

napalmz commented 7 months ago
Description:
Basically in the /backup folder remain every backup he did until disk is full. Files are name like "45f1f9ed.tar" and are not shown in the GUI, instead it says every backup is only present on cloud.
I've tried reinstalling add-on but this behavior remains the same. I've another install at work and it behaves correctly.

Addon version: 0.112.1 Home Assistant Version: 2024.2.5 Supervisor Version: 2024.02.0 Supervisor Channel: stable Hassos Version: 12.0 Docker Version: 24.0.7 Architecture: amd64 Machine: qemux86-64 Date: 2024-02-28T14:06:28.203176+00:00 Timezone: Europe/Rome Failure Time: 2024-02-27T11:35:42.684908+00:00 Last Good Sync: 2024-02-28T14:05:02.378624+00:00 Next Sync: 2024-02-28T16:21:36.269308+00:00 Next Backup: 2024-02-29T04:00:00+00:00 Next Cache Warm: 2024-02-28T16:18:51.641668+00:00 Time Offset: 0.0

Exception:
 No error could be identified automatically.

Backups:

 {
    "HomeAssistant": {
        "backups": 0,
        "retained": 0,
        "deletable": 0,
        "name": "HomeAssistant",
        "title": "Home Assistant",
        "latest": null,
        "max": 1,
        "enabled": true,
        "icon": "home-assistant",
        "ignored": 0,
        "detail": "",
        "size": "0.0 B",
        "ignored_size": "0.0 B",
        "free_space": "59.0 GB"
    },
    "GoogleDrive": {
        "backups": 30,
        "retained": 0,
        "deletable": 30,
        "name": "GoogleDrive",
        "title": "Google Drive",
        "latest": "2024-02-28T04:00:00Z",
        "max": 30,
        "enabled": true,
        "icon": "google-drive",
        "ignored": 0,
        "detail": "willy.baessato@gmail.com",
        "size": "506.2 GB",
        "ignored_size": "0.0 B",
        "free_space": "1.4 TB"
    }
}
Config:
 {
    "Setting.MAX_BACKUPS_IN_HA": 1,
    "Setting.MAX_BACKUPS_IN_GOOGLE_DRIVE": 30,
    "Setting.DAYS_BETWEEN_BACKUPS": 1.0,
    "Setting.IGNORE_OTHER_BACKUPS": true,
    "Setting.DELETE_IGNORED_AFTER_DAYS": 0.0006944444444444445,
    "Setting.BACKUP_TIME_OF_DAY": "05:00",
    "Setting.BACKUP_PASSWORD": "REDACTED",
    "Setting.SEND_ERROR_REPORTS": true,
    "Setting.MAXIMUM_UPLOAD_CHUNK_BYTES": 52428800.0
}
Addon Logs:
 02-28 05:43:18 DEBUG [backup.drive.driverequests] Sending 10 MB to Google Drive
02-28 05:43:19 DEBUG [backup.drive.drivesource] Uploading Full Backup 2024-02-28 05:00:00 99.85%
02-28 05:43:19 DEBUG [backup.drive.driverequests] Sending 10 MB to Google Drive
02-28 05:43:20 DEBUG [backup.drive.drivesource] Uploading Full Backup 2024-02-28 05:00:00 99.91%
02-28 05:43:20 DEBUG [backup.drive.driverequests] Sending 10 MB to Google Drive
02-28 05:43:21 DEBUG [backup.drive.drivesource] Uploading Full Backup 2024-02-28 05:00:00 99.97%
02-28 05:43:21 DEBUG [backup.drive.driverequests] Sending 5.53515625 MB to Google Drive
02-28 05:43:24 DEBUG [backup.drive.drivesource] Uploading Full Backup 2024-02-28 05:00:00 100.00%
02-28 05:43:25 INFO [backup.drive.drivesource] Deleting 'Full Backup 2024-01-29 05:00:00' From Google Drive
02-28 05:43:26 DEBUG [backup.watcher] Checking backup source for changes...
02-28 06:00:00 INFO [backup.watcher] A backup directory file was modified, we'll check for new backups soon.
02-28 06:00:10 DEBUG [backup.watcher] Checking backup source for changes...
02-28 07:56:52 INFO [backup.watcher] A backup directory file was modified, we'll check for new backups soon.
02-28 07:57:02 DEBUG [backup.watcher] Checking backup source for changes...
02-28 07:57:02 DEBUG [backup.model.syncer] Sync requested by Backup Directory Watcher
02-28 07:57:02 INFO [backup.model.coordinator] Syncing Backups
02-28 07:57:02 DEBUG [backup.drive.driverequests] Requesting refreshed Google Drive credentials
02-28 10:11:25 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand
02-28 10:11:25 DEBUG [backup.drive.driverequests] Requesting refreshed Google Drive credentials
02-28 10:20:49 DEBUG [backup.model.syncer] Sync requested by Coordinator
02-28 10:20:49 INFO [backup.model.coordinator] Syncing Backups
02-28 12:23:27 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand
02-28 12:23:27 DEBUG [backup.drive.driverequests] Requesting refreshed Google Drive credentials
02-28 12:30:11 DEBUG [backup.model.syncer] Sync requested by Coordinator
02-28 12:30:11 INFO [backup.model.coordinator] Syncing Backups
02-28 14:09:29 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand
02-28 14:09:29 DEBUG [backup.drive.driverequests] Requesting refreshed Google Drive credentials
02-28 14:17:15 DEBUG [backup.model.syncer] Sync requested by Coordinator
02-28 14:17:15 INFO [backup.model.coordinator] Syncing Backups
02-28 15:05:02 INFO [backup.model.coordinator] Syncing Backups
Supervisor Logs:
 24-02-28 14:51:38 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-02-28 14:51:38 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
24-02-28 14:51:38 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
24-02-28 14:53:41 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with ccab4aaf_frigate-proxy application!
24-02-28 14:53:41 INFO (SyncWorker_0) [supervisor.docker.manager] Stopping addon_ccab4aaf_frigate-proxy application
24-02-28 14:53:41 INFO (SyncWorker_0) [supervisor.docker.manager] Cleaning addon_ccab4aaf_frigate-proxy application
24-02-28 14:53:41 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ccab4aaf/amd64-addon-frigate-proxy with version 1.4
24-02-28 14:53:46 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url=URL('http://172.30.33.10:5000/ws')
24-02-28 14:53:53 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url=URL('http://172.30.33.10:5000/ws')
24-02-28 14:53:58 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url=URL('http://172.30.33.10:5000/ws')
24-02-28 14:54:04 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url=URL('http://172.30.33.10:5000/ws')
24-02-28 14:54:09 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 502, message='Invalid response status', url=URL('http://172.30.33.10:5000/ws')
24-02-28 14:54:32 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to STARTING
24-02-28 14:54:47 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNING
24-02-28 14:54:47 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
24-02-28 14:54:47 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2024.2.5
24-02-28 14:54:47 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
24-02-28 14:54:47 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
24-02-28 14:54:47 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
24-02-28 14:54:47 INFO (SyncWorker_10) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/qemux86-64-homeassistant:2024.2.4']
24-02-28 14:55:03 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
24-02-28 14:56:56 WARNING (MainThread) [supervisor.api.ingress] No valid ingress session None
24-02-28 15:03:26 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from cebe7a76_hassio_google_drive_backup
24-02-28 15:03:26 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
24-02-28 15:03:26 INFO (MainThread) [supervisor.api.middleware.security] /mounts access from cebe7a76_hassio_google_drive_backup
24-02-28 15:03:26 INFO (MainThread) [supervisor.api.middleware.security] /addons access from cebe7a76_hassio_google_drive_backup
24-02-28 15:05:02 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup
24-02-28 15:05:02 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup
24-02-28 15:06:28 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/logs access from cebe7a76_hassio_google_drive_backup
Home Assistant Core Logs:
 2024-02-28 15:06:17.004 WARNING (MainThread) [homeassistant.components.sensor] Updating snmp sensor took longer than the scheduled update interval 0:00:10
bash: line 1: sensors: command not found
2024-02-28 15:06:17.126 ERROR (SyncWorker_8) [homeassistant.components.command_line.utils] Command failed (with return code 127): ssh -i /config/keys/ansible_rsa -o StrictHostKeyChecking=no -q napalmz@10.0.0.246 sensors -jA
2024-02-28 15:06:17.127 WARNING (MainThread) [homeassistant.components.command_line] Empty reply found when expecting JSON data
2024-02-28 15:06:18.999 WARNING (MainThread) [homeassistant.components.command_line] Updating Command Line Sensor OrangePi took longer than the scheduled update interval 0:00:01
bash: line 1: sensors: command not found
2024-02-28 15:06:19.244 ERROR (SyncWorker_4) [homeassistant.components.command_line.utils] Command failed (with return code 127): ssh -i /config/keys/ansible_rsa -o StrictHostKeyChecking=no -q napalmz@10.0.0.246 sensors -jA
2024-02-28 15:06:19.246 WARNING (MainThread) [homeassistant.components.command_line] Empty reply found when expecting JSON data
2024-02-28 15:06:21.001 WARNING (MainThread) [homeassistant.components.command_line] Updating Command Line Sensor OrangePi took longer than the scheduled update interval 0:00:01
bash: line 1: sensors: command not found
2024-02-28 15:06:21.230 ERROR (SyncWorker_39) [homeassistant.components.command_line.utils] Command failed (with return code 127): ssh -i /config/keys/ansible_rsa -o StrictHostKeyChecking=no -q napalmz@10.0.0.246 sensors -jA
2024-02-28 15:06:21.231 WARNING (MainThread) [homeassistant.components.command_line] Empty reply found when expecting JSON data
2024-02-28 15:06:23.003 WARNING (MainThread) [homeassistant.components.command_line] Updating Command Line Sensor OrangePi took longer than the scheduled update interval 0:00:01
2024-02-28 15:06:23.054 INFO (MainThread) [habluetooth.base_scanner] esp-002 (C8:C9:A3:F9:33:FC): Bluetooth scanner has gone quiet for 90s, check logs on the scanner device for more information
2024-02-28 15:06:23.056 INFO (MainThread) [habluetooth.base_scanner] esp-006 (84:F7:03:0B:DB:FC): Bluetooth scanner has gone quiet for 90s, check logs on the scanner device for more information
2024-02-28 15:06:23.075 INFO (MainThread) [habluetooth.base_scanner] esp-007 (08:3A:F2:52:36:00): Bluetooth scanner has gone quiet for 90s, check logs on the scanner device for more information
bash: line 1: sensors: command not found
2024-02-28 15:06:23.259 ERROR (SyncWorker_18) [homeassistant.components.command_line.utils] Command failed (with return code 127): ssh -i /config/keys/ansible_rsa -o StrictHostKeyChecking=no -q napalmz@10.0.0.246 sensors -jA
2024-02-28 15:06:23.260 WARNING (MainThread) [homeassistant.components.command_line] Empty reply found when expecting JSON data
2024-02-28 15:06:24.282 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor double-take ingresso, sending update
2024-02-28 15:06:25.004 WARNING (MainThread) [homeassistant.components.command_line] Updating Command Line Sensor OrangePi took longer than the scheduled update interval 0:00:01
bash: line 1: sensors: command not found
2024-02-28 15:06:25.191 ERROR (SyncWorker_52) [homeassistant.components.command_line.utils] Command failed (with return code 127): ssh -i /config/keys/ansible_rsa -o StrictHostKeyChecking=no -q napalmz@10.0.0.246 sensors -jA
2024-02-28 15:06:25.191 WARNING (MainThread) [homeassistant.components.command_line] Empty reply found when expecting JSON data
2024-02-28 15:06:27.005 WARNING (MainThread) [homeassistant.components.command_line] Updating Command Line Sensor OrangePi took longer than the scheduled update interval 0:00:01
bash: line 1: sensors: command not found
2024-02-28 15:06:27.131 ERROR (SyncWorker_62) [homeassistant.components.command_line.utils] Command failed (with return code 127): ssh -i /config/keys/ansible_rsa -o StrictHostKeyChecking=no -q napalmz@10.0.0.246 sensors -jA
2024-02-28 15:06:27.133 WARNING (MainThread) [homeassistant.components.command_line] Empty reply found when expecting JSON data
2024-02-28 15:06:27.734 INFO (MainThread) [homeassistant.components.nmap_tracker] No MAC address found for 10.0.0.249
Images:

image image

roblandry commented 6 months ago

I've been affected with the same issue. If I recall correctly it started around January. I'm wondering if it's ingress related as I cannot see debug logs and get no valid ingress session when trying.

napalmz commented 6 months ago

Eventually, after reinstalling the plugin again, it resumed naming the backups correctly and considering them, without filling the disk anymore. I don't know if this was due to the reinstallation or something else, though. In any case, everything is okay now.

nkm8 commented 6 months ago

I had this issue and fixed it by manually deleting the old backup files. I'm not sure what the cause is, but I suggest leaving the issue open until it is fixed.