rsyslogd crashed with SIGSEGV with juju-local configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
rsyslog (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
installing juju-local pulls in rsyslog (at least on current xenial). When doing
- juju init
- edit ~/.juju/
- juju boostrap
this creates a file /etc/rsyslog.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.14.0-2ubuntu2
ProcVersionSign
Uname: Linux 4.3.0-5-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Thu Jan 14 12:18:18 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/sbin/rsyslogd
ProcCmdline: /usr/sbin/rsyslogd -n
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x7efcf17d196e: mov 0x58(%rax),%rax
PC (0x7efcf17d196e) ok
source "0x58(%rax)" (0x00000058) not located in a known VMA region (needed readable region)!
destination "%rax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rsyslog
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: rsyslogd crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm
Changed in rsyslog (Ubuntu): | |
assignee: | nobody → Louis Bouchard (louis-bouchard) |
status: | New → Triaged |
Changed in rsyslog (Ubuntu): | |
importance: | Undecided → High |
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 just redundant (I normally don't have it).