#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #967906 (http://bugs.debian.org/967906)
PS: I do not see, how logrotate affects the systemctl command
line to send a HUP to rsyslog, though.
?
On 8/7/20 4:56 PM, Christian Göttsche wrote:
Is this maybe related to #720096 and #831764 ?
logrotate calling the rsyslog-rotate wrapper twice (one time for
/var/log/syslog and another time for the rest (/var/log/mail.* etc.))
and the second time rsyslog is not (yet) ready to receive the SIGHUP
On 8/7/20 1:55 PM, Michael Biebl wrote:
What's the output of logrotate -v /etc/logrotate.d/rsyslog
Sorry, I should have included this right from the start.
srvvm01:~# logrotate -v /etc/logrotate.d/rsyslog
reading config file /etc/logrotate.d/rsyslog
Reading state from file: /var/lib/logrotat
On 8/8/20 11:54 AM, Michael Biebl wrote:
What's the output of
journalctl -b -u systemd-journald.service
srvvm01:~# journalctl -b -u systemd-journald.service
-- Logs begin at Mon 2020-08-10 00:04:18 CEST, end at Mon 2020-08-10 10:19:18
CEST. --
-- No entries --
On 8/10/20 10:19 AM, Harald Dunkel wrote:
On 8/8/20 11:54 AM, Michael Biebl wrote:
What's the output of
journalctl -b -u systemd-journald.service
srvvm01:~# journalctl -b -u systemd-journald.service
-- Logs begin at Mon 2020-08-10 00:04:18 CEST, end at Mon 2020-08-10 10:19:18
CEST. --
-- No
