Duplicati 22.214.171.124 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:
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:
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.