Medibuntu offline
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Medibuntu |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Unable to connect to Medibuntu. When running Software Updater, I get the following error message:-
W:Failed to fetch http://
, W:Failed to fetch http://
, E:Some index files failed to download. They have been ignored, or old ones used instead.
I tried 'pinging' Medibuntu and got the following message
ping -c 3 packages.
PING packages.
--- packages.
3 packets transmitted, 0 received, 100% packet loss, time 2014ms
I am running Ubuntu 12.04 (64 bit).
Gauvain Pocentek (gpocentek) wrote : | #1 |
Colin Mills (cm006a5077) wrote : | #2 |
Still getting the same error message.
I was able to access Medibunu, until about 24 hours ago.
I do not have any filters on (apart from the firewall, which I disabled, but still unable to connect to Medibuntu), and have made no changes to Ubuntu 12.04 since yesterday, other than to run the system updates.
Gauvain Pocentek (gpocentek) wrote : | #3 |
Could you give me your IP address (here or by mail if you prefer)? I'll check on the servers if something is blocking you.
Colin Mills (cm006a5077) wrote : | #4 |
May be a similar bug to the one reported in the Ubuntu forum post (http://
Colin Mills (cm006a5077) wrote : | #5 |
Gauvain
Forgot to mention that I have emailed you my IP address.
Ian McMichael (ian-sigma-uk) wrote : | #6 |
Same for me for the last couple of days from both Virgin cable and BE ADSL in the UK.
Gauvain Pocentek (gpocentek) wrote : | #7 |
Looks like a routing issue. I'm afraid I can't do much about it...
Colin Mills (cm006a5077) wrote : | #8 |
Could you explain what this routing error could be?
I ask because I am able to update all my other launchpad repos and have just installed a new ppa from launchpad.
I also tried editing the file /etc/apt/
Ian McMichael (ian-sigma-uk) wrote : | #9 |
I'm cannot concur with the routing issue diagnosis. Having tried multiple UK based networks, I find it unlikely. Also, I can always get ICMP traffic to packages.
ian@custard:~$ ping packages.
PING packages.
64 bytes from faraway.
64 bytes from faraway.
64 bytes from faraway.
64 bytes from faraway.
64 bytes from faraway.
64 bytes from faraway.
64 bytes from faraway.
^C
--- packages.
7 packets transmitted, 7 received, 0% packet loss, time 6007ms
rtt min/avg/max/mdev = 13.950/
ian@custard:~$ sudo apt-get update
[sudo] password for ian:
Hit http://
Ign http://
Ign http://
Ign http://
Hit http://
Get:1 http://
Hit http://
Hit http://
Hit http://
Hit http://
Get:2 http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Ign http://
Ign http://
Ign http://
Hit http://
Colin Mills (cm006a5077) wrote : | #10 |
It would appear that this problem has occurred before (see http://
I quote
Update: there's an even easier way to fix this (thanks to defrysk). Apparently only the DNS are having issues so you can fix Medibuntu by keeping original address and pasting this in a terminal:
echo "88.191.101.8 packages.
This puts the Medibuntu IP address in the hosts file.
I restarted the system, after running the command in a terminal, and I am now able to access the Medibuntu reepository.
So problem appears to be associated with DNS.
Andy Bovett (abovett) wrote : | #11 |
I'm also getting this problem. Strayngely, I can get the package lists manually with wget, but apt-get update or aptitude update fails.
So, for example, this works:
wget http://
even though when I do apt-get update, I have this error (amongst others):
W: Failed to fetch http://
Unable to connect to packages.
Gauvain Pocentek (gpocentek) wrote : | #12 |
Could you try with this apt configuration instead of the current one (in /etc/apt/
deb http://
Only the port changes. This will use the web server directly, bypassing the load balancer to see if the problems comes from there.
Colin Mills (cm006a5077) wrote : | #13 |
Replacing the apt configuration with " deb http://
Hope this helps
Ian McMichael (ian-sigma-uk) wrote : | #14 |
No joy here on port 8080 I'm afraid:
Err http://
Err http://
Unable to connect to packages.
Fetched 2,314 B in 2min 0s (19 B/s)
Reading package lists... Done
W: Failed to fetch http://
W: Failed to fetch http://
W: Some index files failed to download. They have been ignored, or old ones used instead.
That may be because the IP address is currently unreachable via ICMP echo:
PING packages.
^C
--- packages.
23 packets transmitted, 0 received, 100% packet loss, time 22175ms
Here's the network path from me to the repository server:
traceroute to packages.
1 gatekeeper.
2 * * *
3 * * *
4 linx-6k-
5 bzn-crs16-
6 dedibox-
7 88.191.2.69 (88.191.2.69) 21.406 ms * 15.694 ms
8 faraway.
Let me know if there's anything else I can test for you?
Giuseppe Terrasi (giuseppeterrasi-deactivatedaccount) wrote : | #15 |
I'm on precise. Repository, as is, not available from three days.
This fix my problem:
echo "88.191.101.8 packages.
Andy Bovett (abovett) wrote : | #16 |
Using http://
Andy Bovett (abovett) wrote : | #17 |
Correction to my above comment: using http://
Ian McMichael (ian-sigma-uk) wrote : | #18 |
Something must have changed. Port 8080 is now working for me also and I've changed nothing from the post 8 hours ago. Just retried apt-get update and it connects fine. A web server re-configuration?
neclepsio (neclepsio) wrote : | #19 |
apt-get still does not work for me (in Italy with Fastweb).
The web server correctly fetches the Packages file using the browser.
neclepsio (neclepsio) wrote : | #20 |
ps: using 8080 port works.
Andy Bovett (abovett) wrote : | #21 |
I'm now getting different problems depending on which version of Ubuntu I'm using.
oneiric: port 8080 still works
precise: port 8080 does NOT work but putting the IP address in the hosts file does
Something has changed because eariler port 8080 was working on all PCs
Andy Bovett (abovett) wrote : | #22 |
Getting worse: neither using port 8080 or adding medibuntu to the hosts file work on any of my PCs now :(
Gauvain Pocentek (gpocentek) wrote : | #23 |
Andy, does wget still work?
Dirk T. (dverbeek) wrote : | #24 |
I had the issue from Poland and Denmark using Kubuntu 12.04 even though mtr gave a reasonable ping to both medibuntu.org and packages.
The solution of hardcoding the hosts file works.
Colin Mills (cm006a5077) wrote : | #25 |
For any one who has a similar problem to Andy, where neither of the two options work, there is one more option . Go to my post (#10) where I reported on the "echo "88.191.101.8 packages.
The website lists alternative Medibuntu mirror sites. Websites Mirror1 and Mirror3 still support all Ubuntu versions, including Precise:-
http://
ftp://ftp.
Just follow the installation instructions (remember to replace "Lucid" whatever Ubuntu version you're using).
When the main repository is working you can always change it back.
Dirk T. (dverbeek) wrote : | #26 |
I just noticed the IP that doesn't work for me is: 88.191.127.22
Gauvain Pocentek (gpocentek) wrote : | #27 |
I still can't reproduce the problem on my side.
For reporters, could you run the update with debug options:
apt-get update -o Debug::
Please run this without any workaround (don't use port 8080, don't set an IP in /etc/hosts).
Thanks.
Changed in medibuntu: | |
status: | New → Confirmed |
Colin Mills (cm006a5077) wrote : | #28 |
I hadto run as root i.e.
sudo apt-get update -o Debug::
Whatever the command does, it seems to have worked. I no longer get the "Unable to connect to Medibuntu" error message.
Thanks
Hope this helps.
Ian McMichael (ian-sigma-uk) wrote : | #29 |
Here's (medibuntu bits of) the debug trace from my system with the port 8080 removed so that I'm back through the load balancer:
GET /dists/
Host: packages.
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
GET /dists/
Host: packages.
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
HTTP/1.0 403 Forbidden
Cache-Control: no-cache
Connection: close
Content-Type: text/html
GET /dists/
Host: packages.
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
GET /dists/
Host: packages.
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
HTTP/1.1 404 Not Found
Date: Wed, 25 Apr 2012 09:17:37 GMT
Server: Apache/2.2.14 (Ubuntu)
Content-Length: 358
Keep-Alive: timeout=15, max=61
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
HTTP/1.1 404 Not Found
Date: Wed, 25 Apr 2012 09:17:37 GMT
Server: Apache/2.2.14 (Ubuntu)
Content-Length: 340
Keep-Alive: timeout=15, max=60
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
GET /dists/
Host: packages.
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
GET /stebbins/
Host: ppa.launchpad.net
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
GET /stebbins/
Host: ppa.launchpad.net
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
HTTP/1.1 404 Not Found
Date: Wed, 25 Apr 2012 09:17:37 GMT
Server: Apache/2.2.14 (Ubuntu)
Content-Length: 337
Keep-Alive: timeout=15, max=59
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
GET /wfg/0ad/
Host: ppa.launchpad.net
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
HTTP/1.0 403 Forbidden
Cache-Control: no-cache
Connection: close
Content-Type: text/html
GET /dists/
Host: packages.
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
GET /dists/
Host: packages.
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
GET /dists/
Host: packages.
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
HTTP/1.1 404 Not Found
Date: Wed, 25 Apr 2012 09:17:37 GMT
Server: Apa...
Andy Bovett (abovett) wrote : | #30 |
Gauvain Pocentek (gauvainpocentek) wrote on 2012-04-23:
> Andy, does wget still work?
Sorry for the delay in replying. Yes, it does.
In fact, everything seems to be back to normal (at the moment anyway). I've removed the extra entry from my hosts file, removed the port number from the sources.list fileso I'm going through the load balancer, and everything's working on the two PCs I've tried so far (one precise, one oneiric).
Royce King (king-royce) wrote : | #31 |
I have a fresh install of 12.04 and was getting this error and none of the suggestions worked. When I looked at my sources.list of all the ones that were working precise is spelled with a lower case p. So I changed the Precise to precise and all was well. no more errors.
Gauvain Pocentek (gpocentek) wrote : | #32 |
Is this problem still occurring for some of you?
I've not add more reports since the 12.04 release, so I think everything works as expected.
Colin Mills (cm006a5077) wrote : | #33 |
Everything is now working normally. I am able to install the Medibuntu repository without resorting to any of the 'fixes'
Thanks
Ian McMichael (ian-sigma-uk) wrote : | #34 |
Yes, all fine here without any workarounds for the past few days too. Thanks.
Gauvain Pocentek (gpocentek) wrote : | #35 |
Thanks for the feedback.
I'm marking the bug as fixed, feel free to reopen if it still happens.
Changed in medibuntu: | |
status: | Confirmed → Fix Released |
Johan Lee (leeinglun) wrote : | #36 |
Help me,
Same problem again here,
W: Failed to fetch http://
W: Failed to fetch http://
W: Failed to fetch http://
W: Failed to fetch http://
E: Some index files failed to download. They have been ignored, or old ones used instead.
frankster (wtfrank) wrote : | #37 |
I'm using squid-deb-proxy and getting this error. I can use wget to download the files listed in the debug output, but just not apt!
packages.
PING packages.
64 bytes from faraway.
GET http://
Host: packages.
Cache-Control: max-age=0^M
Accept: text/*^M
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
^M
HTTP/1.0 403 Forbidden^M
Server: squid/3.1.19^M
Mime-Version: 1.0^M
Date: Tue, 27 Nov 2012 18:17:35 GMT^M
Content-Type: text/html^M
Content-Length: 3305^M
X-Squid-Error: ERR_ACCESS_DENIED 0^M
Vary: Accept-Language^M
Content-Language: en^M
X-Cache: MISS from squid-deb-proxy^M
X-Cache-Lookup: NONE from squid-deb-
Via: 1.0 squid-deb-proxy (squid/3.1.19)^M
Connection: keep-alive^M
^M
GET http://
Host: packages.
Cache-Control: max-age=0^M
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
^M
HTTP/1.0 403 Forbidden^M
Server: squid/3.1.19^M
Mime-Version: 1.0^M
Date: Tue, 27 Nov 2012 18:17:35 GMT^M
Content-Type: text/html^M
Content-Length: 3285^M
X-Squid-Error: ERR_ACCESS_DENIED 0^M
Vary: Accept-Language^M
Content-Language: en^M
X-Cache: MISS from squid-deb-proxy^M
X-Cache-Lookup: NONE from squid-deb-
Via: 1.0 squid-deb-proxy (squid/3.1.19)^M
Connection: keep-alive^M
^M
GET http://
Host: packages.
Cache-Control: max-age=0^M
Accept: text/*^M
User-Agent: Debian APT-HTTP/1.3 (0.8.16~
^M
frankster (wtfrank) wrote : | #38 |
So the solution in my case was to add entries for the medibuntu servers to /etc/squid-
Jeff Q (jeffq) wrote : | #39 |
This still seems to be a problem. I've gotten these errors frequently over the past year, and finally seem to have stopped them by switching to the Costa Rican mirror:
deb http://
Neither the :8080 port change nor the IP-address substitution above worked for me. The first gave me same "Failed to fetch" errors. The latter I didn't specifically try because browsing:
by itself didn't get a response. (At least the other URLs could be accessed within a browser, even though they didn't repsond to apt-get's fetches.) Besides, relying on an unchanging IP doesn't seem wise, especially since people will be looking up this info for years to come.
Changing mirrors in /etc/apt/
Changed in medibuntu: | |
assignee: | nobody → JmAbuDabi (dambldor91) |
assignee: | JmAbuDabi (dambldor91) → nobody |
Emeric Vigier (emeric-vigier) wrote : | #40 |
I just switched to ubuntu-12.04 and faced this issue.
Medibuntu has gone down. So 12.04 users should remove associated ppa entries.
https:/
Everything works fine for me. The servers are up.
Please check again, and make sure that you don't have filters of some sort.