Receiving HTTP2 GOAWAY messages with Windows restic v0.17.0

Getting Help
1

I have used Restic for years in linux without issue but have had to deploy it on Windows for backups. All seemed to be going well with BorgBase so I paid for the 1TB and started uploading to the repo. I am now seeing filed backups with logs showing:

restic.exe : Save(<data/22f76475fe>) returned error, retrying after 714.197635ms: Post "https://xxxxxxxx.repo.borgbase.com/data/22f76475fe27d0d8141ec9d395eda942eeedc3e12684c2621d8f8fb30
95584bb": http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown 
GOAWAY] after Request.Body was written; define Request.GetBody to avoid this error
At C:\restic\backup.ps1:290 char:13
+             & $ResticExe backup $ResticBackupFlags $folder_list $vss_ ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Save(<data/22f7...void this error:String) [], RemoteE 
   xception
    + FullyQualifiedErrorId : NativeCommandError
 
Save(<data/21cfb347a5>) returned error, retrying after 525.840985ms: Post "https://xxxxxxx.repo.borgbase.com/data/21cfb347a599268bba18a82fe9fb1421028c56cbedf932356342f252c8049e44": 
http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown GOAWAY] 
after Request.Body was written; define Request.GetBody to avoid this error
Save(<data/22f76475fe>) operation successful after 1 retries
Save(<data/21cfb347a5>) operation successful after 1 retries
Save(<data/874c5655a5>) returned error, retrying after 932.56665ms: Post "https://xxxxxx.repo.borgbase.com/data/874c5655a5308e45a7cb61207c6abbe959711cf7bc388b531e1d16e3f31ca0f1": 
http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown GOAWAY] 
after Request.Body was written; define Request.GetBody to avoid this error
Save(<data/874c5655a5>) operation successful after 1 retries

Any ideas on what to try? 100M/100M fibre internet service.

2

Try contacting BorgBase. Their server is telling you to go away.

3

Of course I have contacted them. Given they are a not to insignificant player in Bord / Restic storage I thought I’d ask here as well.

4

Of course you did! My apologies.

5

Of course I did

image
image1568×404 58.1 KB

6

image
image1746×240 11.3 KB

7

So I still don’t know if the issue is on the Borg http server side or the http/http2 library used by the restic windows client. I don’t recall seeing this issue on the restic linux client I have used for years.

8

That message from the go standard library is meant for the developers :slight_smile: . I’ve created a PR to fix it: rest: improve handling of HTTP2 goaway by MichaelEischer · Pull Request #5018 · restic/restic · GitHub .