--- Log opened Sat May 27 00:00:41 2023
11:25 <@Dagmar> FUBAR is not that bad.  The plots are kinda juvenile, and the jokes aren't much above that, but it's apparently meant to be more of a comedy than any other genre
11:40 < Evilpig> there is nothing wrong with juvenile humor.  it speaks to me
20:49 < Evilpig> what's the rule when weird shit is happening on a modern linux box and nothing seems to be making sense?
20:49 < Evilpig> that's right, disable selinux
20:55 <@Dagmar> Or, just use some sense, read the audit log, and figure out which boolean you didn't set
21:03 < Evilpig> I'm getting no audit events
21:03 < Evilpig> not sure why.  I was messing with a test vm the other day and went to some extremes to get it to start generating events
21:03 < Evilpig> for this, fuck it.  it's off for now.  if the db issues stop, it's definitely selinux related
21:04 < Evilpig> and it could just be the extra overhead of all the checks from the transactional statements with sqlite
21:04 <@Dagmar> If nothing's showing in the audit log then something not selinux is knackered
21:04 < Evilpig> something is grabbing the db and essentially locking it for about 30 seconds at a clip and then just as suddenly clears and it goes forward
21:05 < Evilpig> I'm getting events, just not blocked actions
21:05 < Evilpig> type=SERVICE_START msg=audit(1685239490.764:7410): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=check-mk-agent@2214-1138-985 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'UID="root" AUID="unset"
21:05 < Evilpig> type=SERVICE_STOP msg=audit(1685239492.115:7411): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=check-mk-agent@2214-1138-985 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'UID="root" AUID="unset"
21:06 <@Dagmar> Yeah if that's all you're seeing then selinux isn't what's causing the problems
21:06 < Evilpig> I'm not seeing any sealerts at all
21:06 < Evilpig> I should have seen  at least one
21:06 < Evilpig> ther'es ALWAYS something, at least one dumb thing
21:07 < Evilpig> call it superstition then, but I just did setenforce 0 for now and all my hangs have stopped
21:11 < Evilpig> well shit balls
21:11 < Evilpig> May 27, 2023 21:11:42.229 [140618716150584] DEBUG - 15 threads are waiting on db connections held by threads: 140618903567160,140618714041144,140618682399544,140618884860728,140618663414584,140618877860664,140618699275064,140618665524024,140618145966904,140618951265080,140618652867384,140618114747192,140618882751288,140618889464632,140618150185784,140618667633464,140618697165624,140618703493944,140618709822264,140618690906936
21:26 < Evilpig> you know I had a similar problem with this system a couple of years ago and at the time I suspected a hard drive problem.  I wonder if I have a drive controller doing something flakey
21:41 <@Dagmar> Sure sounds like it
21:46 < Evilpig> alright.  screw it.  I just ordered two samsung 2tb 870s
21:46 < Evilpig> they'll be here monday
21:47 < Evilpig> as soon as they get here i'll swap /sdb and get the remirror done, then i'll swap sda 
21:47 < Evilpig> and if I still have issues, I'll find an offering to the computer gods
--- Log closed Sun May 28 00:00:42 2023