Gladys Plus backups crash and hourly aggregation - 00:00/02:00

Configuration
, ,
1

Hi @pierre-gilles,

I’m following up on the update to 4.44 https://community.gladysassistant.com/t/gladys-assistant-4-44-une-alerte-quand-une-sauvegarde-echoue. After a manual retry, I did receive the alert, that’s great. Thanks. However, it really lacks information for errors…

  • first, at least knowing at which step it failed would be really great.
  • then having the start and end/failure times in the task tab would also be a big plus (and see the duration)
  • as well as the % completion if it fails.

I hadn’t noticed… but I’m in the same case, no backups for 3 months…

image
image714×490 14.9 KB

image
image704×840 59.3 KB

These two errors occur every day (backup and aggregation). Regarding the hourly aggregation, the others run fine; only the ones at 2 AM crash:
image
image562×666 5.85 KB

And I found the two files in the backup folder *.db.gz and *db.gz.enc at 11.4 GB.
And we can see last night they crashed at the same time, the backup after 40 minutes:
image
image966×296 14.4 KB

except that if I go back to previous days, this is no longer the case (so total coincidence?):

For that one I’m not surprised about this morning since the DB may have still been locked by the backup (it was in progress) but for the others… the DB crash happened before 2:00 AM.

On the hardware side:

  • Mini PC
  • before the backup file I’m at 16% of the SSD,
  • once the preparation copy is done I’m at 26%.
  • about 1 GB of RAM / 15.4 GB used during the backup (2nd step - Compression)
  • Processors: one at 100%, the others don’t move much but can sometimes be balanced
    image
    image
    image673×106 2.56 KB

When restarting manually, the first file at the end of the 1st phase is 41 GB (file .db). Then the compressed file rises to 11.4 GB (.db.gz) and right at that moment it crashes: the *.db file is deleted and a new file appears *.db.gz which also grows to 11.4 GB:

image
image1627×497 60.5 KB

image
image475×119 3.79 KB

But @pierre-gilles, haven’t I reached the limit you set?

image
image1152×211 24.6 KB

With no specific error, I have no idea how to solve this problem and for backups, it’s still very annoying as @GBoulvin said… Having no issues with space on my side or performance, I’m going back to manual backups, even if it’s very cumbersome.

Thanks in advance.

1 Like
2

Hi @Terdious :slight_smile:

If there’s a specific error, it’s a 400 Bad Request on the upload, which means the file to upload is too large.

The limit is at 8.5Gb right now, so at 11 Gb it’s normal for the upload to be refused.

Glad this new alert message showed us that — I was expecting to get feedback after yesterday’s release.

What I can offer is to temporarily increase the limit until we move to DuckDB, since after the migration the exports will be drastically reduced.

I’m saying temporarily, because at 11Gb of storage per backup I lose money, so it really shouldn’t last long :sweat_smile:

1 Like
3

@Terdious the backup seems to have worked last night :slight_smile:

4

Hi @pierre-gilles, sorry for the slow reply, very busy with work and house renovations.

Thank you very much, so that’s what I thought, but …

… no, that’s not an acceptable solution

We didn’t take Gladys Plus for you to be at a loss. We took it for a service that must be defined and to support the project. I refuse this solution which, for me, is not one. Not even temporarily.

1st solution, which in my opinion would be suitable, could you simply set up (temporarily or not) another Gladys Plus plan? Like €15 or €20 for larger storage?
2nd solution, I disable Gladys Plus until DuckDB arrives and I do manual backups.

5

Sorry but no this log message is not clear at all neither on the interface nor in the inspector. A 400 error, okay, but it’s just a « failed » without the reason. I think it would be good for the user, even before coming here, to know the exact reason when it can be determined, no?

In this case I know I have some work to do on this on the Netatmo side, for example.

6

Hi @Terdious :slight_smile: Don’t worry, you didn’t have backups for 3 months — if

1 Like