touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Public bug reported:

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

** Affects: juju-core (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: rsyslog (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-crash need-amd64-retrace xenial

** Summary changed:

- rsyslogd crashed with SIGSEGV
+ rsyslogd crashed with SIGSEGV with juju-local configuration

** Information type changed from Private to Public

** Also affects: juju-core (Ubuntu)
   Importance: Undecided
       Status: New

-- 
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 configuration

Status in juju-core package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1534106/+subscriptions