Cannot update, Server says "111 Connection Refused"

Bug #252271 reported by Markus Mayer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Medibuntu
Fix Released
Medium
Maxence DUNNEWIND

Bug Description

Since (roughly) one day, when I try to run a package list update the update fails with the following error(s):

"W: Konnte http://de.packages.medibuntu.org/dists/hardy/Release.gpg nicht holen Konnte nicht mit de.packages.medibuntu.org:80 verbinden (78.46.32.117). - connect (111 Connection refused)

W: Konnte http://de.packages.medibuntu.org/dists/hardy/free/i18n/Translation-de.bz2 nicht holen Konnte nicht mit de.packages.medibuntu.org:80 verbinden (78.46.32.117). - connect (111 Connection refused)

(...etc...)"

In english this would be something like "could not connect to de.packages.medibuntu.org". I've followed the instructions on the packages page - and http://www.medibuntu.org is working without any problems.

The /etc/apt/sources.list.d/medibuntu.list contains following lines:

## Medibuntu - Ubuntu 8.04 LTS "hardy heron"
## Please report any bug on https://bugs.launchpad.net/medibuntu/
deb http://packages.medibuntu.org/ hardy free non-free
deb-src http://packages.medibuntu.org/ hardy free non-free

This is the second time within a months that the "de" mirror is making trouble.

Markus

Changed in medibuntu:
assignee: nobody → maxenced
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Prosper (prosper-nl) wrote :

I've got the same problem since a day or two: when doing "sudo apt-get update", I get this response:
W: Ophalen van http://packages.medibuntu.org/dists/hardy/free/binary-i386/Packages.gz 404 Not Found [IP: 87.98.249.30 80] is mislukt

W: Ophalen van http://packages.medibuntu.org/dists/hardy/non-free/binary-i386/Packages.gz 404 Not Found [IP: 87.98.249.30 80] is mislukt

The site www.medibuntu.org is up and running, but when calling directly for http://packages.medibuntu.org (just to try) I get a redirect to some blog ... Is there a possible link with the problems where encountering ?

Revision history for this message
Maxence DUNNEWIND (maxenced) wrote :

Hi,

indeed, two of our servers have failed in 2 days ...
We're currently trying to put it up again.
Since both are in de.p.m.org, this dns can't be reached, so please use global dns (packages.m.org).

For the global domain, you just have to retry if you get the bad ip.

Cheers,

Maxence

Revision history for this message
Rafael Gattringer (rafael.gattringer) wrote :

Just for the record, right now the server packages.medibuntu.org = dunnewind.net (88.191.30.43) is very slow.

Example (APT): 72% [152 acroread 3314802/29,5MB 11%] 2500B/s 8h20m24s

Revision history for this message
Rafael Gattringer (rafael.gattringer) wrote :

Workaround: Use http://fr.packages.medibuntu.org/ as mirror. Thanks France. :)

Revision history for this message
Maxence DUNNEWIND (maxenced) wrote :

The 88.191.30.43 is the main server, so it handles a lot of requests (medibuntu rsync from all mirrors, medibuntu apt request, dns requests, and many other things), so it may be slow sometimes.

And, for information, 88.191.30.43 is also in France :) Just that fr. mirrors have really less requests than the general dns :)

Cheers,

Maxence

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

No more comment, so I guess this issue has been fixed.

Changed in medibuntu:
status: Incomplete → Fix Released
Revision history for this message
Jeremy Wilkins (wjeremy) wrote :

Well, this seems to have resurrected as an issue again. The site is yet again unresponsive.

Revision history for this message
powerpanda (zveda2000-gmail) wrote :

I have this problem on my university computer which is behind a proxy, but not on my home computer. I am using Ubuntu Lucid.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.