[SOLVED]Latest Mageia Update Fails

[banjo]

I have tried to install the latest Mageia 5 update twice on my desktop and it has failed the same way both times. It complains that there are missing files. Here is the text that is in the error box:

Code: Select all

Installation failed, some files are missing:
    rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/nonfree/updates/dkms-nvidia-current-352.79-3.mga5.nonfree.x86_64.rpm
    rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/core/updates/chromium-browser-stable-51.0.2704.79-1.mga5.x86_64.rpm
    rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/nonfree/updates/x11-driver-video-nvidia-current-352.79-3.mga5.nonfree.x86_64.rpm
    rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/core/updates/xsltproc-1.1.29-1.mga5.x86_64.rpm
    rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/core/updates/lib64xslt1-1.1.29-1.mga5.x86_64.rpm
    rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/nonfree/updates/nvidia-current-doc-html-352.79-3.mga5.nonfree.x86_64.rpm
    rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/core/updates/lib64png16_16-1.6.22-1.mga5.x86_64.rpm
    rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/core/updates/ldetect-lst-0.1.346.4-1.mga5.x86_64.rpm
    rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/nonfree/updates/nvidia-current-kernel-desktop-latest-352.79-10.mga5.nonfree.x86_64.rpm
You may need to update your urpmi database.

Try to continue anyway?


There are buttons on the dialog box to continue with the update or not. I chose not to continue.

Who is jameswhitby and why is he trying to install a kernel on my system with files that are not there? Is this a suspicious update? I am missing something here. I have been installing the updates all along, and I have not had any trouble with them.

Is there something strange going on here, or do I need to reset something? I have not changed the media sources recently. They are pretty much the defaults. Except for google-chrome, the mirror URLs show $MIRRORLIST in the MCC. Google-chrome is set to http://dl.google.com/linux/chrome/rpm/stable/x86_64

Here is a list of the active media:

Code: Select all

[brian@localhost ~]$ urpmq --list-media active
Core Release2
Core Updates
Nonfree Release2
Nonfree Updates
Tainted Release
Tainted Updates
Core 32bit Release
Core 32bit Updates
Nonfree 32bit Release
Nonfree 32bit Updates
google-chrome


Here are the actual URLs.

Code: Select all

[brian@localhost ~]$ urpmq --list-url
Core Release2 rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/core/release
Core Updates rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/core/updates
Core Release cdrom://x86_64/media/core
Nonfree Release cdrom://x86_64/media/nonfree
Core Release Debug
Core Updates Debug
Core Updates Testing
Core Updates Testing Debug
Core Backports
Core Backports Debug
Core Backports Testing
Core Backports Testing Debug
Nonfree Release2 rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/nonfree/release
Nonfree Release Debug
Nonfree Updates rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/nonfree/updates
Nonfree Updates Debug
Nonfree Updates Testing
Nonfree Updates Testing Debug
Nonfree Backports
Nonfree Backports Debug
Nonfree Backports Testing
Nonfree Backports Testing Debug
Tainted Release rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/tainted/release
Tainted Release Debug
Tainted Updates rsync://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/tainted/updates
Tainted Updates Debug
Tainted Updates Testing
Tainted Updates Testing Debug
Tainted Backports
Tainted Backports Debug
Tainted Backports Testing
Tainted Backports Testing Debug
Core 32bit Release rsync://mageia.jameswhitby.net/mageia/distrib/5/i586/media/core/release
Core 32bit Updates rsync://mageia.jameswhitby.net/mageia/distrib/5/i586/media/core/updates
Core 32bit Updates Testing
Core 32bit Backports                                                                                       
Core 32bit Backports Testing                                                                               
Nonfree 32bit Release rsync://mageia.jameswhitby.net/mageia/distrib/5/i586/media/nonfree/release           
Nonfree 32bit Updates rsync://mageia.jameswhitby.net/mageia/distrib/5/i586/media/nonfree/updates           
Nonfree 32bit Updates Testing                                                                             
Nonfree 32bit Backports                                                                                   
Nonfree 32bit Backports Testing                                                                           
Tainted 32bit Release                                                                                     
Tainted 32bit Updates
Tainted 32bit Updates Testing
Tainted 32bit Backports
Tainted 32bit Backports Testing
google-chrome http://dl.google.com/linux/chrome/rpm/stable/x86_64


I guess that explains the "jameswhitby" connection. Is this a legitimate mirror?

Thanks for any help.
Banjo

[benmc]

looks like you have a poorly synced mirror.
(Edit) have a look here for the relative update status of your mirror: https://mirrors.mageia.org/status
I too have had problems with "jameswhitby.net".

I have changed to a specific mirror- added through MCC

have a look here for mirrors http://mirrors.mageia.org/.

personally, I have found "distrib-coffee.ipsl.jussieu.fr" to be very reliable

[banjo]

Thanks for the reply. This was very helpful.

Because I am in the U.S. I added mirror.easthsia.com, which states that its source is distrib-coffee.ipsl.jussieu.fr.

This caused the duplication of media in my MCC. Here are the current active media sites:

Code: Select all

Core Release2
Core Updates
Nonfree Release2
Nonfree Updates
Tainted Release
Tainted Updates
Core 32bit Release
Core 32bit Updates
Nonfree 32bit Release
Nonfree 32bit Updates
google-chrome
Core Release (distrib1)
Core Updates (distrib3)
Nonfree Release (distrib11)
Nonfree Updates (distrib13)
Tainted Release (distrib21)
Tainted Updates (distrib23)
Core 32bit Release (distrib31)
Core 32bit Updates (distrib32)
Nonfree 32bit Release (distrib36)
Nonfree 32bit Updates (distrib37)
Tainted 32bit Release (distrib41)
Tainted 32bit Updates (distrib42)


I'm not sure what to do with all these. Turn off the old ones? Move the new ones up in the list?

What are the (distrib) numbers after the media names?

Maybe I will try turning off the old selections, rebooting, and then see if the update comes through again. Suggestions?

I can't do this right now because I am booked all day for events. I will try to get back to this at the end of the day or tomorrow when I have more time to deal with it.

Thanks again for the help.

Banjo
(_)=='=~

[benmc]

hi Banjo.

you have the choice of just un-ticking your old mirror media and then just ticking the new ones.

or / and deleting the old ones.

that I am aware of, the # has no value other than a reference #

[banjo]

I finally got time to address this update question. Here is what I did.

I deselected the mageia.jameswhitby.net sources and left only the mirror.easthsia.com sources enabled. Then I rebooted the computer to make sure that there was no confusion about where the repository was. Shortly after I logged in from the reboot, the update notice appeared. I ran the update, and it went through without a hitch.

Another reboot seems to have worked fine as well. I always worry whether or not the system will come back up when I install an update that contains the word "nvidia" or "kernel".

Anyway, the new mirror seems to have improved the situation. Thank you for the help.

Marking this one SOLVED

Banjo
(_)=='=~

[doktor5000]

I always worry whether or not the system will come back up when I install an update that contains the word "nvidia" or "kernel".

Why is that?

[banjo]

I am forced to work on a Windows 7 system at work, and the worry carries over. I am not going to rant, but the last Windows update at work took 1 1/2 hours to reboot.

Mageia has always been good to go, and it is nothing like Windows, but the worry carries over. Updating the kernel or the graphics driver is akin to editing the Registry (which I have done). If it doesn't happen exactly right, I could own a brick. Errors during updates make me nervous. I do not have the deep system knowledge that would be necessary to repair a failed kernel or graphics driver update.

Banjo
(_)=='=~

[doktor5000]

When did a kernel update or graphics driver update fail the last time on Mageia for you?

[banjo]

I work in the guts of complex computer technology every day (not in Linux), and I have discovered that catastrophic failures happen most often just after I have become complacent that everything is stable and nothing bad is going to happen. I have also discovered that the more I think I know about how this stuff works, the less I actually do know.

To answer the specific question about Mageia, that has not happened. That is where the complacency comes from.

However, I have had Kernels that would not boot on a regular basis. It was an intermittent problem. Sometimes yes; sometimes no. The older kernel would boot; the newer one would not.... except sometimes.

After weeks of trouble shooting, I figured out that it was a failing disk drive that somehow landed on some of the sectors that had something to do with that kernel. The disk drive went into the trash; problem solved.

So nothing went wrong with the update after all. But that knowledge comes as perfect hindsight. At the time that it happened, it was an unknown.

I am not finding fault with Mageia or any of the outstanding work that is being done in this effort. As I said before, the caution comes from years (decades) of being buried in recalcitrant technology that fails in the most surprising and creative ways at the most inopportune time. It is a general caution, not something specific to Mageia updates.

Banjo
(_)=='=~