Release: 2.1.0.2 (Beta) 2024-11-29

SirFritz · December 11, 2024, 1:53am

Yes it was the test that was failing, apologies, I didn’t realise that that backup set did not have any changes since I updated. I manually made a change (dummy text file) and now I get warnings (not errors) about accessing the source file.
I created a new backup set to test, backing up 1 text file to and from /root (as I assume duplicati running as a service should be able to access this?) and I get same error.
I also updated to the latest canary just to be sure.

{
  "DeletedFiles": 0,
  "DeletedFolders": 0,
  "ModifiedFiles": 0,
  "ExaminedFiles": 1,
  "OpenedFiles": 0,
  "AddedFiles": 0,
  "SizeOfModifiedFiles": 0,
  "SizeOfAddedFiles": 0,
  "SizeOfExaminedFiles": 0,
  "SizeOfOpenedFiles": 0,
  "NotProcessedFiles": 0,
  "AddedFolders": 0,
  "TooLargeFiles": 0,
  "FilesWithError": 0,
  "ModifiedFolders": 0,
  "ModifiedSymlinks": 0,
  "AddedSymlinks": 0,
  "DeletedSymlinks": 0,
  "PartialBackup": false,
  "Dryrun": false,
  "MainOperation": "Backup",
  "CompactResults": null,
  "VacuumResults": null,
  "DeleteResults": null,
  "RepairResults": null,
  "TestResults": null,
  "ParsedResult": "Fatal",
  "Interrupted": false,
  "Version": "2.1.0.101 (2.1.0.101_canary_2024-12-06)",
  "EndTime": "2024-12-11T01:48:17.1861787Z",
  "BeginTime": "2024-12-11T01:47:27.0946256Z",
  "Duration": "00:00:50.0915531",
  "MessagesActualLength": 37,
  "WarningsActualLength": 1,
  "ErrorsActualLength": 2,
  "Messages": [
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: The operation Backup has started",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: List - Started:  ()",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: List - Completed:  ()",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Temporary: duplicati-20241211T013913Z.dlist.zip.aes",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-SchedulingMissingFileForDelete]: scheduling missing file for deletion, currently listed as Uploading: duplicati-b9ffa0fa2d363438c94bb216bd6253192.dblock.zip.aes",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-b13df65f50f024d099ec4b80acee76cf9.dblock.zip.aes",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-b6aad3387362542b698977a34aa233c42.dblock.zip.aes",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-bdecbee6428064e419196249be022cfeb.dblock.zip.aes",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-b21aaffa580fb4af0b5ba0d97e391f4d2.dblock.zip.aes",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-b1785b5a2f4aa4b0d85158a6357d72cc8.dblock.zip.aes",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Started: duplicati-b098951abeb2945ae9aa7075ce6479437.dblock.zip.aes (957 bytes)",
    "2024-12-11 11:47:27 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Retrying: duplicati-b098951abeb2945ae9aa7075ce6479437.dblock.zip.aes (957 bytes)",
    "2024-12-11 11:47:37 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Rename: duplicati-b098951abeb2945ae9aa7075ce6479437.dblock.zip.aes (957 bytes)",
    "2024-12-11 11:47:37 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Rename: duplicati-b7fc3f67833384644824a5b4e0b7bf3ed.dblock.zip.aes (957 bytes)",
    "2024-12-11 11:47:37 +10 - [Information-Duplicati.Library.Main.Operation.Backup.BackendUploader-RenameRemoteTargetFile]: Renaming \"duplicati-b098951abeb2945ae9aa7075ce6479437.dblock.zip.aes\" to \"duplicati-b7fc3f67833384644824a5b4e0b7bf3ed.dblock.zip.aes\"",
    "2024-12-11 11:47:37 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Started: duplicati-b7fc3f67833384644824a5b4e0b7bf3ed.dblock.zip.aes (957 bytes)",
    "2024-12-11 11:47:37 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Retrying: duplicati-b7fc3f67833384644824a5b4e0b7bf3ed.dblock.zip.aes (957 bytes)",
    "2024-12-11 11:47:47 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Rename: duplicati-b7fc3f67833384644824a5b4e0b7bf3ed.dblock.zip.aes (957 bytes)",
    "2024-12-11 11:47:47 +10 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Rename: duplicati-b38083b0a412245d297f724d062e60252.dblock.zip.aes (957 bytes)",
    "2024-12-11 11:47:47 +10 - [Information-Duplicati.Library.Main.Operation.Backup.BackendUploader-RenameRemoteTargetFile]: Renaming \"duplicati-b7fc3f67833384644824a5b4e0b7bf3ed.dblock.zip.aes\" to \"duplicati-b38083b0a412245d297f724d062e60252.dblock.zip.aes\""
  ],
  "Warnings": [
    "2024-12-11 11:47:27 +10 - [Warning-Duplicati.Library.Main.Operation.Backup.FileBlockProcessor.FileEntry-PathProcessingFailed]: Failed to process path: /root/test.txt\nUnauthorizedAccessException: Access to the path '/root/test.txt' is denied."
  ],
  "Errors": [
    "2024-12-11 11:48:17 +10 - [Error-Duplicati.Library.Main.Operation.BackupHandler-FatalError]: Fatal error\nUnauthorizedAccessException: Access to the path '/root/TESTBACKUP/duplicati-b247060b388d14d67bb9138769b5e662d.dblock.zip.aes' is denied.",
    "2024-12-11 11:48:17 +10 - [Error-Duplicati.Library.Main.Controller-FailedOperation]: The operation Backup has failed with error: One or more errors occurred. (Access to the path '/root/TESTBACKUP/duplicati-b247060b388d14d67bb9138769b5e662d.dblock.zip.aes' is denied. (Access to the path '/root/TESTBACKUP/duplicati-b247060b388d14d67bb9138769b5e662d.dblock.zip.aes' is denied.) (One or more errors occurred. (Access to the path '/root/TESTBACKUP/duplicati-b247060b388d14d67bb9138769b5e662d.dblock.zip.aes' is denied.)))\nAggregateException: One or more errors occurred. (Access to the path '/root/TESTBACKUP/duplicati-b247060b388d14d67bb9138769b5e662d.dblock.zip.aes' is denied. (Access to the path '/root/TESTBACKUP/duplicati-b247060b388d14d67bb9138769b5e662d.dblock.zip.aes' is denied.) (One or more errors occurred. (Access to the path '/root/TESTBACKUP/duplicati-b247060b388d14d67bb9138769b5e662d.dblock.zip.aes' is denied.)))"
  ],
  "BackendStatistics": {
    "RemoteCalls": 7,
    "BytesUploaded": 0,
    "BytesDownloaded": 0,
    "FilesUploaded": 0,
    "FilesDownloaded": 0,
    "FilesDeleted": 0,
    "FoldersCreated": 0,
    "RetryAttempts": 5,
    "UnknownFileSize": 0,
    "UnknownFileCount": 0,
    "KnownFileCount": 0,
    "KnownFileSize": 0,
    "LastBackupDate": "0001-01-01T00:00:00",
    "BackupListCount": 0,
    "TotalQuotaSpace": 352638205952,
    "FreeQuotaSpace": 69327446016,
    "AssignedQuotaSpace": -1,
    "ReportedQuotaError": false,
    "ReportedQuotaWarning": false,
    "MainOperation": "Backup",
    "ParsedResult": "Success",
    "Interrupted": false,
    "Version": "2.1.0.101 (2.1.0.101_canary_2024-12-06)",
    "EndTime": "0001-01-01T00:00:00",
    "BeginTime": "2024-12-11T01:47:27.0946365Z",
    "Duration": "00:00:00",
    "MessagesActualLength": 0,
    "WarningsActualLength": 0,
    "ErrorsActualLength": 0,
    "Messages": null,
    "Warnings": null,
    "Errors": null
  }
}

The fact it seemingly can’t read or write anywhere leads me to believe it could be something else (selinux?).

ts678 · December 11, 2024, 2:03am

If that’s turned on, someone who knows it will have to help, but I’m surprised 2.0.8.1 does differently.

SirFritz · December 11, 2024, 2:40am

SElinux seems to have been the issue (I temporary set it to permissive) as all my backups now work. I wonder if anyone else running fedora/rhel has this issue with the new builds.

kenkendk · December 11, 2024, 8:24am

I have not seen other reports about missing read access. But there is another SELinux issue reported:

github.com/duplicati/duplicati

SELinux alerts while trying to connect to the backend (wrong context on executable).

opened 05:32PM - 30 Nov 24 UTC

Szczurowsky

bug

- [x] I have searched open and closed issues for duplicates. - [x] I have searc…hed the [forum](https://forum.duplicati.com) for related topics. ---------------------------------------- ## Environment info - **Duplicati version**: 2.1.0.1_experimental_2024-11-25 - **Operating system**: RockyLinux 9 - **Backend**: (not related) ## Description Any attempt to make connection to back-end fails with permission denied (SELinux error) regarding access to `name_connect` on a TCP socket. ## Steps to reproduce Install latest duplicati version with rpm -i `version.rpm` - **Actual result**: Every attempt of connection is blocked by SELinux - **Expected result**: No SELinux errors ## Screenshots ## Debug log `---- time->Sat Nov 30 18:18:44 2024 type=PROCTITLE msg=audit(1732987124.510:106974): proctitle=2F7573722F62696E2F6475706C69636174692D736572766572002D2D776562736572766963652D696E746572666163653D6C6F6F706261636B type=SYSCALL msg=audit(1732987124.510:106974): arch=c000003e syscall=42 success=no exit=-13 a0=1c3 a1=7f5ed4f2ee08 a2=1c a3=7f5e22ffc538 items=0 ppid=1 pid=(..) auid=(..) uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=(..) exe="/usr/lib/duplicati/duplicati-server" subj=system_u:system_r:init_t:s0 key=(null) type=AVC msg=audit(1732987124.510:106974): avc: denied { name_connect } for pid=(..)comm=(..) dest=443 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:http_port_t:s0 tclass=tcp_socket permissive=0` ## Solution Currently after installing all binary executables are placed in `/usr/lib/duplicati/`. The problem with this is that it will run in the `lib_t` SELinux context type, rather than the intended `bin_t` one. **Executables should be placed in /usr/bin directory with bin_t context** Currently _temporary fix_ is just running `chcon -t bin_t /usr/lib/duplicati/duplicati-server` to set proper context on executable.

The reason for the other SELinux issue, is that the new builds will symlink into /usr/bin where the previous version would have a shell script invoking mono.

Could it be that the permission issue is related to either binaries being in the “wrong” place, or perhaps mono was granted extra permissions?

Ralf · December 12, 2024, 8:13pm

I have upgraded a few Windows machines, a Linux machine, and my Synology NAS (docker image) to this version. So far everything is working well!

I’m looking for the “howto upgrade”-guide but am unable to find it In case it’s documented somewhere a link would be much appreciated.

And will I need to “Recreate the DB” or will they be converted locally?

kenkendk · December 12, 2024, 9:16pm

There is currently no upgrade guide, as it is meant to “just work”, despite the large changes under the surface. The only two things that seem to cause issues is the change to default honor advisory locking and the mandatory API password. Both are described on the Duplicati with Docker page.

No need, all databases are auto-upgraded when you run the new version. No manual intervention needed.

Ralf · December 13, 2024, 8:21am

Thx a lot! I didn’t even think of “installing just over”

Problem though:

Downloaded win64-gui-msi
I’m running the service-variant, therefore stopped the service, installed msi, started service…
and get a password question which wasn’t there before

What’s the default password?

kenkendk · December 13, 2024, 1:07pm

There is no default password, as that is almost as bad as no password.

You can either grab the signin token from the Windows Event log or use ServerUtil.
All the ways are described on this page:

Ralf · December 13, 2024, 9:29pm

Yes, makes sense and works

fwiep · December 16, 2024, 7:50am

Hello all,

Now using Duplicati 2.1.0.2 beta on Fedora 41. After the successful migration of all my backup jobs from v2.0.x, they would not run without errors and/or warnings. Digging in the system logs using journalctl --b --follow while running the jobs showed SELinux’ policies as being the issue. I had to follow the instructions given by setroubleshootd to be able to run the jobs.

open, read and lock access to user files
ability to connect to a remote (non-standard) SSH port for SFTP backups

All this was fixed by adding this custom policy:

module my-NETTPWorker 1.0;

require {
	type http_port_t;
	type user_home_t;
	type init_t;
	class tcp_socket name_connect;
	class file { lock open read };
}
allow init_t http_port_t:tcp_socket name_connect;
allow init_t user_home_t:file { open read };
allow init_t user_home_t:file lock;

ability to follow symlinks

This was fixed by adding this custom policy:

module my-WorkerThreadIR 1.0;

require {
	type init_t;
	type user_home_t;
	class lnk_file read;
}
allow init_t user_home_t:lnk_file read;

Note: I have practically no understanding of SELinux policies; I have just followed the copy-and-paste instructions that were given to me.

Question: is this the right way to fix these SELinux-related problems (client-side), or should this be fixed on Duplicati’s end?

Thanks, kind regards,
FWieP

kenkendk · December 18, 2024, 11:11am

That is a good question. I am not proficient enough with SELinux to give advice on how to configure it “correctly”.

The steps 1 and 2 are required by Duplicati. It needs open+read access to make backups, and write access to restore files. The port requirement is destination dependent, but looks correct.

For 3, I am not sure what the issue is here, but Duplicati needs to read symlinks (and hardlinks) to be able to backup and understand those.

There is another issue registered with SELinux not liking the idea of having the entire Duplicati installation confined to a single folder, but it looks like you are clear of that.

jan_reinhardt · December 18, 2024, 3:18pm

Hi guys,
when is 2.1.0.2 coming to hub.docker.com as duplicati/duplicati:LATEST ?
Id like my machine to auto-update the container, and not have to switch tags or even images to linuxserver/duplicati.
Thanks!

kenkendk · December 18, 2024, 11:11pm

That will happen when we release a stable version. The logic is that latest points to the latest stable release, but since that has not yet materialized, it is not updated.

I still hope to get a stable release out before new year

ts678 · December 18, 2024, 11:56pm

https://hub.docker.com/r/duplicati/duplicati says

Available tags

beta - the most recent beta release
experimental - the most recent experimental release
canary - the most recent canary release
latest - an alias for beta

which actually used to be correct, as latest and 2.0.8.1_beta_2024-05-07 appear the same.
This might be one of those awkward transitional moments, and above text will switch at stable.
Linuxserver kept going with latest = beta. I guess we’ll see what they do when stable is out.

Although Docker has its own update methods, you’ve now got me wondering what Duplicati’s update notifier will think it’s on in terms of channel if you swap a stable Docker for a Beta one.

would be one guess, and if so then this update notifier is out of sync with one watching latest.

jan_reinhardt · December 19, 2024, 3:56am

like ts678 said, the tags beta
and latest
on hub.docker.com are described as being the same, and this is not true atm then?

bkev · December 19, 2024, 10:15am

Thanks for the update.
I updated my server yesterday and just wanted to say it seems to work as expected.
I use encrypted FTP and all testing since the upgrade has been successful. I’ve even tried changed TLS from 1.2 to TLS 1.3 and this also seems to work which previously I had issues with.

The only thing I noticed was I wasn’t able to log into the web gui right away (running as a service) as it said the password (or nonce?) was incorrect. But, I just left it for a little bit and then it was ok. Not sure if I was putting it in wrong or the database was still updating, but all is working now.

Thanks.

kenkendk · December 19, 2024, 9:24pm

I was not aware of that text. The code that decides what gets the “latest” tag is here:

github.com

duplicati/duplicati/blob/master/ReleaseBuilder/Build/Command.CreatePackage.cs#L1171-L1173


      
          var tags = new List<string> { rtcfg.ReleaseInfo.Channel.ToString(), rtcfg.ReleaseInfo.Version.ToString() };
          if (rtcfg.ReleaseInfo.Channel == ReleaseChannel.Stable)
              tags.Add("latest");

That setting essentially chooses what folder to look in on the update server. For Docker it means that you may get a notification for an update that is not there, or miss a notification.

No, it changed when I rewrote the release build process. Going forward it will be “latest == stable”.

Thanks for the feedback most comments are about things that don’t work

That sounds super weird. There is no nonce anymore, but it could perhaps be a browser cache issue?

ts678 · December 19, 2024, 10:19pm

The workaround might be to manually change the updater channel to Docker tag that you chose. Typically these Docker builds seem to track the non-Docker builds pretty well. LSIO is also good.

Probably.

Use of existing tabs when switching Duplicati versions is perhaps common (especially if there isn’t a convenient tray icon to open a new one), and can probably lead to mysterious mismatches such as old JavaScript trying to authenticate the wrong way, e.g. if it actually talked about a nonce there.

For example, in Edge I log into 2.0.8.1 TrayIcon, stop it, replace with 2.1.0.2 Server, try a login, get

Port 8300 is just my setup. Trying again repeats error message. Browser refresh button solves it.

jan_reinhardt · December 20, 2024, 4:22am

The text made super sense for me, because Duplicati has got the word “beta” in its logo.
Maybe with stable version numbers of 2.* Duplicati should lose that word? For new users it doesn’t generate trust, because if you’re looking for a reliable backup software you don’t want “beta” stuff.
(“Lose all your data to a corrupt backup? Well maybe you shouldn’t have used a software that was still beta.”)

kenkendk · December 20, 2024, 7:31am

The “beta” text is loaded based on what version you are running, so a canary build will show “canary” for example. The word disappears once you are running a stable build.

And I agree completely that the beta mark needs to go.