Lately it has become stressful to update the system , all the Repositories Time Out , with zypper even worse , I have to go step by step with Yast one repository at a time
It depends on your used mirrors, location and more…
At least you could show your repository list and the error messages of a failed update attempt…
zypper lr -d
zypper dup
enziosavio@linux-area51:~> sudo zypper ref
There was a problem retrieving files from 'nVidia Graphics Drivers'.
Timeout exceeded while accessing 'https://download.nvidia.com/opensuse/tumbleweed/repodata/repomd.xml'.
Read the error message displayed above.
Banned 'nVidia Graphics Drivers' repository due to above error.
The 'Main Repository (NON-OSS)' repository is up to date.
The 'Main Repository (OSS)' repository is up to date.
Retrieving the metadata of the 'Packman Repository' repository .............................................. .................................................... ..........[mistake]
The repository 'Packman Repository' is invalid.
[ftp.gwdg.de-openSUSE_Tumbleweed|http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/] No valid metadata was found at the specified URL
Chronology:
- [|] Error trying to read from 'http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/'
- Timeout exceeded while accessing 'http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/repodata/repomd.xml'.
Verify that the URIs defined for this repository point to a valid repository.
Excluding the 'Packman Repository' repository due to the above error.
Some repositories have not been updated due to an error.
enziosavio@linux-area51:~>
This is an example
type enziosavio@linux-area51:~> zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
--+---------------------------------+---------------------------------+---------+-----------+---------+----------+--------+---------------------------------------------------------------------+--------
1 | download.nvidia.com-tumbleweed | nVidia Graphics Drivers | Sì | (r ) Sì | Sì | 90 | rpm-md | https://download.nvidia.com/opensuse/tumbleweed |
2 | download.opensuse.org-non-oss_1 | Repository principale (NON-OSS) | Sì | (r ) Sì | Sì | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
3 | download.opensuse.org-oss_1 | Repository principale (OSS) | Sì | (r ) Sì | Sì | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
4 | ftp.gwdg.de-openSUSE_Tumbleweed | Packman Repository | Sì | (r ) Sì | Sì | 50 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ |
enziosavio@linux-area51:~>
or paste code here
Neither of these two repositories are under SUSE or openSUSE control. I can access both links normally, so it appears some local networking issue in your location.
I said it was an example of that moment, it also happens with OSS and NON-OSS repo
It sounds more to me that you have a local problem, just as Andrei says. It could be your machine, local network or upstream. Start by checking journal and network related. Ex.
journalctl _COMM=NetworkManager
Or the kernel entry in journal, back to where the problem first appeared. Ex.
journalctl --since ‘2 day ago’ _TRANSPORT=kernel
Also, check your DNS. If that doesn’t give anything go to your local network (switch, router etc.). You could have a lot of drops that’s not immediately recognized. Check with
ip -statistics a sh
Look for Dropped. External network you check with ping, traceroute or (my favorite) mtr (or if you prefer xmtr). You probably need to install it. zypper in mtr (if the repo is available). Then run
mtr ftp.gwdg.de
Or to nvidia with AS-number and intervall 5 sec.
mtr -z -i 5 download.nvidia.com
Check for Loss% but the other columns might also be important. Here is mine for Nvidia with --report. Just add --report and wait about 10 sec. The loss in my case is just two routers upstream limiting the icmp echo reply directed to that network device. But if they continue upstream towards the end, something is often not right.
# mtr --report download.nvidia.com
Start: 2023-08-03T13:49:56+0200
HOST: jrxm Loss% Snt Last Avg Best Wrst StDev
1.|-- 192.168.1.1 0.0% 10 2.3 3.1 2.0 4.9 0.9
2.|-- r1 0.0% 10 12.0 5.4 2.6 12.0 2.7
3.|-- r2 30.0% 10 22.5 22.9 21.0 24.7 1.4
4.|-- r3 70.0% 10 22.7 22.3 21.7 22.7 0.5
5.|-- r4 0.0% 10 22.6 21.9 20.2 22.8 0.9
6.|-- r5 0.0% 10 22.3 21.9 20.7 24.6 1.1
7.|-- r6 0.0% 10 18.1 18.3 17.7 19.3 0.4
8.|-- r7 0.0% 10 18.6 20.0 17.5 33.9 4.9
9.|-- 192.229.220.191 0.0% 10 18.3 19.8 18.3 25.0 2.0
2 Likes
It must be a local problem just like you said , in fact everything has been happening for a week after a violent storm .