At the beginning of July, I noticed by pure chance that the Duplicati process had not been backing up anything since June 22nd. Restarting Duplicati.app fails since then. Killing the mono-sgen processes (there are usually two of them) does not help. Right now I use the hack of calling the executable inside Duplicati.app via the shell. The log output from June 22nd does not reveal any critical error that would explain the hanging process.
Jul 4, 2018 10:22 PM: Message removing file listed as Temporary: duplicati-20180623T225528Z.dlist.zip.aes Jun 22, 2018 11:13 PM: Message Expected there to be a temporary fileset for synthetic filelist (53, duplicati-b06e35bdf19ba4d5d8ab178af8481f65f.dblock.zip.aes), but none was found? Jun 22, 2018 11:13 PM: Message scheduling missing file for deletion, currently listed as Uploading: duplicati-i37ce2e5f6d4443449ca5cc05534a0a11.dindex.zip.aes Jun 22, 2018 11:13 PM: Message scheduling missing file for deletion, currently listed as Uploading: duplicati-b81f9df6b7e1d4b949600a6987ca17537.dblock.zip.aes
Today I started the exe once again and got an error message saying that the database is blocked. Again I killed all mono-sgen processes. Starting the executable again (still over command line, running Duplicati.app still fails silently) produced no more error messages in the UI; however, I cannot find any trace of the database error in the log output.
I have no idea how to troubleshoot this and make Duplicati stable and reliable on my MacBook. Any hints about where to start?