2026-07-28T06:42:47  *** teepee_ is now known as teepee
2026-07-28T08:16:52  <dza> https://debuginfod.opensuse.org `curl: (7) Failed to connect to debuginfod.opensuse.org:443 after 3226 ms: Could not connect to server`, initially tried from gdb so def not a user-agent issue - not reported on status
2026-07-28T08:17:21  <dza> - also worked yesterday
2026-07-28T14:16:55  *** mia_ is now known as mia
2026-07-28T17:41:37  <matrix-o-o> <holden> Yeah debuginfod is seemingly down or just blocking indiscriminately, not sure which honestly but I came to say the same thing after asking in #support:opensuse.org (https://matrix.to/#/#support:opensuse.org) yesterday.
2026-07-28T19:03:31  <acidsys> as mentioned all public services in the location debuginfod is in are down as the hypervisor cluster still needs to be recovered after power outage the other week
2026-07-28T19:41:51  <acidsys> I tried to look into it now. There were multiple problems.. all physical machines came back online themselves (good). kepler and chaplin including mostly VMs recovered themselves, but lacked DNS. arches pacemaker/sbd was dead, multipath recovered itself, but nfs needed remount. pacemaker cluster and all VMs started back with no further problems afterwards
2026-07-28T19:42:09  <acidsys> still needs some cleanup of failed services
2026-07-28T19:45:10  <acidsys> would be good to have at least one of the nameservers on the standalone hypervisors to have DNS not rely on one cluster
2026-07-28T19:48:05  <acidsys> confirmed slc-mirror.o.o and debuginfod.o.o are online again. but both might need some time to sync latest packages..
2026-07-28T21:19:18  <matrix-o-o> <holden> I missed the message about the power outage, but I can confirm things look to be back online. Thanks a ton!
2026-07-28T21:34:36  <dza> Sincerely thanks!