2020-05-28T02:27:03  *** okurz_ is now known as okurz
2020-05-28T03:04:07  *** Eighth_Doctor is now known as Conan_Kudo
2020-05-28T03:04:47  *** Conan_Kudo is now known as Eighth_Doctor
2020-05-28T04:44:09  -heroes-bot- PROBLEM: PSQL locks on mirrordb2.infra.opensuse.org - POSTGRES_LOCKS CRITICAL: DB postgres total locks: 303 * total waiting locks: 147 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=mirrordb2.infra.opensuse.org&service=PSQL%20locks
2020-05-28T04:45:26  -heroes-bot- PROBLEM: PSQL locks on mirrordb1.infra.opensuse.org - POSTGRES_LOCKS CRITICAL: DB postgres total waiting locks: 4 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=mirrordb1.infra.opensuse.org&service=PSQL%20locks
2020-05-28T04:54:09  -heroes-bot- RECOVERY: PSQL locks on mirrordb2.infra.opensuse.org - POSTGRES_LOCKS OK: DB postgres total=2 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=mirrordb2.infra.opensuse.org&service=PSQL%20locks
2020-05-28T04:55:26  -heroes-bot- RECOVERY: PSQL locks on mirrordb1.infra.opensuse.org - POSTGRES_LOCKS OK: DB postgres total=4 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=mirrordb1.infra.opensuse.org&service=PSQL%20locks
2020-05-28T09:32:09  -heroes-bot- PROBLEM: NRPE on olaf.infra.opensuse.org - CHECK_NRPE: Error - Could not connect to 192.168.47.17. Check system logs on 192.168.47.17 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=olaf.infra.opensuse.org&service=NRPE
2020-05-28T09:42:09  -heroes-bot- RECOVERY: NRPE on olaf.infra.opensuse.org - NRPE v3.2.1 ; See https://monitor.opensuse.org/icinga/cgi-bin/extinfo.cgi?type=2&host=olaf.infra.opensuse.org&service=NRPE
2020-05-28T13:42:31  <malcolmlewis> Hi all, bugzilla is down...?
2020-05-28T16:12:12  <kl_eisbaer> https://bugzilla.opensuse.org/index.cgi works here
2020-05-28T16:12:58  <lcp> bmwiedemann1: I was wondering, apparently YaST's CI setup from internal SUSE Jenkins can't reach Github, which prevents the releases to be tagged automatically, would you mind taking a look
2020-05-28T16:13:12  <lcp> kl_eisbaer: it was down for a sec around 15:45
2020-05-28T16:13:26  <kl_eisbaer> lcp: hm - maybe some network hickups?
2020-05-28T16:13:36  <lcp> it was mysql error
2020-05-28T16:14:12  <kl_eisbaer> Jip: I got a confirmation from our IT guys that there was some problem
2020-05-28T16:14:29  <kl_eisbaer> But they say that everything should be fine again
2020-05-28T16:35:56  <cboltz> kl_eisbaer: just FYI, since you mentioned upcoming IP changes yesterday - the IPs managed by keepalived are in salt (pillar/role/proxy.sls and login.sls)
2020-05-28T16:37:48  <kl_eisbaer> cboltz: I'm currently clarifying the IP ranges.... ...once we have them, we can just add the new addresses there in addition for a while
2020-05-28T16:38:18  <kl_eisbaer> but the good news: the IPv4 address range in Nuremberg stays
2020-05-28T16:38:33  <kl_eisbaer> in Provo, we will have to switch (which mainly affects the mirror servers)
2020-05-28T16:38:48  <kl_eisbaer> in Nuremberg, we have to switch IPv6 only
2020-05-28T16:39:08  <kl_eisbaer> ...which might allow us to do some cleanups. Let's see ...
2020-05-28T16:40:13  <cboltz> keeping the IPv4 in Nuremberg sounds good, and should avoid most problems with outgoing mails
2020-05-28T16:40:39  <cboltz> (BTW: outgoing mails are the reason why static.o.o has a separate IP instead of being CNAME proxy.o.o)
2020-05-28T16:40:54  <kl_eisbaer> we might not get reverse entries for the new IPv6 range in time. So all our email servers might need to switch to "IPv4 only" for a short while
2020-05-28T16:41:19  <kl_eisbaer> but this will hopefulyl become a bit more clear in the next days
2020-05-28T16:41:30  <cboltz> indeed - not nice, but still better than delivery failures
2020-05-28T16:43:26  <cboltz> IIRC you said yesterday that we have to switch to the new IPs next week, so I'm not sure if "will hopefully become [...] clear in the next days" is good or interesting[tm]
2020-05-28T16:43:31  <cboltz> well, probably a bit of both ;-)
2020-05-28T16:44:10  <kl_eisbaer> cboltz: sorry for misleading: the sentence from yesterday was just about the machines in Provo
2020-05-28T16:44:28  <cboltz> ah, ok
2020-05-28T16:44:39  <cboltz> that makes things a bit more relaxed :-)
2020-05-28T16:44:59  <kl_eisbaer> they have to move from 130.57.72. to 91.193.113.
2020-05-28T16:45:16  <kl_eisbaer> well: relaxed for you ... ;-)
2020-05-28T16:46:17  <cboltz> I'd guess / hope also for you ;-)
2020-05-28T16:48:19  <kl_eisbaer> well.... -
2020-05-28T16:48:28  <kl_eisbaer> but to something completely different ...
2020-05-28T16:48:49  <kl_eisbaer> cboltz: do you know who added the configuration for forums.o.o on daffy ?
2020-05-28T16:49:50  <kl_eisbaer> because I guess we should either think about a new macro (which is a good idea anyway) or adjust this configuration to allow the forums machine to see the real client IP
2020-05-28T16:49:51  <cboltz> IIRC I did the initial config some months ago - but I'm not sure if it's still in that state or if someone changed it in the meantime
2020-05-28T16:51:03  <cboltz> just checked - looks like someone changed it in the meantime
2020-05-28T16:53:03  * cboltz wonders if we really want a new macro, or if making daffy salt-managed would make more sense
2020-05-28T16:54:08  <cboltz> with that said - I'll be away for the next ~30 minutes, so my next answer will take a while ;-)
2020-05-28T17:31:30  * cboltz is back