[06:23] <lordievader> Good morning
[12:54] <Soni> how do you check a coredump? coredumpctl doesn't seem to be a thing...
[13:03] <Soni> yes, we git pushed to the correct place, and then we got an remote: Segmentation fault (core dumped)
[13:03] <Soni> but there's nothing about it
[13:52] <Soni> okay, pygit2 consistently segfaults when we force-push
[14:14] <azidhaka> Hi everyone, i have a NFS mount at one place in a Samba share and it shows as empty folder on the clients, what could be the cause?
[14:16] <williamo>  I have a bunch of Ubuntu 20.04 hosts that no longer boot after updating to 5.4.0-81 kernel. booting stops around the end of kernel init, right before initrd takes over. it feels like devices are timing out. only commonality I can find is that this only happens when there is a mix of disks that have been encrypted on the host side in ESX
[14:30] <JanC> in that case you should get a busybox prompt after the time-out, I think
[14:36] <JanC> actually, if it happens _before_ anything in "initrd" (and thus busybox) starts there must be something much more serious, as that gets loaded in RAM by GRUB before the kernel is started?
[14:48] <williamo> JanC, after initrd 'loads' after about 2 minutes, it segfaults and dies
[14:48] <williamo> if I remove ESX side disk encryption, the VMs will boot on -81 and -84.
[15:28] <JanC> like I said, the "initrd" gets loaded by GRUB, and it's essentially a filesystem so I don't see how it can segfault...
[15:29] <JanC> I assume there is some terminology confusion here  :)
[16:30] <williamo> JanC, this is what I'm currently looking at https://imgur.com/XHERauL
[16:32] <williamo> esx shows CPU going nuts, not much memory being used.
[16:42] <JanC> so initrd starts, but fails to mount the actual filesystems
[16:43] <JanC> because the devices it should be on aren't found
[16:47] <JanC> can't you get a busybox shell from there?  that would allow you to investigate if they don't exist or got renamed or whatever?
[19:00] <TJ-> anyone have experience deploying kereberos+openldap following the -server guide, but on attempting 'addprinc' for an existing ldap user (or non-existing) kadmin.local reports "add_principal: User modification failed: Insufficient access while creating ..."