Release: 2.0.6.1 (beta) 2021-05-03

Welcome to the forum @riptera

Your configs (including config for backup job) should be in the Duplicati-server.sqlite that you show.

Every backup job also has non-config data, and that would be in random-letters-named SQLite file.
If your GUI were working (which will be worked on after this intro), the Database screen gives path.

Exporting a backup job configuration to file then safely saving it elsewhere is good. Can’t do that now, but what’s shown looks proper if you upgraded to May 3 release around May 4. I’m guessing job runs at 4 AM.

There are no format changes to config database Duplicati-server.sqlite, so that one doesn’t need a backup.
Backup database increased from 10 to 11 per release note, so that DB gets backed up when server starts.
Backup job database isn’t opened until job runs when it finds it needs that update and leaves backup seen.
Scheduled job continues as usual, updating its database May 12 (latest), recording run in server database.

Do you see new files being put to the destination at the time the DB times update? If so, backup is running.

It sounds like you have the GUI up, but can’t see the jobs. Are you logged in as rpite, with Duplicati starting at login (or manually)? If the Duplicati install is a Windows service (you’d have to run a special command), and if the Windows update was an actual version update (not monthly security), situation could be worse.

Assuming a simple install from .msi file originally, Task Manager should show two Duplicati.GUI.TrayIcon processes. Any more than might be leftover. Browser URL bar should say something like localhost:8200. Anything else (e.g. localhost:8300) might also be a conflict between several pairs of Duplicati run at once.

Assuming you actually got updated, About → System Info should show a BaseVersionName which is also found in you C:\Program Files\Duplicati 2\changelog.txt. Extremely old ones e.g. 2.0.2.1_beta_2017-08-01 seem to have trouble jumping to 2.0.6.1_beta_2021-05-03, but I think the symptoms are more a non-start.

Your system info screen should also show ServerVersion, and I would expect that to say 2.0.6.1. Duplicati initially starts from Program Files, searches for installed update, and then a second Duplicati runs on that.
The mechanism has issues, and may be replaced someday, but that’s the design you should expect now.

The reason very old Duplicati have trouble might be because they have an earlier version of update design before the autoupdater went to paired processes with base version and the current as different processes.

If everything looks OK in System info, you could try a different browser or Wikipedia:Bypass your cache.
Different parts of Duplicati home page are obtained differently. You might have fixed parts but not variable.
Browsers usually have web developer tools on the menu to use, but that’s kind of an advanced thing to do.

Yes, that would be correct. And after checking the info > Server Version I find I am still running 2.0.5.1 so the update didn’t run as I first thought. Just to confirm/clarify, I was running 2.0.5.1 when I got the upgrade dialog.

All of these check out.

I tried clearing the cache for the site, then a full browser cache clear and restart and also tried with Edge (which I’ve never opened Duplicati with) and still the same results. The Duplicati UI works, but my previously running backup job is not showing and no scheduled tasks show.

I have a Acronis image backup local so I feel like I have a fallback here, but was wondering if I should try installing the update directly from an .msi or if there was some other procedure (like renaming the db files) that I should try first. I’ve already made a safe copy of the data dir I showed in my previous post so I should be able to get myself back to where I started if I try anything.

I just don’t want to get myself in a worse situation by attempting my normal troubleshooting before confirming with more knowledgeable folk; I am still new to learning the Duplicati “ropes” as it were and I’ve been around long enough to know that sometimes you’re just better off going to the forums and asking as a noob than mucking about too much on your own.

But was that the base version or an upgrade that it ran? Upgrades for non-service are said to go into an updates folder in the folder you show, but since they didn’t, try C:\ProgramData\Duplicati\updates

The repeated message about the update is normal (or at least not unusual), but if you said install and it
didn’t leave a 2.0.6.1 Duplicati somewhere, that’s odd. A later error on Activate is unfortunately possible. Solution for the web UI not being available at all is manual start. Have you tried stopping and restarting?
A tray icon right-click and Quit should clear all Duplicati processses out (typically just the usual pairing).

That’s the solution for a really old base version (e.g. 2.0.2.1). I’d still like to know if you have one that old.
Even if you don’t, it’d be nice to know what’s going on. If somehow the download just glitched and failed, About → General screen has a Check for updates now button that should let you try updating again…

Other suggestions are welcome.

I believe that was the version I was running before I got the update notification (if that is what you mean by base version).

Just checked and I do find the files populated in this folder:

I’ve done this a few times, but my problem is not the WebUI being available - it is. It’s just not showing the backup job that I had created and had running prior to trying the upgrade via the dialog pop up.

If I could just get my job back, I’d be set. Are you saying that if I try manually starting the upgrade it could bring it back? I could be wrong here (and likely am) but it feels more like the db upgrade process ran but didn’t complete or didn’t trigger the Duplicati upgrade.

No. Whether or not this update worked, you could have had previous updates. Any idea of initial install?

An update is heavily validated before use. Possibly something is missing or extra, but hard to tell by hand.
An update that fails validation is ignored. The other question is why yours is there, not in your user profile.
While you’re in there, might as well see what the May 5 Duplicati-crashlog.txt says. That’s a failed server.

I’ll have to check. I think I’ve only updated once before sio I think my base would be two releases prior to this one.

Here’s the contents of the file:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Duplicati.Server.SingleInstance+MultipleInstanceException: Another instance is running, and was notified
   at Duplicati.Server.Program.CreateApplicationInstance(Boolean writeConsole)
   at Duplicati.Server.Program.RealMain(String[] _args)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Duplicati.Library.AutoUpdater.UpdaterManager.RunMethod(MethodInfo method, String[] args)

Have an update. So before all of this, I had successfully set up email reporting for this install and was getting regular emails. Today, I got an email which means that even though I’m not seeing the job on my dashboard it must be in there somewhere still running on schedule. It seems to have choked on the db version. Content of the email is below:

Duplicati Backup report for KARMA-OneDrive Failed:
The database has version 11 but the largest supported version is 10.

This is likely caused by upgrading to a newer version and then downgrading.
If this is the case, there is likely a backup file of the previous database version in the folder C:\Users\rpite\AppData\Local\Duplicati.
Details: Duplicati.Library.Interface.UserInformationException:
The database has version 11 but the largest supported version is 10.

This is likely caused by upgrading to a newer version and then downgrading.
If this is the case, there is likely a backup file of the previous database version in the folder C:\Users\rpite\AppData\Local\Duplicati.
   at Duplicati.Library.SQLiteHelper.DatabaseUpgrader.UpgradeDatabase(IDbConnection connection, String sourcefile, String schema, IList`1 versions)
   at Duplicati.Library.SQLiteHelper.DatabaseUpgrader.UpgradeDatabase(IDbConnection connection, String sourcefile, Type eltype)
   at Duplicati.Library.Main.Database.LocalDatabase.CreateConnection(String path)
   at Duplicati.Library.Main.Database.LocalBackupDatabase..ctor(String path, Options options)
   at Duplicati.Library.Main.Operation.BackupHandler.<RunAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at CoCoL.ChannelExtensions.WaitForTaskOrThrow(Task task)
   at Duplicati.Library.Main.Controller.<>c__DisplayClass14_0.<Backup>b__0(BackupResults result)
   at Duplicati.Library.Main.Controller.RunAction[T](T result, String[]& paths, IFilter& filter, Action`1 method)

Correct me if I am wrong but it looks like my theory was correct; the db upgrade happened but the install of the new version didn’t.

That was the Duplicati collision I was worrying about, but it seemed to have resolve when you looked.

DB version numbers show that the 2.0.6.1 database version update was done, which means 2.0.6.1 managed to come up at least once to do that. Now it isn’t coming up, and you seem to be on 2.0.5.1.

Please check either the GUI or Program Files. If the base isn’t 2.0.5.1, then look for the 2.0.5.1 update.
Generally I expect all updates to be in the same folder which seems to vary. You can see exactly what executable is being run in Task Manager by turning on “Image path name”. Rick-click Details header.

You could sanity-check the 2.0.6.1 update by seeing if right-click Properties show numbers like these:

image

If you look in the folder itself, and sort by Date modified, files should all be the date of initial upgrade.
I’m actually looking at a folder from the zip binaries, but I think autoupdate gives the same set of files.

Thanks for the guidance @ts678. I have to take the neighbor kid to Archery lessons (she’s my unofficial niece) so I won’t be able to get to this until later this evening. But I’ll report back with my findings.

I’m at least encouraged by what I have found and what you’ve verified that there is indeed a light at the end of the tunnel, and that it isn’t a train.

So I’ve managed to get Duplicati running again, though in a somewhat unstable fashion. Here’s the condensed version…

  1. After a few restarts and going to the About page, I managed to get 2.0.5.1 running and saw the activate link, well, activated and once I clicked the link I saw my job again. FIRST thing I did before anything else was export the config!
  2. The job ran that night, and I received the email. It ran with a warning for one of my Norton folders and I wanted to edit the job but couldn’t. Mostly got warnings, but it also crashed Duplicati once. Decided to leave it for the night after restarting it (and left it without the job visible in the WebUI).
  3. This morning I can see from the email that the job ran again, with the same warnings.
  4. Loaded Duplicati Web UI from the tray app and went to the About section and saw it was calling for an activation once again. After a couple of attempts, it activated and once again I could see my job and better yet I could edit it. Did so and re-exported.
  5. Still showing 2.0.5.1, I attempted an upgrade again. Took a couple of times and a reactivation AGAIN but finally worked. Was showing job and running 2.0.6.1. Decided to reply here.
  6. Just for giggles, decided to look at the WebUI one more time. Guess what? No job, showing 2.0.6.1 but calling for yet another activation. As soon as I do, it switched from showing me running 2.0.6.1 to running 2.0.5.1 again. WTH?!?

So at this point I’m wondering if my upgrade just got botched in some weird, one of a kind occurrence and I’m better off uninstalling, reinstalling from a 2.0.6.1 downloaded installer and then import my job configs. I checked to export passwords so will this save my OneDrive creds/token or will I have to open the job and reauthenticate?

I appreciate all the help and guidance, but I don’t want to dominate your time if this is one of those weird Windows things that could never be error trapped in the first place. LOL If I felt like this was a bug I’d be willing to pursue it with you, but my gut tells me this is more of a rarity combined with my initial lack of experience with the program. Worst case scenario: I learned a lot in the process.

But I’d like your opinion one more time before I do so, because I never want to put myself in a position where my lack of patience gets in the way of proper execution (or being able to contribute meaningful data) so I’ll wait until I hear from you.

Thanks once again for a great intro to Duplicati’s level of support!

Just a follow up; since I didn’t hear back from you I took it upon myself to go ahead and proceed as planned. I uninstalled Duplicati, then reinstalled using the 2.0.6.1 msi and then imported my previous job config. Duplicati picked up where it left off and has been working nominally ever since.

Thanks for your help. As I stated before, I think this was either some weird one of a kind bug unique to my installation or something that I did incorrectly during the update. But everything is back to normal now.

1 Like

A post was split to a new topic: 2.0.6.1 Docker backup, restore, repair missing log warnings and emails

After using the update Button my Email report brings this error every day:

Failed: Could not find method ‘.ctor’ due to a type load error: Could not load file or assembly ‘netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51’ or one of its dependencies. assembly:/usr/share/Duplicati/updates/2.0.6.1/SharpAESCrypt.exe type:SharpAESCrypt member:(null)
Details: System.TypeLoadException: Could not find method ‘.ctor’ due to a type load error: Could not load file or assembly ‘netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51’ or one of its dependencies. assembly:/usr/share/Duplicati/updates/2.0.6.1/SharpAESCrypt.exe type:SharpAESCrypt member:(null)
at Duplicati.Library.Encryption.EncryptionBase.Encrypt (System.IO.Stream input, System.IO.Stream output) [0x00000] in :0
at Duplicati.Library.Encryption.EncryptionBase.Encrypt (System.String inputfile, System.String outputfile) [0x0000e] in :0
at Duplicati.Library.Main.Operation.Common.BackendHandler+FileEntryItem.Encrypt (Duplicati.Library.Main.Options options) [0x0003b] in <34c05650075c4a0583e29e116862f000>:0
at Duplicati.Library.Main.Volumes.VolumeWriterBase.CreateFileEntryForUpload (Duplicati.Library.Main.Options options) [0x00018] in <34c05650075c4a0583e29e116862f000>:0
at Duplicati.Library.Main.Operation.Backup.SpillCollectorProcess.UploadVolumeAndIndex (Duplicati.Library.Main.Operation.Backup.SpillVolumeRequest target, CoCoL.IWriteChannel1[T] outputChannel, Duplicati.Library.Main.Options options, Duplicati.Library.Main.Operation.Backup.BackupDatabase database) [0x00018] in <34c05650075c4a0583e29e116862f000>:0 at Duplicati.Library.Main.Operation.Backup.SpillCollectorProcess+<>c__DisplayClass0_0.<Run>b__0 (<>f__AnonymousType112[j__TPar,j__TPar] self) [0x0081e] in <34c05650075c4a0583e29e116862f000>:0
at CoCoL.AutomationExtensions.RunTask[T] (T channels, System.Func2[T,TResult] method, System.Boolean catchRetiredExceptions) [0x000d5] in <9a758ff4db6c48d6b3d4d0e5c2adf6d1>:0 at Duplicati.Library.Main.Operation.BackupHandler.RunMainOperation (System.Collections.Generic.IEnumerable1[T] sources, Duplicati.Library.Snapshots.ISnapshotService snapshot, Duplicati.Library.Snapshots.UsnJournalService journalService, Duplicati.Library.Main.Operation.Backup.BackupDatabase database, Duplicati.Library.Main.Operation.Backup.BackupStatsCollector stats, Duplicati.Library.Main.Options options, Duplicati.Library.Utility.IFilter sourcefilter, Duplicati.Library.Utility.IFilter filter, Duplicati.Library.Main.BackupResults result, Duplicati.Library.Main.Operation.Common.ITaskReader taskreader, System.Int64 filesetid, System.Int64 lastfilesetid, System.Threading.CancellationToken token) [0x0035f] in <34c05650075c4a0583e29e116862f000>:0
at Duplicati.Library.Main.Operation.BackupHandler.RunAsync (System.String sources, Duplicati.Library.Utility.IFilter filter, System.Threading.CancellationToken token) [0x01048] in <34c05650075c4a0583e29e116862f000>:0
at CoCoL.ChannelExtensions.WaitForTaskOrThrow (System.Threading.Tasks.Task task) [0x00050] in <9a758ff4db6c48d6b3d4d0e5c2adf6d1>:0
at Duplicati.Library.Main.Operation.BackupHandler.Run (System.String sources, Duplicati.Library.Utility.IFilter filter, System.Threading.CancellationToken token) [0x00009] in <34c05650075c4a0583e29e116862f000>:0
at Duplicati.Library.Main.Controller+<>c__DisplayClass14_0.b__0 (Duplicati.Library.Main.BackupResults result) [0x0004b] in <34c05650075c4a0583e29e116862f000>:0
at Duplicati.Library.Main.Controller.RunAction[T] (T result, System.String& paths, Duplicati.Library.Utility.IFilter& filter, System.Action`1[T] method) [0x0011c] in <34c05650075c4a0583e29e116862f000>:0

Log data:
2021-06-01 01:00:20 +00 - [Error-Duplicati.Library.Main.Operation.BackupHandler-FatalError]: Fatal error
System.TypeLoadException: Could not find method ‘.ctor’ due to a type load error: Could not load file or assembly ‘netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51’ or one of its dependencies. assembly:/usr/share/Duplicati/updates/2.0.6.1/SharpAESCrypt.exe type:SharpAESCrypt member:(null)
at Duplicati.Library.Encryption.EncryptionBase.Encrypt (System.IO.Stream input, System.IO.Stream output) [0x00000] in :0
at Duplicati.Library.Encryption.EncryptionBase.Encrypt (System.String inputfile, System.String outputfile) [0x0000e] in :0
at Duplicati.Library.Main.Operation.Common.BackendHandler+FileEntryItem.Encrypt (Duplicati.Library.Main.Options options) [0x0003b] in <34c05650075c4a0583e29e116862f000>:0
at Duplicati.Library.Main.Volumes.VolumeWriterBase.CreateFileEntryForUpload (Duplicati.Library.Main.Options options) [0x00018] in <34c05650075c4a0583e29e116862f000>:0
at Duplicati.Library.Main.Operation.Backup.SpillCollectorProcess.UploadVolumeAndIndex (Duplicati.Library.Main.Operation.Backup.SpillVolumeRequest target, CoCoL.IWriteChannel1[T] outputChannel, Duplicati.Library.Main.Options options, Duplicati.Library.Main.Operation.Backup.BackupDatabase database) [0x00018] in <34c05650075c4a0583e29e116862f000>:0 at Duplicati.Library.Main.Operation.Backup.SpillCollectorProcess+<>c__DisplayClass0_0.<Run>b__0 (<>f__AnonymousType112[j__TPar,j__TPar] self) [0x0081e] in <34c05650075c4a0583e29e116862f000>:0
at CoCoL.AutomationExtensions.RunTask[T] (T channels, System.Func2[T,TResult] method, System.Boolean catchRetiredExceptions) [0x000d5] in <9a758ff4db6c48d6b3d4d0e5c2adf6d1>:0 at Duplicati.Library.Main.Operation.BackupHandler.RunMainOperation (System.Collections.Generic.IEnumerable1[T] sources, Duplicati.Library.Snapshots.ISnapshotService snapshot, Duplicati.Library.Snapshots.UsnJournalService journalService, Duplicati.Library.Main.Operation.Backup.BackupDatabase database, Duplicati.Library.Main.Operation.Backup.BackupStatsCollector stats, Duplicati.Library.Main.Options options, Duplicati.Library.Utility.IFilter sourcefilter, Duplicati.Library.Utility.IFilter filter, Duplicati.Library.Main.BackupResults result, Duplicati.Library.Main.Operation.Common.ITaskReader taskreader, System.Int64 filesetid, System.Int64 lastfilesetid, System.Threading.CancellationToken token) [0x0035f] in <34c05650075c4a0583e29e116862f000>:0
at Duplicati.Library.Main.Operation.BackupHandler.RunAsync (System.String sources, Duplicati.Library.Utility.IFilter filter, System.Threading.CancellationToken token) [0x00a1c] in <34c05650075c4a0583e29e116862f000>:0

what can I Do?

recreate the docker Container and reimport the configs?

Thank you for this great backup tool!

There’s a debate about whether Docker should update by the usual autoupdate or by a new Docker. Regardless, be sure any persistent data such as your Duplicati .sqlite files are safely on the host.
The dockerhub directions for both duplicati and linuxserver image speak to preserving configuration.

Although I don’t use Docker, I think this problem is fixed, at least in 2.0.6.1 Duplicati image, by below.
Note that the newer Duplicati needs more of mono than before. This may impact non-Docker users.

has some other Docker advice but involved a custom stripped down mono. Easiest path for Docker may be to ensure configuration is on the host, then upgrade Docker. Others might need to upgrade their mono.

I might split this into a separate topic, however it’s sort of a general-potential-interest point if it stays short.

I’ve been meaning to get back to you; shortly after I reinstalled and every thing was working nominally, the job disappeared again. But only the job display - the job itself is running nightly and I continue to get emails sent showing the jobs being processed.

On the About screen, it shows as being activated so that issue went away when I reinstalled. But I can’t see the job listed or showing as a next task so I cannot edit it. I’m getting an error on something failing that I’d like to remove from the source, but without the job showing I have no way to edit it.

Not sure why this has happened again and it’s weird that the job is still there somewhere running each night but I don’t know where to find it. Any ideas? Anything I can provide that might help?

Just to add that this affects the .deb as well — its dependency list needs to be updated accordingly.

I’d definitely recommend updating the container with a new image version. It’s the “docker way” as opposed to trying to update the software inside the image.

It’s extremely easy to do, but it is important that the proper volume mappings have been configured so no critical data is stored within the container itself.

Does Duplicati’s Docker follow that or the Duplicati way? If the latter, this issue might be unfortunate:

Cannot disable auto updater #3983

Note the above reference to watchtower, and there may be similar tools. But which one notices first?

Replace auto updater #4542 is a future need, and maybe whatever’s done can keep Docker in mind.

The docker image doesn’t disable the auto-updater. It offers to update to newer versions just like standard Duplicati.

I have never tried it myself, but for kicks I installed 2.6.0.1_beta docker image. I did some basic configurations and then downloaded/activated the 2.0.6.3_beta version that was offered in the web UI.

Looks like it worked, but I still think it’s better to do it the docker way (watchtower is a way to automate that).