Michal Soltys

Additional info: I've added -E0 and multiple -v options to btrfs-receive, this is how it looks in the debug log: ``` utimes home/ansible unlink o123789-148160-0 utimes var/lib/postgresql utimes var/lib/postgresql mkfile...

For the record, still happening with: kernel: 4.20.12 btrfs-progs: 4.20.1

For the record I still have the btrfs filesystem mentioned in the first post - in case it could help with this bug.

We noticed probably the same issue with unbound while trying to upgrade from 1.6.0 (old version in debian stretch - where with identical config we have never had any issues)...

Hmm, looking at other queries that we had in the logs that probably was the issue (e.g. .service.internal. - as these went straight to root servers). I've tested manually compiled...

So to sum up I've tested 1.6.0 (early stretch), 1.13.1 (bullseye), 1.16.1 (manually compiled): 1.6.0 and 1.16.1 work fine, regardless if `harden-below-nxdomain` is or isn't enabled; 1.13.1 will prioritize higher...

Can confirm this - same exact message. Disabling Hojoring makes ACT exit cleanly.

I've run this with TRACE enabled and I think I've found the underlying issue: - our original filter for users eligible for activation is: `(&(objectclass=toukPerson)(toukAccountActive=TRUE)(pwdAccountLockedTime=000001010000Z))` We filter on `pwdAccountLockedTime` because...

This would be fantastic, but also a massive undertaking going into territory of mods like NAIOM (for Nier). Just fixing camera auto-adjust and reset on target-lock will do wonders for...

For the record, this is still an issue in version 2.0.4 (forcing content-type to application/json with e.g. curl's -H workarounds the issue as well)