Signal: killed while performing prune operation

Bug
,
#1

Please describe what you are doing to trigger the bug:
With my nightly backup since a week when performing prune operation I got signal killed.
See logs:
Running prune command from /root/.duplicacy-web/repositories/localhost/all
Options: [-log prune -storage backup -keep 0:1800 -keep 7:30 -keep 1:7 -a]
2020-10-05 00:02:42.164 INFO STORAGE_SET Storage set to /mnt/backup
2020-10-05 00:02:42.168 INFO RETENTION_POLICY Keep no snapshots older than 1800 days
2020-10-05 00:02:42.168 INFO RETENTION_POLICY Keep 1 snapshot every 7 day(s) if older than 30 day(s)
2020-10-05 00:02:42.168 INFO RETENTION_POLICY Keep 1 snapshot every 1 day(s) if older than 7 day(s)
2020-10-05 00:02:44.196 INFO SNAPSHOT_DELETE Deleting snapshot doktorantske at revision 100
2020-10-05 00:02:44.231 INFO SNAPSHOT_DELETE Deleting snapshot doktorantske at revision 101
2020-10-05 00:02:44.249 INFO SNAPSHOT_DELETE Deleting snapshot documents at revision 91
2020-10-05 00:02:44.262 INFO SNAPSHOT_DELETE Deleting snapshot documents at revision 92
2020-10-05 00:02:44.269 INFO SNAPSHOT_DELETE Deleting snapshot mp3 at revision 85
2020-10-05 00:02:44.740 INFO SNAPSHOT_DELETE Deleting snapshot mp3 at revision 86
2020-10-05 00:02:45.136 INFO SNAPSHOT_DELETE Deleting snapshot pictures at revision 86
2020-10-05 00:02:49.496 INFO SNAPSHOT_DELETE Deleting snapshot pictures at revision 87
2020-10-05 00:02:53.739 INFO SNAPSHOT_DELETE Deleting snapshot projects-install at revision 61
2020-10-05 00:02:54.503 INFO SNAPSHOT_DELETE Deleting snapshot projects-install at revision 62
2020-10-05 00:02:55.023 INFO SNAPSHOT_DELETE Deleting snapshot videocutwork at revision 81
2020-10-05 00:03:03.105 INFO SNAPSHOT_DELETE Deleting snapshot videocutwork at revision 82
2020-10-05 00:03:10.762 INFO SNAPSHOT_DELETE Deleting snapshot work at revision 85
2020-10-05 00:03:11.406 INFO SNAPSHOT_DELETE Deleting snapshot work at revision 86
signal: killed

Please describe what you expect to happen (but doesn’t):
It should prune my old backups. Same happens when executing check.

Please describe what actually happens (the wrong behaviour):
The execution of duplicacy is stopped.

Version: Duplicacy Web Edition 1.3.0

#2

Usually the CLI process gets killed when it uses too much memory. Can you check the memory usage while the prune job is running?

#3

Today it started to work again. I checked the memory consumption during prune but is enough free space, see attached image.

2020-10-06 12_04_16-root@duplicacy_ ~
2020-10-06 12_04_16-root@duplicacy_ ~1247×490 55.2 KB

#4

I have started getting this on roughly 50% of the prune jobs for a particular repository. Is there some way to get it to write more information to the logs about what went wrong? Or is running out of memory pretty much the only thing that causes it?

#5

Is there any error message in .duplicacy-web/logs/duplicacy_web.log?