Project

General

Profile

tickets #92966

MirrorBrain scanner is stuck

Added by quantummirror about 1 year ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Mirrors
Target version:
-
Start date:
2021-05-22
Due date:
% Done:

0%

Estimated time:

Description

Dear openSUSE infra team,

I think the MB scanner is stuck and it does not update the file lists. I
also see the normal scanner connections from 195.135.221.170 on opensuse
dir and on the isos.

My mirror hasn't received a single iso or package (ZYpp) download since
yesterday morning. [21/May/2021:08:56:32 +0200]

Output from
(h)ttps://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20210519-Media.iso?mirrorlist

"No mirror was found

I am very sorry, but no mirror was found. Feel free to download directly:
/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20210519-Media.iso
https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20210519-Media.iso

Powered by MirrorBrain" http://mirrorbrain.org/

The other download pages also give this result.

Would you be so kind and fix this issue?

Thank you for your help in advance!

Cheers,

Peter

History

#1 Updated by cboltz about 1 year ago

  • Category set to Mirrors
  • Assignee set to pjessen

#2 Updated by pjessen about 1 year ago

  • Private changed from Yes to No

Bernhard already looked at it and determined it was mirrordb2 having a problem:

I fixed it for now my switching pontifex2:
/etc/apache2/vhosts.d/_download.conf
to use mirrordb1 again.

mirrordb2's postgres would not start (probably replication needs some
kicking again) but I wonder if that replication is really worth all the hassle.

Often enough HA setups decrease availability via increased complexity
causing increased fragility.

E.g. booting up a single node always just works, but rebooting a pair of
HA nodes might well have both of them reject work for fear of split-brain.

The scanner continues to use mirrordb1.

#3 Updated by bmwiedemann about 1 year ago

I also setup a local haproxy on pontifex2 to forward to mirrordb2 if available and fallback to mirrordb1 otherwise.

The advantage is that this makes outages less noticeable, but the downside is that we also notice outages less, so would need better monitoring.

#4 Updated by pjessen 5 months ago

  • Assignee deleted (pjessen)

#5 Updated by pjessen about 1 month ago

  • Assignee set to andriinikitin

Also available in: Atom PDF