Backup stops running and shows "Aborted 6 day ago"

Support
#1

Hello, i’m new to Duplicacy. I have it running in an Unraid Docker from : hub.docker saspus/duplicacy-web

The backup target is wasabi us-east-2

I have a few backups specified, on a particularly large one , approx. 2 TB, it will stop running randomly and show that it was aborted several days ago, even though i kicked it off last night. I’ve tried it multiple times and it always stops.
In the duplicacy_web.log, there are a ton of “An error has occurred: runtime error: invalid memory address or nil pointer dereference” messages throughout the entire log.

Here is a snippet of the end of the duplicacy_web.log

Here is the backup log (sanitized)

Any assistance you can provide would be awesome.

#2

The CLI running the backup may be killed due to using too much memory. The memory usage is highly dependent on the number of files, rather than the total size of all files. At this time the only workaround is to divide the backup job into several smaller jobs either by backing up subdirectories separately or using different filters for each smaller job.

The "invalid memory address or nil pointer dereference” error is caused by uninitialized objects (which may also be caused by an out-of-memory situation where the browser becomes slow). I’ve replicated this bug in my testing and will fix it for the next release.

#3

Thank you for the reply!
I have multiple backups configured to split up critical folders. This is the only one giving me trouble.
It has 13,105 Files using 3.22TB of space. Most of the files are very small, the rest are computer backups.
There was another folder I was able to backup successfully that has 33,288 using 73GB of space.

The machine the docker is running on has 32GB of RAM. Is there a parameter I can configure to allow it to use more RAM? It’s been running for about 12 hours now and is only consuming 1GB.

#4

That doesn’t look like an out-of-memory issue.

Can you check the log file ~/.duplicacy-web/logs/duplicacy_web.log to see if the web GUI was restarted? You can grep for Duplicacy Web Edition line which is printed on restart.

#5

Here is a section of the log requested where the words “Duplicacy Web Edition” show up.

Thanks for your help!

#6 
2020/11/25 02:00:10 Failed to request a license: activate

It is likely that the backups failed due to an expired license.

#7

I’m still in the trial period and I can still complete on-prem backups without an issue. However, I just purchased a license and activated then started the backup again. I’ll report back in the morning. :slight_smile:

image

#8

Issue persists when a license has been purchased and activated.

I can see in this line that the backup appears to still be running at 02:00
2020/11/26 02:00:01 A manual backup is in progress for computer localhost and backup 6

Then at 5:31:05 this message pops up
2020/11/26 05:31:05 Failed to get the value from the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: dbus: DBUS_SESSION_BUS_ADDRESS not set
Followed by the “Duplicacy Web Edition” Message.
2020/11/26 05:31:05 Duplicacy Web Edition 1.4.1 (074ED2)

#9

I’m still experiencing this issue, are there any known fixes?

#10

Can you post a new log file?

#11

Sorry for the delay, the backup was running and i had to wait for it to fail again.

Here is the section in the duplicacy_web.log where “Duplicacy Web Edition” appears last.

Here is the associated backup log for the backup that’s failing.

Running this same backup to local storage works without an issue. It’s only failing when backing up to Wasabi.

#12

This shows that the web GUI was restarted at 5:30. Do you know why it was restarted? Was the backup still running at that time?

2020/12/08 05:30:47 Duplicacy Web Edition 1.4.1 (074ED2)
#13

I don’t know why the Web GUI was restarted. There are no tasks that would restart it that i know of.
Yes, the backup was running at that time.

Right before the Web UI restarts there is this message.

  1. 2020/12/08 05:30:47 Failed to get the value from the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: dbus: DBUS_SESSION_BUS_ADDRESS not set

  2. 2020/12/08 05:30:47 Temporary directory set to /cache

  3. 2020/12/08 05:30:47 Duplicacy Web Edition 1.4.1 (074ED2)

#14

So i’m an idiot. I dug into this and it looked like it was always happening at 5AM. It turns out that the Unraid Application “Backup/Restore Appdata” Stops all of your dockers when it runs, then starts the up again. I had that set to daily at 5AM. I’ve corrected that issue.