[SOLVED] After online upgrade to v. 9, unable to update
MageiaThis forum is for the discussion of Mageia Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I did follow one of the suggestions. I opened drakconf, went to Software Management-->Configure media sources for install and update-->File-->Add a custom medium and added a repo from the repo list above. It did not work.
Before I do a reinstall, I thought should ask whether anyone has a suggestion as to how I could fix this without a reinstall.
I will add that when I did an online upgrade from v. 7 to v. 8, it went flawlessly.
If a transaction proceeds to remove /etc/resolv.conf, not found errors become expected behavior. I've done multiple Mageia updates in the past two days, and exactly this happened in one of them.
In a way, I did that in advance. /etc/resolv.conf here is replicated as /etc/resolv.conf.latest, so I need only copy the copy back over the broken one, or into the void left by whatever removal transaction.
Thank you all for your responses. I'm been late getting back to this thread because, frankly, my brain is tired.
The odd thing is that websites seem to resolve properly.
I looked at my resolve.conf and found this. It points to a site belonging to my ISP.
Code:
# cat resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 68.105.28.11
nameserver 68.105.29.11
nameserver 68.105.28.12
I did a web search for "edit reolve.conf mageia" and the results made my brain even more tired.
Can someone point me to nice, concise, clear tutorial on how to make the edit?
mrmazda, you said:
Quote:
If a transaction proceeds to remove /etc/resolv.conf, not found errors become expected behavior. I've done multiple Mageia updates in the past two days, and exactly this happened in one of them.
Just seeking clarity, by "remove" do you mean "delete"?
Just seeking clarity, by "remove" do you mean "delete"?
They pretty much mean the same thing. However, one can cause the same intended effect with a mv (aka renaming) of resolv.conf to something like resolv.con, which deletes (aka removes) resolv.conf from the directory, replacing it with resolv.con. The file remains, but its original name does not, resulting in broken DNS, as if the file had been physically "deleted" (which we know isn't what delete {rm} actually does either).
Thanks. I just wanted to make sure I understood you correctly. I oft for asking a stupid question over making a stupid mistake any day of the week and twice on Sundays.
I'll try some things tomorrow and let you all know what happens.
(Like I said, everything's working fine except the updates, so I am not in panic mode, at least not yet.)
Last edited by frankbell; 12-20-2023 at 09:14 PM.
Reason: clarity
Any additional suggestions as to where I might look would be greatly appreciated.
And, if you don't have any suggestions, thanks for trying.
I know nothing about Red Hat package management but from the error message, it looks to me as if urpmi is a shell script, not a binary. In which case, you ought to be able to find out what $MIRRORLIST is set to and how it relates to the mirrors list file that you actually have.
Are you able to ping your router? As prequel to trying to do a follow-up here, I did a fresh Mageia 9 installation, with my NIC statically configured. ip a and ip route produced expected output, and I have a valid /etc/resolv.conf (same one used on the other 15 distros on that PC), but I couldn't do anything with it. Ping 127.0.0.1 worked, but none other. e.g. ping 192.168.<self> or router produced "ping: sendmsg: Operation not permitted", something I had never seen before. Then it dawned on me this was a default installation, something I hadn't done since early Mandrake days, and thus firewall must have been installed and enabled. Turning it off got everything network working. Did your upgrade add or change your firewall behavior?
Just to wrap things up, I finally got around to doing a fresh install of Mageia v. 9. It went very smoothly.
Since I have a separate /home partition, the great majority of my existing configuration was retained. Firefox and Thunderbird, for example, worked just fine out of the box, with all configuration and plugins still functional.
I did have to install xscreensaver anew and no doubt I shall run across some other speed bumps along the way, but, generally, everything's okay and I can update and add software just fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.