search for: ip_resolve

Hi, Disabled ipv6 (using sysctl, disabled ip6tables, no reboot, no proxy present) and still get the message as below. Centos 6.3 (i know its old) Kernel : 2.6.32-279.14.1.el6.x86_64 (I know its old) Standard /etc/yum.conf (no changes) Standard repos (centos base), enabled Cleaned cache: yum metadata (didn't work) Then: yum clean all (didn't work) Then yum makecache (didn't work)

Tried that :D yum is still trying to connect via ipv6 (ip_resolve=4 in config file) -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Alikhan Damirov Sent: Thursday, December 25, 2014 11:59 AM To: CentOS mailing list Subject: Re: [CentOS] (py)curl error 7 Hi, from man yum.conf: ip_reso...

...failfunc' : <function _do_raise at 0x7effcd5bf848>, 'failure_callback': None, 'ftp_disable_epsv': False, 'ftp_headers' : None, 'half_life' : 2592000, 'http_headers' : None, 'interrupt_callback': None, 'ip_resolve' : None, 'keepalive' : 1, 'libproxy' : False, 'max_connections': 5, 'max_header_size': 2097152, 'minrate' : None, 'mirror_group' : None, 'multi_progress_obj': None, 'no_cache' : Fal...

...a way, it might make a usability improvement. A lot of people have no idea what IPv6 is and would be confused. >> >> I was confused myself at first, wondering if DHCP pulled in IPv6 from the router. > > If your DNS answers IPv6, it will have prefence over IPv4. You can set > ip_resolve=4 in your yum.conf > The issue is the yum server was down, so IPv4 didn't work. Once that server was back up (third party repo) it of course worked no issue. The issue is the error message, while a technically correct one, is one that is not very user friendly and can be confusing to pe...

I ran into this exact issue last night - http://www.iotti.biz/?p=433 When a computer is connected via IPv4 but the IPv4 a repo host connects to is not available, yum then tries the IPv6 address and will fail with a confusing message telling you it failed to connect to the IPv6 address. I don't know if there is a way for yum to figure out whether the current network connection to the

Am 2019-08-29 16:51, schrieb Gary Stainburn: > On Thursday 29 August 2019 15:45:44 Gordon Messmer wrote: >> On 8/29/19 3:03 AM, Gary Stainburn wrote: >> > https://us-east.repo.webtatic.com/yum/el7/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." >> >> >> What do you see when you run: >>

Hi, from man yum.conf: ip_resolve Determines how yum resolves host names. `4' or `IPv4': resolve to IPv4 addresses only. `6' or `IPv6': resolve to IPv6 addresses only. On 25 December 2014 at 11:53, Mateusz Guz <Mateusz.Guz at itworks.pl> wrote: > Hi, > > Disabled ipv6...

...t; > But if there is a way, it might make a usability improvement. A lot of people have no idea what IPv6 is and would be confused. > > I was confused myself at first, wondering if DHCP pulled in IPv6 from the router. If your DNS answers IPv6, it will have prefence over IPv4. You can set ip_resolve=4 in your yum.conf -- Marcelo "?No ser? acaso que esta vida moderna est? teniendo m?s de moderna que de vida?" (Mafalda)

...A lot >>> of people have no idea what IPv6 is and would be confused. >>> >>> I was confused myself at first, wondering if DHCP pulled in IPv6 from >>> the router. >> >> If your DNS answers IPv6, it will have prefence over IPv4. You can set >> ip_resolve=4 in your yum.conf >> > > The issue is the yum server was down, so IPv4 didn't work. > > Once that server was back up (third party repo) it of course worked no > issue. > > The issue is the error message, while a technically correct one, is one > that is not ver...

...9;failfunc' : <function _do_raise at 0x7fd3c45da848>, 'failure_callback': None, 'ftp_disable_epsv': False, 'ftp_headers' : None, 'half_life' : 2592000, 'http_headers' : (), 'interrupt_callback': None, 'ip_resolve' : None, 'keepalive' : True, 'libproxy' : False, 'max_connections': 5, 'max_header_size': 2097152, 'minrate' : 0, 'mirror_group' : None, 'multi_progress_obj': None, 'no_cache' : Fal...

...g to avoid) -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Mateusz Guz Sent: Thursday, December 25, 2014 3:16 PM To: CentOS mailing list Subject: Re: [CentOS] (py)curl error 7 Tried that :D yum is still trying to connect via ipv6 (ip_resolve=4 in config file) -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Alikhan Damirov Sent: Thursday, December 25, 2014 11:59 AM To: CentOS mailing list Subject: Re: [CentOS] (py)curl error 7 Hi, from man yum.conf: ip_reso...

Am 2019-08-29 17:36, schrieb Gary Stainburn: > On Thursday 29 August 2019 16:20:00 Alexander Dalloz wrote: >> Hi, >> >> yum uses libcurl behind the scenes and thus NSS and not OpenSSL. >> >> Do you get something indicative when running: >> >> URLGRABBER_DEBUG=1 yum --disablerepo=\* --enablerepo=webtatic >> check-update >> >>