Re: dnf not working

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/24/2016 10:37 AM, machine wrote:
> Hi, 
> 
>> You have a DNS failure:
>>
>> 	[Resolving timed out after 120000 milliseconds]
>>
>> So get that solved first. Verify your network came up ("sudo ifconfig
>> -a") and that you have valid nameservers configured ("cat
>> /etc/resolv.conf"). Try to ping the name servers from that list (if
>> you have any).
> According to ifconfig, my network is fine. There was an entry 'wlo1'.

Based on that device name, I'm assuming you're using wifi. I'm also
assuming you're using DHCP to get an IP address for your machine and
that the DHCP server is your wireless access point/router/whatever.

> cat /etc/resolv.conf returned :
> # Generated by NetworkManager
> nameserver 192.168.1.1
> 
> I could ping this. 

Not surprising. On the vast majority of networks, the first usable IP
(in your case 192.168.1.1) is the gateway and should be pingable. Some
networks use the LAST usable IP as the gateway (nowhere near as
common) and still others use some arbitrary address as the gateway
(pretty rare).

What disturbs me is that your DHCP server didn't offer any external DNS
servers and that, based on the fact it only gave you its own address,
that it's not acting as either a caching DNS server or proxying your
requests through.

> After this, I added google's open DNS to this file : 8.8.8.8
> Now, I can access xyz.fedoraproject.org 
> 
> Idk if this can help or not in diagnosing the problem, I read on a
> related question to try this,
> 
> 1.rpm -q dnf librepo python-librepo	
> Output:
> dnf-1.1.9-2.fc24.noarch
> librepo-1.7.18-2.fc24.x86_64
> package python-librepo is not installed.
> 
> 2. Installing python2
> Curl error (28): Timeout was reached for https://mirrors.fedoraproject.
> org/metalink?repo=fedora-24&arch=x86_64 [Resolving timed out after
> 120000 milliseconds]
> However, I can download metalink file from the browser.

That data may be cached by your browser if you examined it after
adding the 8.8.8.8 nameserver to your /etc/resolv.conf. Try a reboot
or flush the browser's cache and try to fetch the metadata again via
the browser without the 8.8.8.8 nameserver in /etc/resolv.conf. I'll
bet it fails.

> Does this help ? 
> OR is it still looking like a network issue?

It still looks like a network issue to me in that the DNS services
aren't happening. Check your NetworkManager (NM) config for that device,
go to the "IPv4 Settings" tab (assuming you're using IPv4) and make
sure that if you're using DHCP, you have "Automatic (DHCP)" selected in
the "Method" section and NOT "Automatic (DHCP) addresses only" and that
you don't have anything in the "Additional DNS servers" section, then
restart Network Manager:

	sudo systemctl restart NetworkManager

Recheck the /etc/resolv.conf file to see if you have any additional
nameservers defined. If not, then you COULD add 8.8.8.8 to the
"Additional DNS servers" section of the NM config and do another
NM restart. The thing that bothers me is that the DHCP stuff is not
giving you any nameservers to use other than the router and that the
machine it is giving you (192.168.1.1) isn't acting like a resolver
itself and it should if it doesn't pass along any nameservers.

The vast majority of wireless routers pass through the DNS servers they
get from their ISP upstream providers. The WAN side of your wireless
router gets its IP via DHCP from your ISP along with nameservers to
use. It usually passes those nameservers along to ITS DHCP clients on
the LAN side of things. If not, they run a caching name server or proxy
that the LAN DHCP clients use.

----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-      Always remember you're unique, just like everyone else.       -
----------------------------------------------------------------------
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux