With the removed delaycompress-option it is working a little bit better :
-rw-r----- 1 root adm 0 Mai 22 00:00 kern.log
-rw-r----- 1 root adm 17152 Mai 21 18:02 kern.log.1.gz
-rw-rw-r-- 1 root utmp 298368 Mai 22 02:29 lastlog
drwx------ 2 root root 4096 Mai 22 00:55 letsencrypt
drwxr-x--- 2 www-data www-data 4096 Mai 21 05:31 lighttpd
-rw-r----- 1 root adm 0 Okt 18 2020 mail.err
-rw-r----- 1 root adm 867 Mai 22 01:00 mail.info
-rw-r----- 1 root adm 462 Mai 21 17:54 mail.info.1.gz
-rw-r----- 1 root adm 867 Mai 22 01:00 mail.log
-rw-r----- 1 root adm 462 Mai 21 17:54 mail.log.1.gz
-rw-r----- 1 root adm 0 Mai 22 00:00 mail.warn
-rw-r----- 1 root adm 142 Mai 21 17:54 mail.warn.1.gz
-rw-r----- 1 root adm 154 Mai 22 00:00 messages
-rw-r----- 1 root adm 17462 Mai 21 21:09 messages.1.gz
drwxr-s--- 2 mysql adm 4096 Mai 22 00:00 mysql
-rw-r----- 1 root www-data 1042 Mai 22 02:00 ncp.log
drwxr-xr-x 2 root root 4096 Feb 20 2019 openvpn
-rw-r----- 1 root adm 54483 Mai 22 02:28 openvpn.log
-rw------- 1 root root 669 Mai 22 02:38
openvpn-status.log
-rw-r--r-- 1 root root 2516 Feb 15 07:22 pcas.txt
-rw------- 1 root root 186 Mai 21 21:21 php7.3-fpm.log
drwxr-xr-x 2 pihole pihole 4096 Jun 15 2020 pihole
-rw-r--r-- 1 pihole pihole 0 Mai 22 00:00 pihole-FTL.log
-rw-r--r-- 1 pihole pihole 11945 Mai 22 00:00 pihole-FTL.log.1
-rw-r--r-- 1 pihole pihole 0 Mai 22 00:00 pihole.log
-rw-r--r-- 1 pihole pihole 2156 Mai 22 00:00 pihole.log.1
-rw-r--r-- 1 root root 9908 Mai 16 03:11
pihole_updateGravity.log
-rw-r--r-- 1 root root 48265 Mai 15 18:34
popularity-contest
-rw-r--r-- 1 root root 16226 Mai 15 18:34
popularity-contest.new.gpg
drwx------ 2 root root 4096 Mai 27 2020 private
drwxr-s--- 2 redis adm 4096 Mai 21 05:31 redis
-rw-r----- 1 root adm 23506 Mai 22 01:54 rng.log
drwxr-x--- 3 root adm 4096 Mai 18 05:47 samba
-rw-r----- 1 root adm 16815 Mai 22 02:36 syslog
-rw-r----- 1 root adm 51224 Mai 22 00:00 syslog.1.gz
syslog is starting with:
May 22 00:00:02 debian64 rsyslogd: [origin software="rsyslogd"
swVersion="8.1901.0" x-pid="6765" x-info="https://www.rsyslog.com";]
rsyslogd was HUPed
May 22 00:00:02 debian64 systemd[1]: logrotate.service: Succeeded.
May 22 00:00:02 debian64 systemd[1]: Started Rotate log files.
May 22 00:00:02 debian64 systemd[1]: man-db.service: Succeeded.
May 22 00:00:02 debian64 systemd[1]: Started Daily man-db regeneration.
May 22 00:01:01 debian64 CRON[10633]: (root) CMD (/root/checkipv6.sh >
/dev/null 2>&1)
May 22 00:02:01 debian64 CRON[10647]: (root) CMD (/root/checkwebmin.sh >
/dev/null 2>&1)
May 22 00:05:01 debian64 CRON[10671]: (www-data) CMD (php -f
/var/www/nextcloud/cron.php)
Notice: The man-db-regeneration succeeded BEFORE starting.
I noticed that there are NEW log-entries in the OLD-syslog.1.gz-file
which belong to the new day.
May 21 23:59:01 debian64 CRON[10390]: (daemon) CMD (test -x
/usr/bin/debsecan && /usr/bin/debsecan --cron)
May 22 00:00:01 debian64 systemd[1]: Starting Daily man-db regeneration...
May 22 00:00:01 debian64 systemd[1]: Starting Rotate log files...
May 22 00:00:01 debian64 systemd[1]: Reloading The Apache HTTP Server.
May 22 00:00:01 debian64 systemd[1]: Reloaded The Apache HTTP Server.
May 22 00:00:01 debian64 CRON[10559]: (root) CMD (
PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole flush once quiet)
May 22 00:00:01 debian64 CRON[10564]: (root) CMD (
PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker local)
May 22 00:00:01 debian64 CRON[10565]: (www-data) CMD (php -f
/var/www/nextcloud/cron.php)
May 22 00:00:01 debian64 CRON[10567]: (root) CMD
(/root/checkfritzreboot.sh > /dev/null 2>&1)
May 22 00:00:01 debian64 CRON[10568]: (root) CMD (/root/check6tunnel.sh
> /dev/null 2>&1)
