[07:27:37] <Amir1>	 marostegui: okay if I restart the parsercache clean up in eqiad?
[07:28:17] <marostegui>	 Amir1: yeah
[07:28:22] <Amir1>	 awesome
[08:38:21] <Emperor>	 db2189 is acked but not resolved; is that something someone's working on?
[08:41:13] <Emperor>	 Ah, yes, T384202
[08:41:13] <stashbot>	 T384202: db2189 replication broken - https://phabricator.wikimedia.org/T384202
[08:41:59] <Emperor>	 marostegui: do you think that'll be done before the p.age fires again, should I resolve the VO incident, ...?
[08:47:25] <marostegui>	 Emperor: it may take a bit longer than usual as I'll teach federico3 how to deal with it
[08:47:45] <marostegui>	 Emperor: please resolve it if you don't mind 
[08:55:38] <Emperor>	 {{done}}
[09:08:00] <marostegui>	 thank you
[13:48:23] <Emperor>	 ms-fe1014 seems unhappy (and I get EIO trying to log in)
[13:52:27] <Emperor>	 oh, great, the reboot cookbook barfs too
[13:52:36] <Emperor>	 ValueError: invalid literal for int() with base 10: 'bash: /etc/bash.bashrc: Input/output error\nxargs: echo: Input/output error\nxargs: echo: Input/output error\nxargs: echo: Input/output error\n0'
[13:53:14] <volans>	 it probably needs a hard reboot via ipmi/redfish/mgmt console/iDRAC UI
[13:53:27] <Emperor>	 gah, I wish everything would stop all breaking at once :(
[13:58:37] <Emperor>	 Wow, that's a "the RAID controller is doomed, all is doomed" console message
[13:59:02] <Emperor>	 I'll open a ticket for dc-ops with a screenshot
[14:03:39] <Emperor>	 T384317
[14:03:39] <stashbot>	 T384317: ms-fe1014 hardware fault (may need new disk controller?) - https://phabricator.wikimedia.org/T384317
[15:22:42] * Emperor alarmed by Dell saying we've the wrong drives in ms-be2075, given Dell sold it to us :(
[15:22:55] <Emperor>	 context: T382707
[15:22:55] <stashbot>	 T382707: Frequent disk resets on ms-be2075 - https://phabricator.wikimedia.org/T382707
[17:56:13] <swfrench-wmf>	 greetings data-persistence friends - following up here about switching pc sections over to the parsercache flavor, what I'd propose is fairly simple [0].
[17:56:14] <swfrench-wmf>	 given the desire to coordinate potentially conflicting changes, perhaps we could aim for some time Wednesday (tomorrow)? I'm happy to start my day on the early side :)
[17:56:14] <swfrench-wmf>	 [0] https://phabricator.wikimedia.org/T383324#10480877
[17:57:50] <volans>	 just do it when the team is asleep, to avoid any conflict :-P
[17:57:54] * volans hides
[18:04:16] <swfrench-wmf>	 lol
[18:13:19] <marostegui>	 swfrench-wmf: we can do it tomorrow yeah 
[18:37:39] <swfrench-wmf>	 marostegui: sounds good - I'll aim to be here by 15:00 UTC tomorrow to check in and find a time. I can also do a bit earlier if that works better. thanks!