Hi Thorsten, On 25/06/2019 18:17, Thorsten Bro | openSUSE Heroes wrote:
unfortunately I have to inform you, that rsync.opensuse.org is down since this evening ~17.00 CEST.
The machine is a server which was donated by SUSE Linux GmbH. The rack space, power and uplink was donated by QSC AG datacenter in Nuremberg (former IP-Exchange).
What happened: I tried to do a kernel update of the machine and now it doesn't come back to life. As this machine is in an external DC, we need to drive there, as we don't have out-of-band-management possibilities in the sponsored rack of QSC AG.
What's the impact of this: rsync.opensuse.org is down, which means that all unauthorized rsync-mirrors of openSUSE (which are not in the whitelist on stage.opensuse.org), are not able to sync from us at the moment.
Furthermore rsync.opensuse.org is used as first push mirror usually by the OBS, which means that all clients which access download.opensuse.org via HTTP get redirected to rsync.opensuse.org by mirrorbrain, as long as the other servers in the world are syncing the newest updates and have it not yet ready.
In summary: - non-whitelisted rsync-mirrors can't mirror at the moment - Users will feel a performance drop for installing and downloading updates because they are redirected to downloadcontent.opensuse.org, the mirror in our office datacenter in Nuremberg with limited Uplink capacities, until other mirrors and the scanning caught up with the changes. - This affects -indeed- every package updated in the OBS which is not published below this path: https://download.opensuse.org/repositories/ - including Updates, Tumbleweed and Leap snapshots
Mitigation: In the end, running this on an old SUSE-donated machine with a lot of spinning slow disks, is not matching the performance needs of the machine. So there need to be a final and well-engineered solution for this. Which was, until now, always out of scope of any budget. Does someone have a good understanding what the needs would be? As a quick fix, somebody needs to drive to the data centre and investigate the machine. I'm willing to help, but I'm not driving those 60km again on my private expense, as I did last time. Sorry.
I don't know why this had to be a private expense
when you drove there last time.
But definitely not this time -- if you go there, this will be
your working time and business travel which of course
can be reimbursed.
I would appreciate you going there short-term.
Best,
--
Kurt Garloff