04-11-2025, 07:10 PM
(04-11-2025, 06:01 PM)Tim Curtis Wrote: Nvm.
This is prolly the cause of the logrotate error.
Code:pi@moode9scn:~ $ ls -l /etc/logrotate.d/
total 52
-rw-r--r-- 1 root root 120 Feb 14 2023 alternatives
-rw-r--r-- 1 root root 173 May 25 2023 apt
-rw-r--r-- 1 root root 130 Oct 14 2019 btmp
-rw-r--r-- 1 root root 112 Feb 14 2023 dpkg
-rw-r--r-- 1 pi pi 97 Sep 18 2024 log2ram
-rw-r--r-- 1 root root 186 Jun 19 2023 minidlna
-rw-r--r-- 1 root root 101 Jul 16 2019 mpd
-rw-r--r-- 1 root root 329 Mar 14 2023 nginx
-rw-r--r-- 1 root root 215 Nov 25 12:21 php8.2-fpm
-rw-r--r-- 1 root root 94 Apr 11 2022 ppp
-rw-r--r-- 1 root root 875 Oct 10 2023 samba
-rw-r--r-- 1 root root 353 Oct 10 2023 winbind
-rw-r--r-- 1 root root 145 Oct 14 2019 wtmp
I'll investigate why the user:group is pi:pi instead of root:root and fix it but that log rotate error shouldn't have anything to do with the log2ram service.
Erm. We find in /etc/logrotate.d the file log2ram so, yes, the logrotate service will touch the log2ram log. Now that I know to look, I see the OP's error in the journals of the two players currently powered up here.
Incidentally, there seem to be some other, unrelated errors in that directory.
Cases in point,
- file /etc/logrotate.d/mpd refers to files /var/log/mpd/*.log which won't pick up the actual mpd log file /var/log/mpd/log.
- file ppp refers to file /var/log/ppp- connect-errors. Should these be "php" or are we really referring to the old point to point protocol used with dial-up modems?
I haven't looked carefully at logrotate to see where permissions matter.
Regards,
Kent
