rsyslogd crashed with SIGSEGV with juju-local configuration

Bug #1534106 reported by Martin Pitt
26
This bug affects 3 people
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/environments.yaml to set "local" as default
- juju boostrap

this creates a file /etc/rsyslog.d/25-juju-USERNAME-local.conf and restarts rsyslog. rsyslog then crashes like this with this configuration.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.14.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
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/rsyslog/lmnsd_gtls.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 ?? () from /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
Title: rsyslogd crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm

Revision history for this message
Martin Pitt (pitti) wrote :
summary: - rsyslogd crashed with SIGSEGV
+ rsyslogd crashed with SIGSEGV with juju-local configuration
information type: Private → Public
Revision history for this message
Martin Pitt (pitti) wrote :

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).

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtlsClientCertCallback (session=<optimized out>, req_ca_rdn=<optimized out>, nreqs=<optimized out>, sign_algos=<optimized out>, sign_algos_length=<optimized out>, st=0x7efceed3e720) at nsd_gtls.c:254
 call_get_cert_callback () from /tmp/apport_sandbox_GOcefj/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 _gnutls_server_select_cert () from /tmp/apport_sandbox_GOcefj/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 remove_unwanted_ciphersuites () from /tmp/apport_sandbox_GOcefj/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28
 _gnutls_server_select_suite () from /tmp/apport_sandbox_GOcefj/usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in juju-core (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Martin Pitt (pitti)
Changed in rsyslog (Ubuntu):
assignee: nobody → Louis Bouchard (louis-bouchard)
status: New → Triaged
Changed in rsyslog (Ubuntu):
importance: Undecided → High
Revision history for this message
Trent Lloyd (lathiat) wrote :

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?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in juju-core (Ubuntu):
status: New → Confirmed
Revision history for this message
Trent Lloyd (lathiat) wrote :

Tested that patch, and it definitely solves the issue for me.

Revision history for this message
Louis Bouchard (louis) wrote :

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
assignee: Louis Bouchard (louis-bouchard) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.