This bug has been fixed by the latest upload of rsyslog :
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1539483. Marking
it fix released
** Changed in: juju-core (Ubuntu)
Status: Confirmed => Invalid
** Changed in: rsyslog (Ubuntu)
Status: Triaged => Fix Released
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Tested that patch, and it definitely solves the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1534106
Title:
rsyslogd crashed with SIGSEGV with juju-local
Fixed upstream in 8.15:
https://github.com/rsyslog/rsyslog/issues/575
Latest release 8.16 is in Debian, perhaps we could just sync up to it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
** Changed in: rsyslog (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1534106
Title:
rsyslogd crashed with SIGSEGV with
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: rsyslog (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Really shabby workaround for xenial: Change
/lib/systemd/system/rsyslog.service like this:
[Service]
Type=oneshot
ExecStart=/bin/true
RemainAfterExit=yes
On that note, it would really be nice if juju-local would not require
rsyslog. We have the systemd journal, so having rsyslog installed is
7 matches
Mail list logo
