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
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 w
> 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 +020
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 ro
Maybe a helpful idea/reason/solution for the problem?
A website in German:
https://debianforum.de/forum/viewtopic.php?f=32&t=180761&hilit=syslog
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
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
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 |
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
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.r
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 -
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.co
13 matches
Mail list logo
