Bug#995860: drm: Problem: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]]
Package: raspberrypi-kernel Version: 1:1.20210928-1~buster Severity: normal File: drm Dear Maintainer, I found this using dmesg and don_t know if it is relevant for a Pi4 2GB for normal operation [85186.639426] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:87:crtc-0] flip_done timed out [85196.879566] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:151:crtc-1] flip_done timed out [85207.119649] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:87:crtc-0] flip_done timed out [85217.359836] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:151:crtc-1] flip_done timed out [85227.599965] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:89:HDMI-A-1] flip_done timed out [85237.840100] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:153:HDMI-A-2] flip_done timed out [85248.080248] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:31:plane-0] flip_done timed out [85258.320371] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:95:plane-8] flip_done timed out [85268.560513] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:87:crtc-0] flip_done timed out [85278.800679] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:151:crtc-1] flip_done timed out -- System Information: Debian Release: 10.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 'oldstable') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 5.10.63-v8+ (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#991978: zram-tools: running zramswap with kernel 5.10.52 #1441 result in cpu warning
Package: zram-tools Version: 0.3.2.1-1 Severity: normal Tags: a11y Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? zramswap was running before #1441 without problems * What exactly did you do (or not do) that was effective (or ineffective)? after installting kernel update #1441 the system was running for ca. 2 days. * What was the outcome of this action? Aug 7 07:30:01 nextcloudpi kernel: [120894.788674] [ cut here ] Aug 7 07:30:01 nextcloudpi kernel: [120894.788712] WARNING: CPU: 3 PID: 14802 at kernel/rcu/tree_plugin.h:297 rcu_note_context_switch+0x64/0x428 Aug 7 07:30:01 nextcloudpi kernel: [120894.788715] Modules linked in: binfmt_misc zram zsmalloc md4 md5 nls_utf8 cifs libarc4 nft_ct tun cfg80211 rfkill 8021q garp stp llc sg vc4 cec v3d bcm283 Aug 7 07:30:01 nextcloudpi kernel: [120894.788906] sha256_generic aes_neon_blk crypto_simd cryptd ip_tables x_tables ipv6 [last unloaded: zsmalloc] Aug 7 07:30:01 nextcloudpi kernel: [120894.788931] CPU: 3 PID: 14802 Comm: cron Tainted: G C5.10.52-v8+ #1441 Aug 7 07:30:01 nextcloudpi kernel: [120894.788934] Hardware name: Raspberry Pi 4 Model B Rev 1.2 (DT) Aug 7 07:30:01 nextcloudpi kernel: [120894.788940] pstate: 2085 (nzCv daIf -PAN -UAO -TCO BTYPE=--) Aug 7 07:30:01 nextcloudpi kernel: [120894.788945] pc : rcu_note_context_switch+0x64/0x428 Aug 7 07:30:01 nextcloudpi kernel: [120894.788949] lr : rcu_note_context_switch+0x54/0x428 Aug 7 07:30:01 nextcloudpi kernel: [120894.788951] sp : ffc013bd3ac0 Aug 7 07:30:01 nextcloudpi kernel: [120894.788954] x29: ffc013bd3ac0 x28: ff806b771e40. Aug 7 07:30:01 nextcloudpi kernel: [120894.788961] x27: x26: ffc011476000. Aug 7 07:30:01 nextcloudpi kernel: [120894.788968] x25: x24: ff807fbbf240. Aug 7 07:30:01 nextcloudpi kernel: [120894.788973] x23: x22: ff806b771e40. Aug 7 07:30:01 nextcloudpi kernel: [120894.788979] x21: ffc011462328 x20: ffc011298948. Aug 7 07:30:01 nextcloudpi kernel: [120894.788986] x19: ff807fbbfec0 x18: . Aug 7 07:30:01 nextcloudpi kernel: [120894.788991] x17: x16: . Aug 7 07:30:01 nextcloudpi kernel: [120894.788997] x15: x14: . Aug 7 07:30:01 nextcloudpi kernel: [120894.789003] x13: x12: . Aug 7 07:30:01 nextcloudpi kernel: [120894.789009] x11: x10: . Aug 7 07:30:01 nextcloudpi kernel: [120894.789015] x9 : ffc010acffb8 x8 : . Aug 7 07:30:01 nextcloudpi kernel: [120894.789021] x7 : x6 : ffc013bd3ab0. Aug 7 07:30:01 nextcloudpi kernel: [120894.789026] x5 : 0001 x4 : ffc06ebe3000. Aug 7 07:30:01 nextcloudpi kernel: [120894.789033] x3 : 0001 x2 : ffc010fc7000. Aug 7 07:30:01 nextcloudpi kernel: [120894.789039] x1 : ffc06ebe3000 x0 : 0001. Aug 7 07:30:01 nextcloudpi kernel: [120894.789046] Call trace: Aug 7 07:30:01 nextcloudpi kernel: [120894.789051] rcu_note_context_switch+0x64/0x428 Aug 7 07:30:01 nextcloudpi kernel: [120894.789060] __schedule+0xc8/0x818 Aug 7 07:30:01 nextcloudpi kernel: [120894.789063] schedule+0x48/0x100 Aug 7 07:30:01 nextcloudpi kernel: [120894.789066] io_schedule+0x24/0xb0 Aug 7 07:30:01 nextcloudpi kernel: [120894.789072] __lock_page_or_retry+0x1cc/0x498 Aug 7 07:30:01 nextcloudpi kernel: [120894.789077] do_swap_page+0x1f4/0x700 Aug 7 07:30:01 nextcloudpi kernel: [120894.789081] handle_mm_fault+0x4a8/0xcb8 Aug 7 07:30:01 nextcloudpi kernel: [120894.789085] do_page_fault+0x148/0x3e8 Aug 7 07:30:01 nextcloudpi kernel: [120894.789089] do_translation_fault+0x58/0x70 Aug 7 07:30:01 nextcloudpi kernel: [120894.789095] do_mem_abort+0x48/0xa8 Aug 7 07:30:01 nextcloudpi kernel: [120894.789099] el0_da+0x40/0x58 Aug 7 07:30:01 nextcloudpi kernel: [120894.789104] el0_sync_handler+0x68/0xb8 Aug 7 07:30:01 nextcloudpi kernel: [120894.789108] el0_sync+0x180/0x1c0 Aug 7 07:30:01 nextcloudpi kernel: [120894.789112] ---[ end trace 586c9eec844f90cf ]--- * What outcome did you expect instead? normal operation *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.10 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 5.10.52-v8+ (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_CRAP Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
> syslog.1 is newer then syslog. So some log messages ended up in syslog, > but rsyslog then continued to write to syslog.1 ? > If you were referring to that problem, can you share what has been > written to syslog and syslog.1? Please take a look on my message from Sat, 22 May 2021 03:18:01 +0200, where I uploaded parts of syslog und syslog.1. The protocols look similar today.The entries in syslog.1 do not end at midnight.
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
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)
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
Maybe a helpful idea/reason/solution for the problem? A website in German: https://debianforum.de/forum/viewtopic.php?f=32=180761=syslog
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
The actual situation is today the same than yesterday. The system is writing to the old files. using a systemctl kill -s HUP --kill-who=main rsyslog.service didn't help. The system was still writing to the old syslog.1-file while the new syslog content's kern.log messages. Only a pkill -HUP rsyslogd helped. the kernel is Linux debian64 5.10.17-v8+ #1414 SMP PREEMPT Fri Apr 30 13:23:25 BST 2021 aarch64 GNU/Linux cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL="https://www.debian.org/; SUPPORT_URL="https://www.debian.org/support; BUG_REPORT_URL="https://bugs.debian.org/; -- Looking on a second server with the original /usr/lib/rsyslog/rsyslog-rotate -version and kernel Linux localhost 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL="https://www.debian.org/; SUPPORT_URL="https://www.debian.org/support; BUG_REPORT_URL="https://bugs.debian.org/; Here everything works fine.
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
Thanks for the killall-warning. I tried the different commands in the terminal. systemctl kill -s HUP rsyslog.service 2 lines with HUP-notice are shown in syslog. systemctl kill -s HUP --kill-who=main rsyslog.service 2 lines with HUP-notice are shown in syslog. pkill -HUP rsyslogd 4 lines with HUP-notice are shown in syslog. There is 1 main process and 3 childs.
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
I found this in the internet: https://github.com/rsyslog/rsyslog/issues/3952 I will give it a try by changing |#!/bin/sh if [ -d /run/systemd/system ]; then systemctl kill -s HUP rsyslog.service else invoke-rc.d rsyslog rotate > /dev/null fi to ||#!/bin/sh if [ -d /run/systemd/system ]; then ||killall -HUP rsyslogd else ||killall -HUP rsyslogd fi Then I manually restarted the rsyslog.service and startet journalctl --rotate. I will see. |||
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
A morning surprise: After I reset the / usr/ lib/ rsyslog /rsyslog-rotate fileto the original-version the content of kern.log, syslog and messages is almost identical. The syslog file seems to be rotated, but thesystem is writing to syslog.1 while the syslog-file has kern.log-content.Currently the content of the 3 files kern.log, syslog and messages is almost identical. I tried to restart with systemtl restart rsyslogd.service = no effect journalctl --rotate = no effect syslog.1: May 19 06:59:01 debian64 CRON[865]: (daemon) CMD (test -x /usr/bin/debsecan && /usr/bin/debsecan --cron) May 19 07:00:01 debian64 CRON[880]: (root) CMD ( PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker local) May 19 07:00:01 debian64 CRON[881]: (www-data) CMD (php -f /var/www/nextcloud/cron.php) May 19 07:00:01 debian64 CRON[882]: (root) CMD (/root/check6tunnel.sh > /dev/null 2>&1) May 19 07:00:01 debian64 CRON[885]: (root) CMD (/root/checkfritzreboot.sh > /dev/null 2>&1) May 19 07:00:01 debian64 systemd[11441]: mnt-fritznas.mount: Succeeded. May 19 07:00:01 debian64 systemd[1]: mnt-fritznas.mount: Succeeded. May 19 07:00:01 debian64 systemd[607]: mnt-fritznas.mount: Succeeded. May 19 07:01:01 debian64 CRON[925]: (root) CMD (/root/checkipv6.sh > /dev/null 2>&1) May 19 07:02:01 debian64 CRON[1076]: (root) CMD (/root/checkwebmin.sh > /dev/null 2>&1) May 19 07:03:27 debian64 dhcpcd[383]: eth0: Router Advertisement from fe80::2e91:abff:123:e8b2 May 19 07:05:01 debian64 CRON[1120]: (www-data) CMD (php -f /var/www/nextcloud/cron.php) May 19 07:06:27 debian64 dhcpcd[383]: eth0: Router Advertisement from fe80::2e91:abff:123:e8b2 May 19 07:09:00 debian64 systemd[1]: Starting Clean php session files... May 19 07:09:00 debian64 systemd[1]: phpsessionclean.service: Succeeded. May 19 07:09:00 debian64 systemd[1]: Started Clean php session files. May 19 07:09:01 debian64 CRON[1286]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi) May 19 07:10:01 debian64 CRON[1415]: (root) CMD ( PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker local) May 19 07:10:01 debian64 CRON[1416]: (www-data) CMD (php -f /var/www/nextcloud/cron.php) May 19 07:15:01 debian64 CRON[1545]: (www-data) CMD (php -f /var/www/nextcloud/cron.php) May 19 07:16:16 debian64 dhcpcd[383]: eth0: Router Advertisement from fe80::2e91:abff:123:e8b2 May 19 07:17:01 debian64 CRON[1576]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 19 07:18:20 debian64 systemd[1]: Stopping System Logging Service... May 19 07:18:20 debian64 rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="302" x-info="https://www.rsyslog.com;] exiting on signal 15. May 19 07:18:20 debian64 systemd[1]: rsyslog.service: Succeeded. May 19 07:18:20 debian64 systemd[1]: Stopped System Logging Service. May 19 07:18:20 debian64 systemd[1]: Starting System Logging Service... May 19 07:18:20 debian64 rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0] May 19 07:18:20 debian64 rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="1593" x-info="https://www.rsyslog.com;] start May 19 07:18:20 debian64 systemd[1]: Started System Logging Service. May 19 07:20:01 debian64 CRON[1614]: (www-data) CMD (php -f /var/www/nextcloud/cron.php) May 19 07:20:01 debian64 CRON[1613]: (root) CMD ( PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker local) May 19 07:24:10 debian64 dhcpcd[383]: eth0: Router Advertisement from fe80::2e91:abff:123:e8b2 May 19 07:25:01 debian64 CRON[1810]: (www-data) CMD (php -f /var/www/nextcloud/cron.php) May 19 07:25:12 debian64 dhcpcd[383]: eth0: Router Advertisement from fe80::2e91:abff:123:e8b2 --- syslog: May 19 00:30:01 debian64 kernel: [543701.990594] CIFS: Attempting to mount //fritz.box/fritz.nas/ May 19 01:00:01 debian64 kernel: [545501.705868] CIFS: Attempting to mount //fritz.box/fritz.nas/ May 19 02:30:01 debian64 kernel: [550902.133413] CIFS: Attempting to mount //fritz.box/fritz.nas/ May 19 03:00:02 debian64 kernel: [552702.512337] CIFS: Attempting to mount //fritz.box/fritz.nas/ May 19 05:00:01 debian64 kernel: [559902.394223] CIFS: Attempting to mount //fritz.box/fritz.nas/ May 19 05:30:01 debian64 kernel: [561701.838038] CIFS: Attempting to mount //fritz.box/fritz.nas/ May 19 07:00:01 debian64 kernel: [567102.215190] CIFS: Attempting to mount //fritz.box/fritz.nas/ messages: May 18 16:22:24 debian64 rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0"
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
Yes, it is very easy.But I think that I will only be able to see in a few days whether the old behavior will return.Please be patient. On Tue, 18 May 2021 18:18:37 +0200 Michael Biebl wrote: > Am 18.05.21 um 17:05 schrieb Michael Biebl: > > Am 18.05.21 um 16:37 schrieb UN-pi: > >> "systemctl status rsyslog.service" say: > >> > >> rsyslog.service - System Logging Service > >> Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor > >> preset: enabled) > >> Active: active (running) since Wed 2021-05-12 17:27:41 CEST;5 days > >> ago > >> Docs: man:rsyslogd(8) > >> https://www.rsyslog.com/doc/ > >> Main PID: 302 (rsyslogd) > >> Tasks: 4 (limit: 1968) > >> CGroup: /system.slice/rsyslog.service > >> └─302 /usr/sbin/rsyslogd -n -iNONE > >> > > > > Ok, so you have single process. I don't see how --kill-who=main is going > > to make a difference here. > > > > Could you switch back to the original version without "--kill-who=main" > > and verify that this reintroduces the problem for you? >
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
"systemctl status rsyslog.service" say: rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2021-05-12 17:27:41 CEST; 5 days ago Docs: man:rsyslogd(8) https://www.rsyslog.com/doc/ Main PID: 302 (rsyslogd) Tasks: 4 (limit: 1968) CGroup: /system.slice/rsyslog.service └─302 /usr/sbin/rsyslogd -n -iNONE Mai 16 00:00:03 debian64 rsyslogd[302]: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="302" x-info="https://www.rsyslog.com;] rsyslogd was HUPed Mai 16 00:00:03 debian64 rsyslogd[302]: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="302" x-info="https://www.rsyslog.com;] rsyslogd was HUPed Mai 17 00:00:03 debian64 rsyslogd[302]: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="302" x-info="https://www.rsyslog.com;] rsyslogd was HUPed Mai 18 00:00:02 debian64 rsyslogd[302]: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="302" x-info="https://www.rsyslog.com;] rsyslogd was HUPed Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. -- The htop-program has 1 main task and 3 childs.
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
On Tue, 18 May 2021 14:23:14 +0200 Michael Biebl wrote: > On Tue, 18 May 2021 14:10:08 +0200 =?UTF-8?Q?Christian_G=C3=B6ttsche?= > wrote: > > > Based on Samuel's comment, modified /usr/lib/rsyslog/rsyslog-rotate > > > #!/bin/sh > > > > > > if [-d /run/systemd/system]; then > > > systemctl kill -s HUP --kill-who = main rsyslog.service > > > else > > > invoke-rc.d rsyslog rotate> /dev/null > > > fi > > > " > > > > > > Is it a bug or do I have an understanding problem somewhere? > > > > > What exactly did you change in the script? Please post a diff (or the > file before and after the modifications you did). > > This is my actual file: #!/bin/sh #based on #https://askubuntu.com/questions/695999/var-log-syslog-not-rotating #if [ -d /run/systemd/system ]; then # systemctl kill -s HUP rsyslog.service #else # invoke-rc.d rsyslog rotate > /dev/null #fi if [ -d /run/systemd/system ]; then systemctl kill -s HUP --kill-who=main rsyslog.service else invoke-rc.d rsyslog rotate > /dev/null fi - logrotate -v /etc/logrotate.conf is running journalctl -u logrotate says: -- Logs begin at Sat 2021-05-15 07:00:01 CEST, end at Tue 2021-05-18 14:51:27 CEST. -- Mai 16 00:00:01 debian64 systemd[1]: Starting Rotate log files... Mai 16 00:00:03 debian64 systemd[1]: logrotate.service: Succeeded. Mai 16 00:00:03 debian64 systemd[1]: Started Rotate log files. Mai 17 00:00:01 debian64 systemd[1]: Starting Rotate log files... Mai 17 00:00:03 debian64 systemd[1]: logrotate.service: Succeeded. Mai 17 00:00:03 debian64 systemd[1]: Started Rotate log files. Mai 18 00:00:01 debian64 systemd[1]: Starting Rotate log files... Mai 18 00:00:02 debian64 systemd[1]: logrotate.service: Succeeded. Mai 18 00:00:02 debian64 systemd[1]: Started Rotate log files. It is the first time that I have made such a report via reportbug. I can only hope that I comply with the reporting rules to some extent.
Bug#988652: logrotate: kern.log,syslog and other files in /var/log not rotating
Package: logrotate Version: 3.14.0-4 Severity: normal Tags: newcomer Dear Maintainer, I noticed that some log files in /var/log are not being rotated. e.g. kern.log, syslog etc. There are no files ending with .1 or .gz. The files keep getting bigger. I found on the internet: https://askubuntu.com/questions/695999/var-log-syslog-not-rotating. After I make the change it seems to work. Extract from the website: " Based on Samuel's comment, modified /usr/lib/rsyslog/rsyslog-rotate #!/bin/sh if [-d /run/systemd/system]; then systemctl kill -s HUP --kill-who = main rsyslog.service else invoke-rc.d rsyslog rotate> /dev/null fi " Is it a bug or do I have an understanding problem somewhere? -- Package-specific info: Contents of /etc/logrotate.d total 100 -rw-r--r-- 1 root root 120 Apr 19 2019 alternatives -rw-r--r-- 1 root root 442 Jun 18 2020 apache2 -rw-r--r-- 1 root root 173 May 28 2019 apt -rw-r--r-- 1 root root 79 Feb 13 2019 aptitude -rw-r--r-- 1 root root 297 Aug 20 2019 asterisk -rw-r--r-- 1 root root 130 Aug 29 2018 btmp -rw-r--r-- 1 root root 82 May 26 2018 certbot -rw-r--r-- 1 root root 112 Apr 19 2019 dpkg -rw-r--r-- 1 root root 313 Apr 4 2018 fail2ban -rw-r--r-- 1 root root 234 Mar 1 2018 iaxmodem -rw-r--r-- 1 root root 419 Jan 28 2019 lighttpd -rw-r--r-- 1 root root 97 Jun 18 2020 log2ram -rw-r--r-- 1 root root 802 Jan 29 2020 mysql-server -r--r--r-- 1 root root 111 May 15 07:45 ncp -rw-r--r-- 1 root root 182 Nov 11 2020 openvpn -rw-r--r-- 1 root root 155 Oct 26 2019 php7.3-fpm -rw-r--r-- 1 root root 1029 Jan 25 2019 psaccs_atop -rw-r--r-- 1 root root 541 Jan 25 2019 psaccu_atop -rw-r--r-- 1 root root 124 Jul 10 2019 redis-server -rw-r--r-- 1 root root 501 Feb 26 2019 rsyslog -rw-r--r-- 1 root root 891 Sep 2 2019 samba -rw-r--r-- 1 root root 188 Jun 15 2020 ufw -rw-r--r-- 1 root root 235 Jun 8 2019 unattended-upgrades -rw-r--r-- 1 root root 305 Sep 2 2019 winbind -rw-r--r-- 1 root root 145 Feb 19 2018 wtmp -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 5.10.17-v8+ (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages logrotate depends on: ii cron [cron-daemon] 3.0pl1-134+deb10u1 ii libacl1 2.2.53-4 ii libc6 2.28-10 ii libpopt01.16-12 ii libselinux1 2.8-1+b1 ii systemd-sysv241-7~deb10u7 Versions of packages logrotate recommends: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1 logrotate suggests no packages. -- no debconf information
