On 07/10/17 03:21, Richard England wrote: > Recently I've started seeing failure with dnf update. It appears that I'm > attempting to access a RedHat ipaddress presumably to update the repomd.xml file > but it is failing and seems to indicate that there is a "network failure" (code 4) > > http://209.132.178.35/25/repomd.xml appears to be a dead link Just for reference.... [egreshko@meimei tmp]$ wget http://209.132.178.35/25/repomd.xml --2017-07-10 08:20:07-- http://209.132.178.35/25/repomd.xml Connecting to 209.132.178.35:80... failed: No route to host. [egreshko@meimei tmp]$ host 209.132.178.35 35.178.132.209.in-addr.arpa domain name pointer vm-35-178-132-209.osop.rhcloud.com. I'm guessing the "vm" stands for "virtual machine" > > I have attempted to remove /var/dnf/cache completely thinking it was storing the > IPaddr there but to no avail. Where is this URL/IPaddr coming from? > > Has anyone else encountered this or know where to start to debug? I have found that > all three of my Fedora 25 systems are exhibiting the same symptom. Yes, it all sounds very odd. If those systems have been updated from previous versions you can try using /usr/bin/dnf-2 to update. I'm going to guess this will also fail. Meaning, I don't think it is a dnf issue. Since you have 3 systems all acting the same way I would suspect something external to the systems. Is it safe to assume you've not made any recent changes? What I would do is first try using an external DNS server. I would manually edit the /etc/resolv.conf file and change the nameserver entry to point to 8.8.8.8 or 8.8.4.4 which are google's public DNS servers. Then clear all the cache and try again. -- Fedora Users List - The place to go to speculate endlessly
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
