Project

General

Profile

tickets #113632

How to request for mirror rsync adjustments?

Added by itachi.sama.amaterasu@gmail.com 7 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2022-07-14
Due date:
% Done:

0%

Estimated time:

Description

Hi,

I was referred to here from the Build Service mailing list regarding
broken mirrors.

As it is clearly visible at:

https://mirror.opensuse.org/

the majority of mirrors for the Build Service is untracked.
This is important as it makes the redirector to not work properly and
make it impossible to install packages without directly pointing to a
server.

I would like to know what is the procedure in order to make the
rsync-hronizations to start again.

Bests,

Giovanni

P.S This was the conversation on the mailing list:

On 2022-07-06 14:55, Adrian Schröter wrote:

On Mittwoch, 6. Juli 2022, 14:33:04 CEST Giovanni Santini wrote:

Hi everyone,

Since a few days I am experiencing issues using mirrors for the build
service.

As you can see from the official mirror status page:

https://mirror.opensuse.org/

Multiple mirrors for Build Service are in stale status, especially in
Europe where I live.

My personal Arch repository in my nearest mirror:

https://ftp.lysator.liu.se/pub/opensuse/repositories/home:/ItachiSan:/archlinux/standard/x86_64/

is outdated since May 22nd.

My main question is where I should report this syncing issues, at
OpenSUSE level or to every mirror?

I do not believe we are supposed to nag to every mirror service, while I
can do to my nearest one if needed.
admin@opensuse.org is handling the mirror topics.


Related issues

Related to openSUSE admin - tickets #111246: /srv/bs/bin/needed_pushIn Progress2022-05-182022-08-08

History

#1 Updated by pjessen 7 months ago

  • Private changed from Yes to No

itachi.sama.amaterasu@gmail.com wrote:

As it is clearly visible at:
https://mirror.opensuse.org/
the majority of mirrors for the Build Service is untracked.

Actually, the mirror status is tracked :-) That's why you see them listed as probably outdated.

This is important as it makes the redirector to not work properly and

Well no, a lack of current mirrors for repositories is not a problem for the redirector.

make it impossible to install packages without directly pointing to a
server.

No, the redirector is very well aware of which mirrors have up-to-date repositories and will redirect you accordingly.

I would like to know what is the procedure in order to make the
rsync-hronizations to start again.

If there is a genuine problem, the right thing is to open a ticket for the specific mirror, then our mirror admin will look into it.

Multiple mirrors for Build Service are in stale status, especially in
Europe where I live.

My personal Arch repository in my nearest mirror:

https://ftp.lysator.liu.se/pub/opensuse/repositories/home:/ItachiSan:/archlinux/standard/x86_64/

is outdated since May 22nd.

Right, that is something that can be looked into.
We run a push service for Lysator, and I see your repo waiting to be pushed since 13 July. Just looking at today since midnight, we have 1396 home repos waiting to be pushed. Dated 14 July, there is another 2000, 13 July 1154 home repos. At a quick glance, the repo push process is running fine, but home repos are given the lowest priority.

#2 Updated by pjessen 7 months ago

  • Assignee set to pjessen

Before I go away for summer holidays, I took another quick look at pontifex and the repopush.
At 2022-07-19 0920, /srv/bs/arrived had 22805 items awaiting push, the oldest from May 18. Of those, about 77% (17635) are home-repos.
At a quick glance, that number "repos ready to be pushed", continues to slowly grow.
At 2022-07-19 1024, now 22812 repos.
2022-07-19 1324, about three hours later, 22840.

Hmm, /srv/bs/pushed/ also has some 31000 files, which is surely unusual.

Hmm, I did some editing of /srv/bs/bin/needed_push around 18/20 May, to accommodate filenames with blanks. Now I have to wonder if I screwed something up.

#3 Updated by pjessen 7 months ago

#4 Updated by ItachiSan 6 months ago

Hi,

From my understanding you don't need any additional input, is it correct?

And it seems to me from the comment that the script seems to be misbehaving.

Please let me know if I can help in any way. :)

/ Giovanni

#5 Updated by pjessen 5 months ago

I have been looking at how to improve our repopush. The issue we have is that there is simply too much to do. Build service provides updates faster than we can push them out. Some mirrors are faster than others, so my impression is that the limitation is on the receiving side, which we can't do much about.

Also available in: Atom PDF