This bug was fixed in the package rsyslog - 8.32.0-1ubuntu3
---
rsyslog (8.32.0-1ubuntu3) bionic; urgency=medium
* tmpfiles.d: Let var.conf to create /var/log with 'd' directive, and
only adjust the permissions of /var/log with 'z' directive, thus
avoiding warnings about dup
The current rsyslog does not store logs properly, nor accept remote logs
(well accepts, but they end up nowhere). This update solves all that.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Removing systemd task, as the fixes are only needed in the rsyslog
package w.r.t. permissions used.
** No longer affects: systemd (Ubuntu Bionic)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adding block-proposed to avoid automatic migration, without release team
ack.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761630
Title:
journald takes over /dev/log
Possibly duplicate of
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1748147
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761630
Title:
journald takes over /dev/log in bionic, impacts usab
** Changed in: rsyslog (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761630
Title:
journald takes over /dev/log in bionic, impacts usabilit
Hmmm is rsyslog failing to write things to files?
Apr 07 15:15:01 sochi rsyslogd[2023]: action 'action 6' suspended (module
'builtin:omfile'), retry 0. There should be messages before this one giving the
reason for suspension. [v8.32.0 try http://www.rsyslog.co
Apr 07 15:15:01 sochi rsyslogd
Looking at systemd-journald-dev-log.socket, it creates
/run/systemd/journal/dev-log socket, and that unit specifies Symlink to
take over /dev/log. And has been doing so since at least xenial (check
in a LXD container).
In journald.conf it has set #ForwardToSyslog=yes, which forwards to this
socket
** Tags added: id-5ac6b878dbf324d2105d5891
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761630
Title:
journald takes over /dev/log in bionic, impacts usability of syslog
querying
To manage noti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761630
Title:
jo
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rsyslog (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761630
Title:
jo
11 matches
Mail list logo
