Zypper fails to access repository after some time running updates

Trying to install updates for the second time, having the same problem. After I run zypper dup and confirm the package upgrades, zypper hangs after downloading some packages. It may download 30 or even 60 packages, but then the progress bar stops moving on some random package. I’ve been solving this by nuking zypper with Ctrl+C each time and running zypper dup again. This way, zypper skips the packages that are already in cache and proceeds to download the rest. However, this needs to be repeated many times, as after 10-20 packages zypper hangs again. I think this may be an odd connection issue. It should be noted that zypper becomes completely unresponsive when it fails like that, no error messages or anything, just a stuck progress bar.

I’m running a fresh install of Tumbleweed, this is literally my second time updating this installation. Never had a problem like that in Tumbleweed. Nothing crazy about the configuration other than BTRFS swap subvolume instead of a partition (to avoid a second passphrase prompt on boot with full disk encryption)

okay, it’s been sitting for a while and I got an error message from zypper (in verbose mode):

Retrieving: libKF6JobWidgets6-lang-6.11.0-1.1.noarch.rpm ..............................................[error]
Download (curl) error for 'http://download.opensuse.org/tumbleweed/repo/oss/noarch/libKF6JobWidgets6-lang-6.11.0-1.1.noarch.rpm':
Error code: Curl error 56
Error message: Recv failure: Connection timed out

I also had the same problems a few months ago. To solve them I used a VPN, coincidentally shortly before I had sent a complaint to my provider for Wireless problems in the home network, when the technician called me I also mentioned this problem I had in downloading from certain sources, and I asked him if someone was closing the taps on certain IPs… well since that phone call I have not had to use the VPN anymore and now I always download at the maximum of what comes from the network. I don’t know why but there is a sort of filter towards the Opensuse mirrors by the providers.

This also occurred a few weeks back, except it wasn’t a time our error.

seems to have been fixed by fumbling with dns config on my router

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.