Followup to this. It happened again, but while I was asleep this time. Had to just restart php-fpm in a panic, so still couldn't debug. Something happens at 3am once in a blue moon that is triggering this. I'm convinced it's systemd-tmpfiles-clean.timer now because before I rebooted I looked at /tmp and there was maybe 2-3 systemd "systemd-private-*" dirs... and after I rebooted there are 20. So it looks like the default systemd cleaner is mental. It was never a problem before. Some update must have broken it. I had not configured a single thing about it: it was running on full defaults.
From what I gather it's only supposed to clean systemd-private dirs that are stale from dead ps's. But clearly that it's hosing whole whacks of them. I'm shocked other daemons haven't been blowing up!
So I did what I did on my Fedora boxes ages ago: systemctl mask systemd-tmpfiles-clean.timer systemctl mask systemd-tmpfiles-clean.service Note, you can't use disable, it must be mask. I guess there's a reason I learned to mask these on Fedora... Have I mentioned I hate systemd? This is a huge, expensive, for-pay legit RHEL9 production box and I'm having to fight with this stuff? P.S. I'm a bit puzzled why the cleaner dir hose affected php-fpm though since I had done PrivateTmp=false after the last time. _______________________________________________ Roundtable mailing list -- roundtable@muug.ca To unsubscribe send an email to roundtable-leave@muug.ca