Forum archive
Turnkey Core 15.0 new install -- Failed to fetch archive.turnkeylinux.org....
apt-get update
Ign:1 http://deb.debian.org/debian stretch InRelease
Get:2 http://security.debian.org stretch/updates InRelease [94.3 kB]
Err:3 http://archive.turnkeylinux.org/debian stretch-security InRelease
Could not connect to archive.turnkeylinux.org:80 (54.83.15.172). - connect (111: Connection refused)
Err:4 http://archive.turnkeylinux.org/debian stretch InRelease
Unable to connect to archive.turnkeylinux.org:http:
Hit:5 http://deb.debian.org/debian stretch Release
Hit:6 http://dl.ubnt.com/unifi/debian stable InRelease
Get:8 http://security.debian.org stretch/updates/main amd64 Packages [492 kB]
Fetched 586 kB in 0s (1192 kB/s)
Reading package lists... Done
W: Failed to fetch http://archive.turnkeylinux.org/debian/dists/stretch-security/InRelease Could not connect to archive.turnkeylinux.org:80 (54.83.15.172). - connect (111: Connection refused)
W: Failed to fetch http://archive.turnkeylinux.org/debian/dists/stretch/InRelease Unable to connect to archive.turnkeylinux.org:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.
I have used this ISO a number of times in the last 2 weeks. I have also tested a couple of these installs and they also get the same error.
Replies (16)
Thanks so much for reporting!
Reply 1Issue is now resolved
Reply 2The TurnKey apt archive should now be working as expected. Thanks for the patience.
Thanks Ralf - I've pinged Alon
Reply 3Thanks for the heads up Ralf. I've pinged Alon but unfortunately, it's 11pm Saturday in Israel ATM, so it'll probably be ~8+/- hours before he'll get to it.
It's back up...
Reply 4Unfortunately it's a known issue
Reply 5Please see my comment on another thread.
Should be back up now
Reply 6Please see my comment on the GitHub issue for further details.
Unfortunately it's a known issue
Reply 7Please see my comment on another thread.
Should be back up now
Reply 8Please see my comment on the GitHub issue for further details.
Looks like you lost internet
Reply 9It looks like you lost your internet connection? Otherwise, perhaps a DNS failure?
To see if it's still a problem, please manually run:
apt update
update on jellyfin, Simple Network Attached Media Storage
Reply 10CRON-APT RUN [/etc/cron-apt/config]: Tue Sep 20 12:33:01 UTC 2022 CRON-APT SLEEP: 3599, Tue Sep 20 13:33:00 UTC 2022 CRON-APT ACTION: 0-update CRON-APT LINE: /usr/bin/apt-get -o quiet=1 update -o quiet=2 W: Failed to fetch http://archive.turnkeylinux.org/debian/dists/buster-security/InRelease Connection failed [IP: 54.83.15.172 80] W: Failed to fetch http://security.debian.org/dists/buster/updates/InRelease Connection failed [IP: 199.232.138.132 80] W: Failed to fetch http://archive.turnkeylinux.org/debian/dists/buster/InRelease Connection failed [IP: 54.83.15.172 80] W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Connection failed [IP: 199.232.138.132 80] W: Some index files failed to download. They have been ignored, or old ones used instead.... and so on Hello. I have been getting these error messages for some time now when updating the Jellyfin media server. What is the problem?
Thanks for reporting!
Reply 11Thanks very much for reporting. I've just restarted the webserver. A quick browse through the logs, it looks like it was under attack (or perhaps just a poorly coded bot?). The webserver coped with it for a while, but eventually crashed.
I've restarted it now and all appears to be ok. Hopefully they don't come back anytime soon. Once we're into the new year, I'll look into this closer. IPv6 support is on my agenda anyway, so while I'm working on the server, I'll look closer at hardening against this sort of thing.
Regardless, it all seems to be working fine now.
Sorry for bump it up, but looks its down again
Reply 12I got this log, it looks its down again.
CRON-APT RUN [/etc/cron-apt/config]: Tue Dec 20 06:33:02 UTC 2022
CRON-APT SLEEP: 883, Tue Dec 20 06:47:45 UTC 2022
CRON-APT ACTION: 0-update
CRON-APT LINE: /usr/bin/apt-get -o quiet=1 update -o quiet=2
W: Failed to fetch http://archive.turnkeylinux.org/debian/dists/bullseye-security/InRelease Could not connect to archive.turnkeylinux.org:80 (54.83.15.172). - connect (111: Connection refused)
W: Failed to fetch http://archive.turnkeylinux.org/debian/dists/bullseye/InRelease Unable to connect to archive.turnkeylinux.org:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.
CRON-APT ACTION: 5-install
CRON-APT LINE: /usr/bin/apt-get -o quiet=1 autoclean -y
Reading package lists...
Building dependency tree...
Reading state information...
CRON-APT LINE: /usr/bin/apt-get -o quiet=1 dist-upgrade -y -o APT::Get::Show-Upgraded=true -o Dir::Etc::sourcelist=/etc/apt/sources.list.d/security.sources.list -o Dir::Etc::sourceparts=nonexistent -o DPkg::Options::=--force-confdef -o DPkg::Options::=--force-confold
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Thanks for confirming. Should be good now.
Reply 13Please see my comment above.
Can't access again right now.
Reply 14Yes it was... :(
Reply 15Yes it was... :( Thanks to you (and others) that reported it.
As of about 24 hours ago it should be back up and running again.
Looks like the http://archive
Reply 16Looks like the http://archive.turnkeylinux.org/debian is down again
UPDATE: Issue has now been resolved!
It seems that our apt archive server has had a failure! :(
The server itself appears to still be running ok, but it's (obviously) not hosting any of the archive files/filesystem.
Unfortunately, I don't have direct access to that machine, so I'm not even sure what has gone wrong and there is nothing I can do immediately.
However, I have contacted my colleague (who does have access) and hopefully he'll resolve it ASAP. Having said that, it's currently early hours of the morning in his timezone - so no clear ETA as of yet. I expect that he will make this a priority (it's a critical issue!).
As an immediate workaround, you could disable the TurnKey repos in the sources.list & security.sources.list files. To do that, edit the 2 above mentioned files (you'll find them in /etc/apt/sources.list.d) and preface each line that mentions "archive.turnkeylinux.org" with a '#'. I.e. these:
Become like these:
Obviously you won't be able to update any TurnKey custom packages, but it will get you going (and you will be able to install Debian packages ok). Don't forget to re-enable them after the issue is fixed though!
I plan to post back with an update ASAP (i.e. when it's fixed), but I will be busy over the weekend, so it may be a little delayed. If you do comment out the apt repo in your sources.lists, the easiest way to double check (from the commandline) is via curl:
If it's still not fixed, you'll get a response like "Failed to connect to archive.turnkeylinux.org port 80: Connection refused".
Alternatively, just try to browsing to http://archive.turnkeylinux.org. If you get an "ERR_CONNECTION_REFUSED" (or similar) it's still broken.
Also, I've opened an issue on our tracker and assigned my colleague Alon, he'll hopefully close that issue once it's been resolved.