Unable to reconnect following upgrade to 0.9.7

Support
1

After upgrading to 0.9.7 the following is displayed by Kopia UI.

image

In an effort see what is going on I have tried to connect via cli:

kopia repo connect rclone --remote-path=onedrive-personal:backup --log-level=debug --log-dir=c:\temp\kopia\

…this generates the following output:

generating new TLS certificate
adding alternative IP to certificate: 127.0.0.1
starting C:\Program Files\Rclone\rclone.exe
detected webdav address: https://127.0.0.1:20767/
Enter password to open repository:

Creating cache directory 'C:\Users\Chris\AppData\Local\kopia\34920e150ee5b318' with max size 5242880000
generating new TLS certificate
adding alternative IP to certificate: 127.0.0.1
starting C:\Program Files\Rclone\rclone.exe
detected webdav address: https://127.0.0.1:20780/
finished sweeping content cache in 831.2µs and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 37.7296ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 611.5µs and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 34.0402ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 1.008ms and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 34.0696ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 646.3µs and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 39.2453ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 962.3µs and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 41.5607ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 1.264ms and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 35.7785ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 1.3697ms and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 33.3384ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 1.168ms and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 37.4939ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 1.0684ms and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 34.2747ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 1.0632ms and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 33.3595ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 1.0343ms and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 32.1488ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 1.1721ms and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 45.0539ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 1.218ms and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 34.5785ms and retained 2023429987/5242880000 bytes (38 %)
finished sweeping content cache in 561.2µs and retained 490860/5242880000 bytes (0 %)
finished sweeping metadata cache in 43.0925ms and retained 2023429987/5242880000 bytes (38 %)

Attempting to repair the repo has no obvious effect. It isn’t the end of the world for me if I must destroy and rebuild the repo from scratch, but naturally this has me wondering whether the issue will reoccur.

Would very much appreciate any input, perhaps this is recoverable?

2

How big is the repository and is there a chance it’s simply very slow backend? Can you see the files using rclone directly?

3

I presume you did not disconnect the repository in the UI when doing the upgrade, right? Can you add another connection tot the same repo and see if that works ?

4

Wow, talk about swift responses…

Sadly the repo is on a relatively slow backend, OneDrive Personal, size-wise we’re talking <4Gb.

rclone ls yields a very quick output, for what indication that might give. To date this setup has been pretty stable, surprisingly so to be honest.

Edit: Bandwidth 500/76Mbs

5

I have tried adding the repo again via KopiaUI, but it does not progress beyond the following.

ConnectRepo

6

Hmm, but rclone size onedrive-personal:backup is painfully slow:

2021/12/11 23:01:12 DEBUG : rclone: Version "v1.57.0" starting with parameters ["C:\\Program Files\\Rclone\\rclone.exe" "size" "onedrive-personal:backup" "-vv"]
2021/12/11 23:01:12 DEBUG : Creating backend with remote "onedrive-personal:backup"
2021/12/11 23:01:12 DEBUG : Using config file from "C:\\Users\\Chris\\.config\\rclone\\rclone.conf"
2021/12/11 23:06:55 ERROR : UnknownError: : upload chunks may be taking too long - try reducing --onedrive-chunk-size or decreasing --transfers
2021/12/11 23:06:55 DEBUG : pacer: low level retry 1/10 (error UnknownError: )
2021/12/11 23:06:55 DEBUG : pacer: Rate limited, increasing sleep to 20ms
2021/12/11 23:06:55 DEBUG : pacer: Reducing sleep to 15ms
2021/12/11 23:06:55 DEBUG : pacer: Reducing sleep to 11.25ms
2021/12/11 23:06:55 DEBUG : pacer: Reducing sleep to 10ms
Total objects: 1.185k (1185)
Total size: 10.893 GiB (11696624641 Byte)
2021/12/11 23:11:27 DEBUG : 3 go routines active

Looks like I was a little ‘off’ regarding repo size, more like 10Gb+.

Perhaps I need to rethink the backend, cheap isn’t always cheerful!

7

Yeah, that’s definitely an indication that backend is being slow.

8

Understood, I will find a better alternative.

Very much appreciate your input, and of course the solution itself, kopia is most excellent :slight_smile: