Log rotation after bullseye upgrade

Log messages suggest that it is succeeding, but it looks like log rotation on my Pioneer Edition (You are running Debian GNU/Linux 11 (bullseye) and FreedomBox version 21.4.4. FreedomBox is up to date.) hasn’t occurred since it upgraded to bullseye on Aug 16.

I do have a notification “A scheduled backup failed. Past 1 attempts for backup did not succeed. The latest error is: database is locked”. Are backups and log rotation intertwined?

xxx@freedombox:~$ ls -l /var/log/sys*
-rw-r----- 1 root adm 4107740 Aug 21 10:00 /var/log/syslog
-rw-r----- 1 root adm 642600 Aug 16 00:00 /var/log/syslog.1
-rw-r----- 1 root adm 47362 Aug 15 00:00 /var/log/syslog.2.gz
-rw-r----- 1 root adm 35024 Aug 14 00:00 /var/log/syslog.3.gz
-rw-r----- 1 root adm 34016 Aug 13 00:00 /var/log/syslog.4.gz
-rw-r----- 1 root adm 43597 Aug 12 00:00 /var/log/syslog.5.gz
-rw-r----- 1 root adm 38013 Aug 11 00:00 /var/log/syslog.6.gz
-rw-r----- 1 root adm 30283 Aug 10 00:00 /var/log/syslog.7.gz

Aug 21 00:00:20 freedombox systemd[1]: logrotate.service: Succeeded.
Aug 21 00:00:20 freedombox systemd[1]: Finished Rotate log files.
Aug 21 00:00:20 freedombox systemd[1]: logrotate.service: Consumed 2.052s CPU time.

Not sure if it’s related or just transient, but this morning I got (for the first time) a logrotate failure with the message “logrotate_script: 2: /usr/lib/php/php7.3-fpm-reopenlogs: not found”

What I find in /usr/lib/php is php7.4-fpm-reopenlogs.

I also get this error. Checking my SD card, I have /etc/logrotate.d/php7.3-fpm, but not /usr/lib/php/php7.3-fpm-reopenlogs.

/etc/logrotate.d/php7.3-fpm is part of the php7.3-fpm package. The package has been uninstalled, but not purged, so configuration files in /etc were left behind.

There is a fix to avoid this in newer versions of php*-fpm:

For now, it seems you can go ahead and purge the php7.3-fpm package (I did not test this yet).