When trying to update from the http://mageia.balinor.net/ Canadian server, it returns errors. It is listed as "old or broken" on the server status page http://mirrors.mageia.org/status. Unfortunately, when adding media servers through the MCC update module, if located in Canada, the http://mageia.balinor.net/ is picked but then sends error messages when one tries to update. I help out approx. 30-40 people with their Mageia setups -- many of whom are 70-80yrs of age and they are unable to update the media servers in the MCC to another mirror. I am in the process of updating them individually. Is there a way to remove the http://mageia.balinor.net/ site and have anyone who is going to that mirror, have it point to another mirror site with an up-to-date mirror? Otherwise, does this mean that all of the Canadian users need to go into the MCC and update to another server? Marc
CC: (none) => marc
(In reply to Marc Paré from comment #0) > When trying to update from the http://mageia.balinor.net/ Canadian server, > it returns errors. It is listed as "old or broken" on the server status page > http://mirrors.mageia.org/status. > > Unfortunately, when adding media servers through the MCC update module, if > located in Canada, the http://mageia.balinor.net/ is picked but then sends > error messages when one tries to update. Assigning to sysadmin team, because I think removing the mirror from http://mirrors.mageia.org/ will fix this. > > I help out approx. 30-40 people with their Mageia setups -- many of whom are > 70-80yrs of age and they are unable to update the media servers in the MCC > to another mirror. I am in the process of updating them individually. > > Is there a way to remove the http://mageia.balinor.net/ site and have anyone > who is going to that mirror, have it point to another mirror site with an > up-to-date mirror? Nor sure that can be done on our side. However, "dig mageia.balinor.net" returns mageia.balinor.net. 300 IN A 213.186.33.5 and "whois 213.186.33.5" returns inetnum: 213.186.33.0 - 213.186.33.255 netname: OVH descr: OVH SAS descr: Shared Hosting Servers descr: http://www.ovh.com Maybe you can contact OVH and ask them, since "Balinor" seems to no longer use their services? > Otherwise, does this mean that all of the Canadian users > need to go into the MCC and update to another server? @ Thierry *If* OVH is willing to (temporarily) do a redirect, is it then possible to push an update which replaces this mirror with a better one, for users who had this one configured? (I was about to clone this report for that, but if it's impossible, or if OVH refuses, then it's wasted time)
Product: Mageia => WebsitesCC: (none) => marja11, sysadmin-bugs, thierry.vignaudComponent: RPM Packages => mirrors.mageia.orgVersion: 5 => trunkAssignee: bugsquad => sysadmin-bugs
If they use mirrorlist, we don't have anything to do. The redirect will take care of that and the mirrors cache will be fixed the next time it's updated
Bellow there's another obsolete mirror listed in http://mirrors.mageia.org/api/mageia.5.i586.list http://mageia.webconquest.com/
CC: (none) => filip.komarSummary: Canadian server not serving updates => Some mirrors are obsolete, so not serving updates
(In reply to Filip Komar from comment #3) > Bellow there's another obsolete mirror listed in > http://mirrors.mageia.org/api/mageia.5.i586.list > > http://mageia.webconquest.com/ That one's owned by remmy, and both Mga5 and cauldron are up to date now, for all arches, according to http://mirrors.mageia.org/status CC'ing remmy
CC: (none) => remco
(In reply to Marja van Waes from comment #4) > (In reply to Filip Komar from comment #3) > > Bellow there's another obsolete mirror listed in > > http://mirrors.mageia.org/api/mageia.5.i586.list > > > > http://mageia.webconquest.com/ > > That one's owned by remmy, and both Mga5 and cauldron are up to date now, > for all arches, according to > http://mirrors.mageia.org/status > > CC'ing remmy Indeed is fine. I was only looking at Last Modified time of mageia_timestam file which is from 2016 ;).
(In reply to Filip Komar from comment #5) > Indeed is fine. I was only looking at Last Modified time of mageia_timestam > file which is from 2016 ;). Ohhh, blunder. It's just a few hours back :(. Sorry for the noise. So for now only http://mageia.balinor.net/ is lost.
We could set this as old, but it is an ever recurring problem... Also see Bug 3166 - use mirrorbrain for download management (for better mirror choosing and for DNF)
CC: (none) => fri