search

SynoCommunity / spkrepo

Synology Package Repository
http://spkrepo.readthedocs.org
MIT License
152 stars 26 forks source link

Packages server down #104

Closed paulirish closed 9 months ago

paulirish commented 1 year ago

repro url: https://packages.synocommunity.com/homeassistant/20/homeassistant.v20.f42661%5Bapollolake-avoton-braswell-broadwell-broadwellnk-broadwellnkv2-broadwellntbap-bromolow-cedarview-denverton-epyc7002-geminilake-grantley-kvmx64-purley-r1000-v1000%5D.spk?arch=r1000&build=64570

Error 503 first byte timeout

first byte timeout

Error 54113

Details: cache-pao-kpao1770069-PAO 1689102944 418037530

Varnish cache server

publicarray commented 1 year ago

Hey @paulirish thanks for letting us know. The server is still running but for some reason is having a hard time delivering this file. Usually this is when it's overloaded

In the mean time you can download the file from

https://synocommunity.com/package/homeassistant Instead

I'll investigate later if there is anything we can do about it.

publicarray commented 1 year ago

image The X axis is about 1 minute

I think part of the problem is that I believe all online Synology NASs just ask for updates (json) around the same time unfortunately and don't spread the load evenly. I raised a ticked once with them and never heard back or they did not understand.

paulirish commented 1 year ago

In the mean time you can download the file from synocommunity.com/package/homeassistant Instead

it's fine now but.... isnt it the same asset URL regardless? I got this 503 when clicking from that website.. but also noticed that my NAS was pulling from the same URL.

I think part of the problem is that I believe all online Synology NASs just ask for updates (json) around the same time unfortunately and don't spread the load evenly.

Bummer.. Relatedly I'm slightly miffed that within the DSM, all scheduled tasks default to midnight. I know some variability in the cron times would spread the load for whatever. :) cheers

publicarray commented 1 year ago

Hi @Diaoul, Do you know why we use the additional query parameters when downloading a file ?arch=r1000&build=64570? do we need them? If they are not used I can filter them out on Fastly's end and increase the hit ratio. Every time Synology updates their build number the Fastly cache is effectively reset.

EDIT

Never mind. I just checked the configuration and the query parameters are already filtered. I think the server is just overloaded

if (req.url.qs != "" && req.url.ext == "spk")  {
  set req.url = req.url.path; # strip query parameters when requesting a spk package
}
Diaoul commented 1 year ago

I just rebooted the server, let's see if it helps :grimacing:

TimKras commented 1 year ago

Not fixed, i'm getting this error for all downloads here: https://synocommunity.com/package/git

Error 503 Backend unavailable, connection timeout
Backend unavailable, connection timeout

Error 54113
Details: cache-dub4321-DUB 1689577272 1343005206

Varnish cache server
PHENOMICAL commented 1 year ago

Also got this issue. Package Server is still dead. Used link: https://packages.synocommunity.com/inotify-tools/3/inotify-tools.v3.f15047%5Brtd1296-armada37xx%5D.spk

Error 503 Backend unavailable, connection timeout

Backend unavailable, connection timeout
Error 54113

Details: cache-ams12768-AMS 1689588967 1480831573

Varnish cache server
publicarray commented 1 year ago

I just rebooted the server, let's see if it helps grimacing

Hm, I just logged on and our docker containers weren't running.. I've started them now

TimKras commented 1 year ago

I can confirm it is working again. Thanks!

PHENOMICAL commented 1 year ago

I just rebooted the server, let's see if it helps grimacing

Hm, I just logged on and our docker containers weren't running.. I've started them now

Thank you. Also can confirm that it's working.