'Server returned HTTP 503' from time to time. #845
Comments
|
Seems to be impossible to install |
|
Note that it really only happens for this one flatpak then for some time. So it really looks like a DDOS protection… (but you do have to expect many and large file downloads, that's just how it is) |
Well this is happening for me for multiple flatpaks from flathub not only one :( |
|
Yes, but not all of them, so… that was my point. |
|
Happens every time I try to install org.freedesktop.Sdk.Extension.texlive. Wouldn't be so bad if flatpak didn't try to redownload the whole thing from scratch instead of resuming where it left off. |
|
There wouldn't happen to be a way to get flatpak to resume from where it left off that I don't know about would there? |
|
I too am having this issue. How long do you usually have to wait? |
|
Not sure but since more and people are having trouble with this I suspect that flathub has probably some problems dealing with heavy traffic. |
|
I'm trying to free some disk space as publishing updates is blocked for 20-30h now and that kills the drive. I applied some |
|
OK, we're back. I'll close it for now; next week we're migrating to new server and that should help with infrastructure-related 503s. |
|
Migration was finished so hopefully random 503 will be gone. |
|
This issue may still not be resolved. Downloading large files is extremely slow and still returns 503. I downloaded texstudio twice, the download speed is very low (<45 KB/s), and I always get 503 errors. |
|
Same old, |
|
hi, would it be possible to reopen this issue? i occasionally have to install my own package from flathub, and am often surprise how many times i have to retry it, before i can get it to install. i was pretty glad when you guys mentioned new infrastructure, but this doesn't seem to have made a difference (in my limited experience). i'm with thanks |
|
Possibly related to same root cause as #505, where it may have been returning 404 responses when it's overloaded. Definitely unresolved, and a major usability issue with flathub and flatpak. Would love to see the issue at least acknowledged. |
|
i have found this to be very useful when installing things from flathub, in fact it should probably go in the installation instructions. you'll notice that between 503's, progress is actually being made, so this isn't redownloading the same content over and over. cheers |
|
I think we should figure out the exact cause of this, but also i filed ostreedev/ostree#2022 about how ostree could auto-detect this and retry a few times. |
|
I don't see any 503 errors on our load balancers. Around two hundred 503 errors were reported by Fastly to our stats box, but I don't think it's the issue we're talking about here as it sounds like something more common. |
|
i don't know if this is related, but downloading test builds is remarkably slow too. it's quite typical to experience downloads at about 30k/s. combined with the 503s, a test download can take 3-5 hours to download. |
|
I'm facing the same 503 error on our Travis CI setup when downloading |
|
@sudden6, you may actually find the 503's helpful on travis, travis has a 50 minute job limit, and downloading a flatpak can take much longer than that. if you're not running up against the time limit then just use:
if you're running up against the time limit, the 503's will actually help you out. just list lots of installs like this: by distributing the download over 30 separate 'jobs', no single job takes more than 50 minutes (where as if you just use a single once you've got it downloaded to travis, cache that sucker! and then have a script that only downloads if it's not in the cache: i've found this works quite well. cheers |
|
@jonathon-love Thank you I arrived at the same conclusion, that downloading multiple times is probably the solution. |
|
@sudden6 You should also consider upgrading flatpak to latest 1.4.x or 1.6.x releases. In previous releases there is a regression causing flatpak not to use static deltas. |
works around flathub/flathub#845 (cherry picked from commit 6967783)
|
I'm having this same error trying to install flatpak MuseScore -- see the thread I started here: @flathub/org.musescore.MuseScore#53 @jonathon-love, I'd like to try your "trying again" loop workaround, but I'm clearly getting it wrong ... please help with idiot-proof syntax? Thanks!
|
|
ah yup, my bad, you're missing the repo (in this case try this: |
|
Thanks -- I tried it with and without prefixing "sudo", still missing something:
Tried replacing "do" with "sudo", and got the same syntax error but near 'done' instead of near 'do' |
|
hmm, i'm slightly at a loss. that command works for me:
might have to await someone else's input. |
|
OK, thanks again. Patience is a virtue, they tell me. |
|
FWIW, we've digressed several levels from why the server craps out sometimes to troubleshooting a particular invocation scenario of a hacky retry script. Flathub devs, please consider putting some more attention into fixing the actual 503 problem. If there is a way, it'd be win-win: I suspect having people loop and retry will also not be kind to your servers. |
|
The issue is gone now. Nodes in our load balancer were not keeping up with traffic from CDN; they were replaced with new SSD-backed hosts and number of 503s in CDN logs is down to zero. |
I noticed that when I am using flathub frequently, e.g. installing several apps in a row i've have been getting this error from time to time with some apps (not the same app), in both command line and gnome-software.
This might be rather a question than issue, so is this a security precaution from the server to prevent an overload from certain clients or am I hitting some possible issue with service stability ?
The text was updated successfully, but these errors were encountered: