| Summary: | The distrib-coffee.ipsl.jussieu.fr mirror is out-of-date | ||
|---|---|---|---|
| Product: | Websites | Reporter: | Frédéric "LpSolit" Buclin <LpSolit> |
| Component: | mirrors.mageia.org | Assignee: | Sysadmin Team <sysadmin-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | major | ||
| Priority: | High | CC: | atelier-bugs, davidwhodgins, filip.komar, fri, kcpammer, mageia, mageia, petlaw726, qa-bugs, sysadmin-bugs |
| Version: | trunk | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://mirrors.mageia.org/status | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Bug Depends on: | 17400 | ||
| Bug Blocks: | |||
|
Description
Frédéric "LpSolit" Buclin
2024-03-24 13:54:39 CET
Everybody can contact the server admin. The contact adress is directly on the front page! (In reply to sturmvogel from comment #1) > Everybody can contact the server admin. The contact adress is directly on > the front page! FYI Thomas Andrews the QA leader already did it Blog and forum, and discuss ml posts should go out explaining that the problem. People should be warned to check https://mirrors.mageia.org/status for a mirror that is syncing. Once they pick one to use, they can remove their current sources with "urpmi.removemedia -a" (as root) and then add a specific mirror https://wiki.mageia.org/en/Installing_and_removing_software#Adding_a_specific_Media_Mirror CC:
(none) =>
atelier-bugs, davidwhodgins
Dave Hodgins
2024-03-29 18:27:25 CET
CC:
(none) =>
qa-bugs It would be good if the various Mageia tools that update packages (e.g. mgaapplet, rpmdrake) were able to detect if a repository is out of date. Maybe the tools could look for a TIMESTAMP file in the repositories that is updated daily even if there are no new package updates, and warn the user if the repository is too out-of-date. The warning message could suggest using another up-to-date mirror, possibly with some usability features like showing a list of up-to-date mirrors and a button to use the selected mirrors. CC:
(none) =>
mageia This is a too frequent problem for this important functionality. More than once a year more than one mirror have some problem. There was a proposal Bug 27623 - Fallback mirrors CC:
(none) =>
fri since the mirror of free seems to resist, a temporarily solution is to add to /etc/yum.repos.d/mageia-x86_64.repo the uncommented line: baseurl=http://ftp.free.fr/mirrors/mageia.org/distrib/9/x86_64/media/core/<release, updates>/ and the same for nonfree, tainted, i586 ... where the line above must be adapted to the different cases it works well as long as the free mirror will be functional compare to ubuntu mirrors: https://launchpad.net/ubuntu/+archivemirrors There are a lot of open bugs on that topic: https://bugs.mageia.org/buglist.cgi?quicksearch=mirror We need more permanent solution. Like the one in bug 17400 or similar. CC:
(none) =>
filip.komar we have to many mirrors using distrib-coffee.ipsl.jussieu.fr as master (and it is not the first time it failed) how can we prevent mirrors syncing from out of date mirrors or switching to a working one? can mirrorbrain provide a sync link for a protocol too, so it chooses an update mirror for sync? btw ftp-stud.hs-esslingen.de uses "distrib-coffee.ipsl.jussieu.fr" too as a source - the status page is not correct. Thankfully we were not hit by xz-issue, as many would not get our updates at the moment. CC:
(none) =>
mageia I wonder if we not have again an issue like the ibiblio.org https://bugs.mageia.org/show_bug.cgi?id=30089#c28 ? I don't understand: some mirrors, as https://mageia.c3sl.ufpr.br/ and some others, are marked as being out of use since 2024-04-02 at 9:28 p.m.; it's impossible, since today, april, 3rd at 1:00 p.m. Paris time, they were green thank for explanation (In reply to peter lawford from comment #13) > I don't understand: some mirrors, as https://mageia.c3sl.ufpr.br/ and some > others, are marked as being out of use since 2024-04-02 at 9:28 p.m.; it's > impossible, since today, april, 3rd at 1:00 p.m. Paris time, they were green > thank for explanation The status legend is somewhat misleading. When a mirror shows "Less than 2 days old", it does NOT mean it's been 12 to 48 hours since it last synced. The status is based on the age of the last package that was synced, not when the last check for updates occurred. If a repo has no updates for 12 hours, and then an update is built, then all mirrors immediately become orange in status as the date/time of the hdlist and package files that it has are at least 12 hours old. It will turn green again as soon as the mirror syncs that repo again. It works this way because the status page uses the date/time of the files on the mirrors. It does NOT check the log on the main server to see when a mirror last checked for updates. Using the log on the main server would only be possible for the tier 1 mirrors. As the logs on the tier 1 mirrors are not accessible, it can not be done that way for other mirrors. For simplicity, the status of all mirrors is based on the age of the hdlist files on the mirror. (In reply to Marc Krämer from comment #11) > we have to many mirrors using distrib-coffee.ipsl.jussieu.fr as master (and > it is not the first time it failed) > how can we prevent mirrors syncing from out of date mirrors or switching to > a working one? can mirrorbrain provide a sync link for a protocol too, so it > chooses an update mirror for sync? > > btw ftp-stud.hs-esslingen.de uses "distrib-coffee.ipsl.jussieu.fr" too as a > source - the status page is not correct. > > Thankfully we were not hit by xz-issue, as many would not get our updates at > the moment. what is xz-issue? (In reply to peter lawford from comment #15) > (In reply to Marc Krämer from comment #11) > > we have to many mirrors using distrib-coffee.ipsl.jussieu.fr as master (and > > it is not the first time it failed) > > how can we prevent mirrors syncing from out of date mirrors or switching to > > a working one? can mirrorbrain provide a sync link for a protocol too, so it > > chooses an update mirror for sync? > > > > btw ftp-stud.hs-esslingen.de uses "distrib-coffee.ipsl.jussieu.fr" too as a > > source - the status page is not correct. > > > > Thankfully we were not hit by xz-issue, as many would not get our updates at > > the moment. > > what is xz-issue? https://lwn.net/Articles/967180/ But mageia is not affected https://blog.mageia.org/en/2024/03/30/about-backdoor-security-alert-for-xz/ it looks like the server started syncing again. https://mirrors.mageia.org/status it is not up-to-date yet it seems that coffee-jussieu.ipsl out of synch again where is gone the distrib-coffee.ipsl.jussieu.fr mirror? it no loger appear in the list of mageia's mirrors distrib-coffee.ipsl.jussieu.fr is back and green |