You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to set up an existing remote repo (I succeeded, but I think by accident - more on that later).
When I try to save the config I get a 504 error (after a minute or so). The in-UI error message isn't very useful, but trying again gets a pretty instant error due to an unreleased lock (I released it from the command line). That error gave me the command that was run (including env vars I had set). From what I can tell, the pre-save config check times out because borg info takes too long.
I tested borg info directly from the command line; it takes 2-3 minutes to finish (if I restrict it to the latest archive)
I set BORG_REPO to ::latest for repo creation, I don't know if it had an impact
I was able to get the repo config to save - I saw the yellow "Pending configuration changes" popup after a bit, which applied what I had entered into the form. I think one of these happened:
The background borg info command finished and the info was saved (triggering the popup)
The popup happed when OMV tries to sign me out
Working from another tab on the env variables triggered the popup, which captured the repo config too
I can now use the list button on the repo and get a result in seconds. The info button works too; I get the initial output quickly but the size estimate takes a while.
If you can give me some pointers on where to look, I'm happy to do some debugging
The text was updated successfully, but these errors were encountered:
I just tested the guide on a small remote repo. It worked. So, I think you are right and your setup is timing out because borg info is taking so long.
From the command line, if you do a borg info "path/to/repo" --last 1, is it any faster? If not, is borg list "path/to/repo" fast? The plugin needs something to confirm the remote repo is actually a borg repo.
I am trying to set up an existing remote repo (I succeeded, but I think by accident - more on that later).
When I try to save the config I get a 504 error (after a minute or so). The in-UI error message isn't very useful, but trying again gets a pretty instant error due to an unreleased lock (I released it from the command line). That error gave me the command that was run (including env vars I had set). From what I can tell, the pre-save config check times out because
borg info
takes too long.BORG_RSH
configured properlyborg info
directly from the command line; it takes 2-3 minutes to finish (if I restrict it to the latest archive)BORG_REPO
to::latest
for repo creation, I don't know if it had an impactI was able to get the repo config to save - I saw the yellow "Pending configuration changes" popup after a bit, which applied what I had entered into the form. I think one of these happened:
borg info
command finished and the info was saved (triggering the popup)I can now use the list button on the repo and get a result in seconds. The info button works too; I get the initial output quickly but the size estimate takes a while.
If you can give me some pointers on where to look, I'm happy to do some debugging
The text was updated successfully, but these errors were encountered: