Unsolved Backup fails - "task 475 crashed with code null and signal SIGABRT"

[necrevistonnezr]

All my backup tasks crashed overnight

task 475 crashed with code null and signal SIGABRT

I'm using the following settings:

Provider: filesystem
Location: /media/CloudronBackup
Storage Format: rsync
Hardlinks: yes
Retention time: 1 week

Logs: https://paste.cloudron.io/anahomiduw.php

[murgero]

@necrevistonnezr

Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Is there error here. I am not sure of a fix, but hope it helps you find one.

[nebulon]

Hi there, can you try following the guide how to increase the memory limit for those processes at https://cloudron.io/documentation/troubleshooting/#backups ?

[necrevistonnezr]

In

/etc/systemd/system/box.service

I currently have this setting:

MemoryMax=400M

[nebulon]

Does the server run out of memory for the whole system during a backup?

[necrevistonnezr]

Not that I recall - the only thing "out of the ordinary" is the preview generator task by Nextcloud currently (see https://forum.cloudron.io/topic/1716/nextcloud-preview-generator-cron-trouble)

[nebulon]

That box.service file also contains a value for --max_old_space_size= can you set this higher as well and retry? After editing the file, you have to run:

systemctl daemon-reload
systemctl restart box

[necrevistonnezr]

Changed the Setting from 150 to 300. Backup still crashes.

[girish]

@necrevistonnezr I pinged you on chat, will ping again tomorrow.

[girish]

@necrevistonnezr Thanks for helping debug this further!

For the rest: The issue is that there are a large number of files (> 400k) getting backed up and the syncer code is running out of memory since it loads all those filenames in memory. I will get this fixed in the next version. For now, disable automatic backups for nextcloud.