On Wed 26 Jul 2023 at 10:07:34 (-0400), gene heskett wrote: > And since bookworm has shut down, or moved, all the logs that might > keep track of this, I'm lost. What can I do to trace or fix the reason > for this denial of service? I know zip about your new ACL stuff if > thats even involved. IDK. Is there a special version of chown for > raid arrays? > And where the heck are the logs, they should be in the /var directory > of the drive its booted from which s/b /dev/sda, but df thinks its: > now /dev/sda, last boot it was /dev/sdb, so much for UUID's. I have > not moved any cables. One is a 500G samsung 860 SSD, the other a 1t > Samsung 870 SSD. > An ls of /var/log: > gene@coyote:~$ ls /var/log > alternatives.log apache2 boot.log boot.log.2 boot.log.4 btmp > cups dpkg.log.1 faillog gdm3 journal private > runit sddm.log wtmp > alternatives.log.1 apt boot.log.1 boot.log.3 boot.log.5 > btmp.1 dpkg.log exim4 fontconfig.log installer lastlog > README samba > speech-dispatcher > > So where are syslog and dmesg?
I take it you didn't bother to read ยง5.1.7 of the bookworm Release Notes. Cheers, David.
