Release: 2.0.4.9 (canary) 2018-12-22

2.0.4.9-2.0.4.9_canary_2018-12-22

  • Improved code quality, thanks @warwickmm
  • Fixed typo, thanks @JonMikeIV
  • Improved speed from default filter groups, thanks @warwickmm
  • Fixed CPU/memory issue on MacOS, thanks @warwickmm
2 Likes

Thanks for the quick response on this one Kenneth! :slight_smile:

Updates server seems to be giving 502s, causing fallback to the alt server which isn’t set up. Thread here.

C:\Program Files\Duplicati 2>Duplicati.Library.AutoUpdater.exe check
Error detected: System.Net.WebException: The remote server returned an error: (502) Bad Gateway.
   at System.Net.WebClient.DownloadFile(Uri address, String fileName)
   at Duplicati.Library.AutoUpdater.UpdaterManager.CheckForUpdate(ReleaseType channel)
Error detected: System.Net.WebException: The remote name could not be resolved: 'alt.updates.duplicati.com'
   at System.Net.WebClient.DownloadFile(Uri address, String fileName)
   at Duplicati.Library.AutoUpdater.UpdaterManager.CheckForUpdate(ReleaseType channel)
No updates found

C:\Program Files\Duplicati 2>

Just updated my Windows 10 machine using the MSI, and when I looked at the “About, Show Log” it just sat there on “Loading…” until I forced a backup. Then some entries appeared. When I look at “Live” all I see is the level “Disabled”. After the backup completed, for which its own logs are fine, going back to “About” is once again sitting at “Loading…” unless I manually refresh.

Also, how do I update my headless Fedora Server running an older beta, with the update error still happening?

System.IO.InvalidDataException: Unable to verify signature at Duplicati.Library.AutoUpdater.SignatureReadingStream..ctor (System.IO.Stream stream, System.Security.Cryptography.RSACryptoServiceProvider key) [0x00019] in <3227b98b904042faac2116282e7fbdfd>:0 at (wrapper remoting-invoke-with-check) Duplicati.Library.AutoUpdater.SignatureReadingStream:.ctor (System.IO.Stream,System.Security.Cryptography.RSACryptoServiceProvider) at Duplicati.Library.AutoUpdater.UpdaterManager.CheckForUpdate (Duplicati.Library.AutoUpdater.ReleaseType channel) [0x00101] in <3227b98b904042faac2116282e7fbdfd>:0

It’s been weeks since the auto-updater was working on any of my machines.

The canary has an issue with live logs tracked here: https://github.com/duplicati/duplicati/issues/3554 and with a pending fix here: added back watchers for live logs by Pectojin · Pull Request #3555 · duplicati/duplicati · GitHub

I’d recommend pulling the rpm and updating that way: Releases · duplicati/duplicati · GitHub

The update error might have been resolved - please try again.

Thanks, I actually tried it yesterday when I saw the alert for the new release, around 10:00 UTC+1, and I still had the error. So I manually updated all my systems using the MSI and RPM files, and now they no longer report a problem in the logs.

Running the update on Linux stops the service and leaves it hanging. Doesn’t reconnect or anything. Errors out. Stop the service, start it again and it prompts again for the 2.0.4.10 update. Not sure? Thought I would chime in here.
Again, 2.0.4.10 update, not the 2.0.4.9 hightlighted in this post but thought it might be worth while mentioning.

Dec 30 02:15:25 tech-pc mono[7973]: at Mono.Data.Sqlite.SqliteTransaction.Rollback () [0x00008] in
Dec 30 02:15:25 tech-pc mono[7973]: at Mono.Data.Sqlite.SqliteTransaction.Dispose (System.Boolean disposing) [0x00018] in >
Dec 30 02:15:25 tech-pc mono[7973]: at System.Data.Common.DbTransaction.Dispose () [0x00000] in
Dec 30 02:15:25 tech-pc mono[7973]: at Duplicati.Server.Database.Connection.DeleteFromDb (System.String tablename, System.>
Dec 30 02:15:25 tech-pc mono[7973]: at Duplicati.Server.Database.Connection.DeleteFromDb (System.String tablename, System.>
Dec 30 02:15:25 tech-pc mono[7973]: at Duplicati.Server.Database.Connection.DismissNotification (System.Int64 id) [0x00051>
Dec 30 02:15:25 tech-pc mono[7973]: at Duplicati.Server.WebServer.RESTMethods.Notification.DELETE (System.String key, Dupl>
Dec 30 02:15:25 tech-pc mono[7973]: at Duplicati.Server.WebServer.RESTHandler.DoProcess (Duplicati.Server.WebServer.RESTMe>
Dec 30 02:15:25 tech-pc systemd[1]: duplicati.service: Main process exited, code=exited, status=126/n/a
Dec 30 02:15:25 tech-pc systemd[1]: duplicati.service: Failed with result ‘exit-code’.