Solved Backups failing on same app each time

[d19dotca]

I've noticed one app is failing to backup and causing the full backup task to crash. I thought it was memory related so I bumped it up from 4 GB to 6 GB max for backup process, same issue though. What's odd is that if I backup the app individually, it succeeds. So I'm not certain what's causing the issue.

ay 30 21:01:13 box:tasks 10577: {"percent":52.35135135135134,"message":"Uploading backup 806M@26MBps (<appSubDomain>)"}
May 30 21:01:24 box:shell backup-snapshot/app_6b3ebc4f-9708-4243-bc21-4c9a01bc3499 code: null, signal: SIGKILL
May 30 21:01:24 box:backups <appSubDomain> Unable to backup BoxError: Backuptask crashed
at /home/yellowtent/box/src/backups.js:895:29
at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)
at ChildProcess.emit (events.js:315:20)
at ChildProcess.EventEmitter.emit (domain.js:467:12)
at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12) {
reason: 'Internal Error',
details: {}
May 30 21:01:24 box:taskworker Task took 133.496 seconds

Any suggestions?

[d19dotca]

Nevermind, lol. I increased the memory further to 7 GB while also lowering the message size from 1 GB to 512 MB, and suddenly it's all working again. What's weird to me is this was never an issue before, and this app that kept triggering the fail was always on my server since basically day one of starting Cloudron years ago. Also my server's backups were successful now for about a month or two since the last (unrelated) incident. No new apps installed, if anything it's one or two less now. So no idea what would trigger that. haha but it seems to be okay now.

By the way, since there's a ton of backup crashing that seem memory related... is it possible to improve the logging so that there's something in there saying "OutOfMemory" or something like that so poeple know why it's crashing?

[girish]

@d19dotca said in Backups failing on same app each time:

By the way, since there's a ton of backup crashing that seem memory related... is it possible to improve the logging so that there's something in there saying "OutOfMemory" or something like that so poeple know why it's crashing?

Yeah, I would love this as well. Sadly, there seems to be no way on linux to know this reliably. A process just gets killed unceremoniously with SIGKILL and that's that If anyone know how this can be detected would be great.