On Mon, Sep 13, 2021 at 01:44:45PM -0400, Stephen John Smoogen wrote: > On Mon, 13 Sept 2021 at 13:34, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > > > So, it turns out the additional debugging we setup in that sssd package > > on the ipsilon servers isn't sufficent to show what the problem is. ;( > > > > sssd developers would like us to crank up debugging to try and get logs > > of whats happening. Unfortunately, this will use a ton of disk space, > > which these vm's do not have much of. ;( > > > > I was going to ask to grow the disk on ipsilon02, but I think perhaps > > cleaner would be to create a NFS volume and mount it on /var/log/sssd/ > > on ipsilon02. This way we don't need to actually take the machine down > > and it's really easy to back out. > > > > Yeah either do an NFS or a seperate vmdisk to mount as that and then > blow away when done. > > > So, can I get +1s to: > > > > * make a NFS volume and mount it on /var/log/sssd on ipsilon02 > > * adjust ipsilon02's sssd to enable crazy levels of debug. > > * restart sssd and wait for the next failure. > > * profit! > > > > I would try this and if NFS fails then go with a seperate disk for this. +1 on either. Pierre _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
