Duplicati hangs for days. Log in shows "Backup Complete" for one set

Duplicati on one Mac has not done a successful backup for days. When I log in locally to port 8200, it shows both backup sets and the message in the progress bar "<SETNAME> Backup Complete!" I’ve restarted the Duplicati background, but that doesn’t change anything.

On investigation, after unloading the Duplicatie LaunchDaemon there were still background servers running. And there was regular activity of CrashReporter, but I haven’t been able to find any crash report in the usual places.

I killed the extra processes by hand and loaded the LaunchDaemon again. No success. I see these processes:

0 25532     1   0  20 20  4306044   9380 -      SNs    ??    0:00.09 /Applications/Duplicati.app/Contents/MacOS/duplicati-server --webservice-port=8200 --log-file=/Library/Logs/duplicati_server.log --log-level=Information --verbose=true
0 25535 25532   0  20 20  4367144  29488 -      SN     ??    0:00.41 /Library/Frameworks/Mono.framework/Versions/Current/Commands/mono /Applications/Duplicati.app/Contents/Resources/Duplicati.Server.exe --webservice-port=8200 --log-file=/Library/Logs/duplicati_server.log --log-level=Information --verbose=true
0 25537 25535   0  46 20  4371808  33272 -      UN     ??    0:00.46 /Library/Frameworks/Mono.framework/Versions/5.20.1/bin/mono-sgen64 /Applications/Duplicati.app/Contents/Resources/Duplicati.Server.exe --webservice-port=8200 --log-file=/Library/Logs/duplicati_server.log --log-level=Information --verbose=true

And I see this in caught output:

Another instance is running, and was notified

I unloaded again, killed two remaining instances (one with SIGKILL as it would not die with SIGTERM). Now, I’m at the situation that it is not running. And I’m wondering what to do next.

Check running processes with ps aux – I hope its the same command as in linux
If there is some orphaned processes u should kill them too. Then I gueess u should start duplicati and report again.

Killing them was about the orphans. ps laxww|grep upli comes up empty now. But just starting Duplicati in the background doesn’t get me a server I can connect to on port 8200. While the processes are there:

luna-wifi:~ gerben$ ps laxww|grep upli
    0 25992     1   0  20 20  4306044   9328 -      SNs    ??    0:00.03 /Applications/Duplicati.app/Contents/MacOS/duplicati-server --webservice-port=8200 --log-file=/Library/Logs/duplicati_server.log --log-level=Information --verbose=true
    0 25996 25992   0  20 20  4366128  29888 -      SN     ??    0:00.45 /Library/Frameworks/Mono.framework/Versions/Current/Commands/mono /Applications/Duplicati.app/Contents/Resources/Duplicati.Server.exe --webservice-port=8200 --log-file=/Library/Logs/duplicati_server.log --log-level=Information --verbose=true
    0 26007 25996   0  20 20  4371756  32896 -      SN     ??    0:00.49 /Library/Frameworks/Mono.framework/Versions/5.20.1/bin/mono-sgen64 /Applications/Duplicati.app/Contents/Resources/Duplicati.Server.exe --webservice-port=8200 --log-file=/Library/Logs/duplicati_server.log --log-level=Information --verbose=true
 1025 26011 25973   0  31  0  4277256    808 -      S+   s001    0:00.00 grep upli

And the output shows:

Unable to start up, perhaps another process is already running?
Error message: System.Exception: The lock file was locked, but the locking process did not respond to the start command
  at Duplicati.Server.SingleInstance..ctor (System.String basefolder) [0x0025e] in <63a01150aadd4a64a4d7c359bdc1e45d>:0 
  at Duplicati.Server.Program.CreateApplicationInstance (System.Boolean writeConsole) [0x00005] in <63a01150aadd4a64a4d7c359bdc1e45d>:0

can u manually start duplicati from console with some random port and see if u can connect that way?
On linux it would be something like this
/usr/bin/mono /opt/duplicati-latest/Duplicati.GUI.TrayIcon.exe --webservice-port=8400 --webservice-interface=loopback
and then try to connect to port 8400.
If not mistaken, mono garbage collector mono-sgen64 might causing your problems.
Also can u post some logs files from /var/log/messages

The start at port 8400 did not help. I removed the processes again. Then, on a hunch, I looked for mono-sgen and there were 3 still running that had been killed with SIGKILL. So, these were unkillable zombies. I restarted the machine (this hardly ever happens) and after a restart everything seems to be working again. Though the UI does complain about a warning that is not there.

So u couldn’t kill a process with kill -9? If this ever happen again check STAT column of that process. If, for example has letter D you might want to check your disks for health. There is a topic here on forum dealing with multiple disk failure.