On 2024-02-24 23:01:51 Rodney Baker wrote:
On Sunday, 25 February 2024 14:06:28 ACDT J. Leslie Turriff wrote:
A few days ago I installed Leap 15.5 on a Lenovo ThinkPad, and on a spare drive on my system. All seemed to be working well, then when I was getting
ready to install some pipewire bits, this happened : | @19:31:45 root@pinto | wd=~ | ● zypper ref | Problem retrieving files from 'KDE3'. | Download (curl) error
url=https%3A%2F%2Fdownload.opensuse.org%2Frepositories%2FKDE%3A%2FKDE3%2F15 .5 %2Frepodata%2Frepomd.xml&data=05%7C02%7C%7Caaeb891e26474c47f32108dc35b31300 %7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638444290471308668%7CUnknown %7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6 Mn0 %3D%7C0%7C%7C%7C&sdata=b2gA3u65Td%2BRxh17HygaYxu55FjVTzcSdYRI4ItDOfc%3D&r
eserved=0':
| Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: | Couldn't
connect to server
[...]
I tried using YaST sw_single, but it did the same thing. (See attached.) For some reason, YaST is now working again on one machine, but the problem persists with zypper on both. Other network applications (web browser, email) work just fine.
The reference to 127.0.0.1 leads me to conclude that the issue is internal to my machines, but networking is pretty much a black box to me and various tools keep being replaced with new ones, I have no idea how to collect additional information that might explain what is happening.
Leslie
127.0.0.1 is always "localhost" i.e. the local machine. It looks like curl is configured to use a (possibly filtered) proxy on the local machine, or the repo addresses are somehow being resolved to localhost rather than their actual IP addresses.
Localhost addresses will never be routed externally to the local machine, so you 'll need to figure out why those addresses appear to be being resolved as localhost. Yes, as I said above; but I don't know how to diagnose that.
Do you have entries in your /etc/hosts file? Yes: | # | # hosts This file describes a number of hostname-to-address | # mappings for the TCP/IP subsystem. It is mostly | # used at boot time, when no name servers are running. | # On small systems, this file can be used instead of a | # "named" name server. | # Syntax: | # | # IPv4 Address Fully Qualified Hostname Short Hostnames | #------------- ------------------------ ------------------- | 127.0.0.1 localhost | # | 192.168.1.1 grey.sixys.site grey router | 192.168.1.2 pinto.sixys.site pinto desktop1 | 192.168.1.3 philips.sixys.site philips TV | 192.168.1.4 chestnut.sixys.site chestnut desktop2 | 192.168.1.5 black.sixys.site black windows | 192.168.1.6 charcoal.sixys.site charcoal dell | #92.168.1.7 unused | #92.168.1.8 unused | 192.168.1.9 palomino.sixys.site palomino server | 192.168.1.10 buckskin.sixys.site buckskin printer | #92.168.1.11 unused | 192.168.1.12 chrome.sixys.site chrome laptop1 | 192.168.1.13 pinto-foal.sixys.site pinto-foal UPS | 192.168.1.14 toreador.sixys.site toreador laptop2 | # | 192.168.100.1 blueroan.sixys.site blueroan downlink | # | #============================================================ | # IPv6 Address Hostnames | #------------- --------------------------------------------- | ::1 localhost ipv6-localhost ipv6-loopback | | fe00::0 ipv6-localnet | | ff00::0 ipv6-mcastprefix | ff02::1 ipv6-allnodes | ff02::2 ipv6-allrouters | ff02::3 ipv6-allhosts | # | #============================================================ | # DNS Servers: | # 192.168.1.1 | 99.197.99.99 | 99.196.99.99 | #============================================================
What about /etc/resolv.conf?
Just the DNS list: | 23:10:07 root@pinto | wd=~ | ● ll /etc/resolv.conf | lrwxrwxrwx 1 root root 26 2024-02-20 22:25:28 /etc/resolv.conf -> /run/netconfig/resolv.conf | rc=0 | @00:04:14 root@pinto | wd=~ | ● l /run/netconfig/resolv.conf | ### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf | ### autogenerated by netconfig! | # | # Before you change this file manually, consider to define the | # static DNS configuration using the following variables in the | # /etc/sysconfig/network/config file: | # NETCONFIG_DNS_STATIC_SEARCHLIST | # NETCONFIG_DNS_STATIC_SERVERS | # NETCONFIG_DNS_FORWARDER | # or disable DNS configuration updates via netconfig by setting: | # NETCONFIG_DNS_POLICY='' | # | # See also the netconfig(8) manual page and other documentation. | # | ### Call "netconfig update -f" to force adjusting of /etc/resolv.conf. | nameserver 192.168.1.1 | nameserver 99.197.99.99 | nameserver 99.196.99.99 |rc=0
Are you running a filtered proxy server or some other process that was working and now is not?
I run Privoxy, installed from the openSUSE repository and activated by YaST Service Manager. It uses 127.0.0.1:8118.
What are the URLs for the repos under /etc/zypp/repos.d?
| @00:28:33 root@pinto | wd=~ | ● l /etc/zypp/repos.d | total 152K | -rw-r--r-- 1 root root 154 Feb 21 18:05 KDE3.repo | -rw-r--r-- 1 root root 128 Feb 21 18:05 Local.repo | -rw-r--r-- 1 root root 188 Feb 21 18:05 NVIDIA:repo-non-free.repo | -rw-r--r-- 1 root root 204 Feb 21 18:05 ftp.gwdg.de-openSUSE_Leap_$releasever.repo | -rw-r--r-- 1 root root 200 Feb 21 18:05 openSUSE-Leap-15.5-1.repo | -rw-r--r-- 1 root root 209 Feb 21 18:05 openSUSE:repo-non-oss-debug.repo | -rw-r--r-- 1 root root 203 Feb 21 18:05 openSUSE:repo-non-oss.repo | -rw-r--r-- 1 root root 186 Feb 21 18:05 openSUSE:repo-openh264.repo | -rw-r--r-- 1 root root 197 Feb 21 18:05 openSUSE:repo-oss-debug.repo | -rw-r--r-- 1 root root 200 Feb 21 18:05 openSUSE:repo-oss-source.repo | -rw-r--r-- 1 root root 191 Feb 21 18:05 openSUSE:repo-oss.repo | -rw-r--r-- 1 root root 208 Feb 21 18:05 openSUSE:update-backports-debug.repo | -rw-r--r-- 1 root root 202 Feb 21 18:05 openSUSE:update-backports.repo | -rw-r--r-- 1 root root 202 Feb 21 18:05 openSUSE:update-non-oss-debug.repo | -rw-r--r-- 1 root root 196 Feb 21 18:05 openSUSE:update-non-oss.repo | -rw-r--r-- 1 root root 190 Feb 21 18:05 openSUSE:update-oss-debug.repo | -rw-r--r-- 1 root root 184 Feb 21 18:05 openSUSE:update-oss.repo | -rw-r--r-- 1 root root 190 Feb 21 18:05 openSUSE:update-sle-debug.repo | -rw-r--r-- 1 root root 184 Feb 21 18:05 openSUSE:update-sle.repo | -rw-r--r-- 1 root root 149 Feb 21 18:05 packman.repo | -rw-r--r-- 1 root root 200 Feb 21 18:05 repo-backports-debug-update.repo | -rw-r--r-- 1 root root 254 May 23 2023 repo-backports-debug-update.repo.rpmsave | -rw-r--r-- 1 root root 199 Feb 21 18:05 repo-backports-update.repo | -rw-r--r-- 1 root root 199 May 23 2023 repo-backports-update.repo.rpmsave | -rw-r--r-- 1 root root 179 Feb 21 18:05 repo-debug-non-oss.repo | -rw-r--r-- 1 root root 183 Feb 21 18:05 repo-debug-update-non-oss.repo | -rw-r--r-- 1 root root 162 Feb 21 18:05 repo-debug-update.repo | -rw-r--r-- 1 root root 157 Feb 21 18:05 repo-debug.repo | -rw-r--r-- 1 root root 178 Feb 21 18:05 repo-non-oss.repo | -rw-r--r-- 1 root root 164 Feb 21 18:05 repo-openh264.repo | -rw-r--r-- 1 root root 167 Feb 21 18:05 repo-oss.repo | -rw-r--r-- 1 root root 209 Feb 21 18:05 repo-sle-debug-update.repo | -rw-r--r-- 1 root root 234 May 23 2023 repo-sle-debug-update.repo.rpmsave | -rw-r--r-- 1 root root 208 Feb 21 18:05 repo-sle-update.repo | -rw-r--r-- 1 root root 208 May 23 2023 repo-sle-update.repo.rpmsave | -rw-r--r-- 1 root root 160 Feb 21 18:05 repo-source.repo | -rw-r--r-- 1 root root 183 Feb 21 18:05 repo-update-non-oss.repo | -rw-r--r-- 1 root root 165 Feb 21 18:05 repo-update.repo | rc=0
Is there anything in /etc/curlrc or /root/.curlrc that is configuring a proxy at localhost:1080 (or 127.0.0.1:1080)?
| @00:31:16 root@pinto | wd=~ | ● ll /etc/curlrc | /bin/ls: cannot access '/etc/curlrc': No such file or directory | rc=2 | @00:31:50 root@pinto | wd=~ | ● ll .curlrc | /bin/ls: cannot access '.curlrc': No such file or directory | rc=2
Or perhaps an environment variable doing the same? | @00:31:55 root@pinto | wd=~ | ● env|grep 1080 | rc=1 | @00:33:10 root@pinto | wd=~ | ● env|grep 8118 | https_proxy=127.0.0.1/8118 | http_proxy=127.0.0.1/8118 | rc=0
Regards, Rodney.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64