Trying to update TW today and constant errors accessing repos

I am trying to update my 2 TW installs today and both are getting repos unaccessible (yes I know wrong spelling :wink: ).
I have over 4000 updates so I assume heavy load but it is making life difficult. I do update several times a week and still had over 4000 today!

Stuart

Same here. Everyone had the same issue last week too. I wonder what’s going on with the repos

@broadstairs yes the python switch… I suspect some syncing still going on… have you tried preload? env ZYPP_PCK_PRELOAD=1 zypper -vvv dup

@broadstairs @LizardDude22 and there is another snapshot syncing… 20250310-0

Not sure what preload does but I do use the download-only option so it caches stuff. One machine has now managed all its downloads and has updated.

What annoys me is that zypper retries (waiting 30 seconds) maybe once or twice but then gives up on the next failure instead of retrying each time! I’d be quite happy to leave it running with a wait time of 60 seconds but no idea if that timing can be altered.

Stuart

Stuart

@broadstairs All is covered in the Factory Mailing List which you should follow or at least visit when seeing things like this :wink:

I’ll find some time to look at that.

Frankly if they are intent on having thins kind of size update then they need to make some improvements, either ramp up server capacity or improve the way zypper works so rather than giving up it continues with longer wait times or better still both! It is simply ridiculous to take this long to update, taking nearly a whole day for 2 PCs!

Stuart

The servers are not provided or operated nor under the control of openSUSE (never where and never will be). If you want more bandwidth, you need to contact the server owners. Be aware that in most cases the servers are under control of universitys or other institutions.

You may understand, that openSUSE is not the only linux distribution or software project which is hosted on the same server. You may get a glimps of understanding which bandwith the servers are already providing when you have a look at the basic directory of such a server. This are all linux distributions/projects which are hosted on ONE SINGLE server (which gets accesses by several thousand users at the same time…):
https://ftp.halifax.rwth-aachen.de/

OK so in that case improve zypper so that it

  1. allows more time between retries maybe a parameter somewhere
  2. when it decides it is autoselecting abort then just abort instead of waiting for the timeout

working like this is unacceptable.

Stuart

And I think a comment like that is rude, given the fact that you are consuming a free product.

1 Like

@broadstairs What I would suggest is looking at when new snapshots are released, both Forums and Mailing Lists have this information (or subscribe to the Mailing List?)

As already indicated, the Mirror re-sync is controlled by the third party providers. If you peruse the Mirrors List, perhaps there is a closer locale to you that has a high sync time and use that? http://mirrors.opensuse.org/

There is some expectation when using Tumbleweed that you, as your system(s) admin keep an eye on snapshot releases and look at when it can be done?

I don’t think I was being rude at all. I am proposing the processes are looked at to improve handling for these kind of situations. I realise that money is not often the answer but thinking ‘out of the box’ may bear fruit.

If I had the means to schedule a download and leave it unattended to completion that would be good way to eliminate the frustration of having to ‘baby sit’ my PCs to get it through.

Stuart

There are some settings in zypp.conf which should be modified by the system adminstrator if he is not satisfied by the defaults.

1 Like

I experienced the same issues, as well.

I don’t know if it was a coincidence, but today my problem was resolved ONLY after an explicit “zypper ref” before “zypper dup