Backup Failed

[girish]

@humptydumpty I wonder if this is a temporary network issue. Does this happen again?

[humptydumpty]

@girish Yes, this happened before. Previous error was about 2-3 weeks ago. If it's network related, I assume there's nothing I can do about it. Any way to verify the integrity of the backup files without having to manually restore/test them?

Edit: oh no, this last error was 3 days ago and it hasn't repeated yet. Rereading this, I'm confusing af so here's the timeline:

today (no errors) --> 3 days ago (one error) ---> 3 weeks ago (one error) --> no errors iirc.

[girish]

@humptydumpty Generally, it's normal for things to fail once in a while but not regularly. Servers, network go up and down. Anyway, it if's happening very regularly, we can investigate further. Please write to support@cloudron.io in such a case.

[micmc]

@girish said in Backup Failed:

@humptydumpty Generally, it's normal for things to fail once in a while but not regularly. Servers, network go up and down. Anyway, it if's happening very regularly, we can investigate further. Please write to support@cloudron.io in such a case.

I also experiment the same thing since the update to 7.1 I haven't had much time to report yet because manual backup is working, so I can still trigger one when I get on my dashboard.
However, it was working without any glitches previously and I haven't changed anything nor moved server etc.
The log shows that the process for tar for each app goes on 'till the end however it seems like once the box:tasks setCompleted then the backup is not found.
I get the backup failed message every day for about two weeks now.
Here's the end lines of the backup log file:

2022-04-05T03:31:41.902Z box:taskworker Task took 1901.358 seconds
2022-04-05T03:31:41.902Z box:tasks setCompleted - 9312: {"result":null,"error":{"stack":"BoxError: Backup not found\n    at Object.update (/home/yellowtent/box/src/backups.js:187:42)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)","name":"BoxError","reason":"Not found","details":{},"message":"Backup not found"}}
2022-04-05T03:31:41.902Z box:tasks update 9312: {"percent":100,"result":null,"error":{"stack":"BoxError: Backup not found\n    at Object.update (/home/yellowtent/box/src/backups.js:187:42)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)","name":"BoxError","reason":"Not found","details":{},"message":"Backup not found"}}
BoxError: Backup not found
    at Object.update (/home/yellowtent/box/src/backups.js:187:42)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Is there anything I should check before reaching support by email?

[girish]

@micmc What backup provider are you using?

[micmc]

@girish AWS S3 actually

[girish]

@micmc said in Backup Failed:

Is there anything I should check before reaching support by email?

Nothing obvious stands out. Please reach out via email.

[micmc]

@girish said in Backup Failed:

@micmc said in Backup Failed:

Is there anything I should check before reaching support by email?

Nothing obvious stands out. Please reach out via email.

Will do though will check and try a few things before, because it's now become more intermittent. Weird lol
Manual backup still works pretty well otoh

TTYL

[humptydumpty]

@girish I'm getting more backup errors but it's a bit different. Is this another temp network hiccup or something more serious?

This happened 3 days ago but I ignored it.

Backup failed: Could not pipe http://172.18.0.12:3000/backup?access_token=xxxxxxxxxxx to /home/yellowtent/appsdata/xxxxxxxxxxx /dump.rdb: Request timedout

Then another error 7 hours ago:

Backup failed: Could not pipe http://172.18.0.3:3000/databases/dbxxxxxxx to /home/yellowtent/appsdata/xxxxxxxx/postgresqldump: Request timedout. 

I replaced the actual values with xxxxxxxxxxx in case those are sensitive.

Edit: two more backup attempts failed today and I received an email from my cloudron saying a full backup failed this time. I have a flight today. I'll email the logs to support when I can. Thanks!

[girish]

@humptydumpty said in Backup Failed:
This is most likely to do with postgresql not having enough memory. Please go to Services and bump up the postgres memory.