[07:13:18] I am failing over phabricator proxy, it should be smooth and I won't force connections to move, but if you see something weird please ping me [17:51:46] ottomata: I got an offer on my house last week from someone married to a guy named 'Andrew Otto'. I'm pretty sure it's not you though :) [18:41:05] andrewbogott: if it is me it sounds like a really fun scandal! [18:41:12] I didn't know I was married [18:41:12] ! [18:41:27] newlywed! https://www.zola.com/wedding/drewandelle2023 [18:50:40] I thought people usually password-protected those wedding websites... [18:53:44] Or took them down after the wedding? [18:54:45] (to be fair, I'm pretty happy about the idea of selling my house to humans rather than a rental corp) [19:20:22] /ac/ac [23:09:23] Do we use "The Lounge IRC Client" in our monitoring? I noticed it pop up in wdqs1015 access log right after I merged 982138 , but could be a coincidence [23:12:05] inflatador: I don't know of any official use of it, but it looks nice. https://thelounge.chat/ - self-hosted, so it strikes me that it might be someone's personal web based client. Just a guess. [23:16:54] btullis thanks, I'm grasping at straws a bit ;0 [23:30:06] inflatador: noteworthy is there is nothing in /var/log/nginx* when manually running the check_http against that [23:30:39] oh, there is, a while later [23:30:57] - [11/Dec/2023:23:29:33 +0000] "GET /bigdata/ldf HTTP/1.1" 500 8569 "-" "check_http/v2.2 (monitoring-plugins 2.2)" [23:31:08] there's the user agent for check_http [23:31:43] and the 500, but in access.log, not error.log [23:35:19] inflatador: at least one SRE uses that client personally [23:59:00] I keep getting "Server returned error: HTTP 500." when trying to edit an article.