systemd-journald crashed with signal 7

Bug #1389355 reported by Christian Kirbach
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I am not sure how I triggered this.
What I can say is that journalctl does not find any journals to show.

nazgul@rivendell:~$ journalctl
No journal files were found.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: systemd 208-8ubuntu8 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Tue Nov 4 01:21:58 2014
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2013-01-08 (665 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcCmdline: /lib/systemd/systemd-journald
Signal: 7
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-journald crashed with signal 7
UpgradeStatus: Upgraded to utopic on 2014-10-23 (12 days ago)
UserGroups:

Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 stdout_stream_free (s=0xcf81d0) at ../src/journal/journald-stream.c:323
 process_event (s=0x7fff66d165c0, ev=0x7fff66d165b0) at ../src/journal/journald-server.c:1311
 main (argc=<optimized out>, argv=<optimized out>) at ../src/journal/journald.c:118

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 systemd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Martin Pitt (pitti) wrote :

Did you actually boot with systemd as PID1? Note that this isn't supported in Ubuntu 14.10 (only upstart). On current vivid, running "journalctl" under upstart just exits cleanly with 1. Can you reproduce this crash easily, i. e. does it still happen on your system if you run journalctl? (the stack trace isn't very helpful, I'm afraid).

Changed in systemd (Ubuntu):
status: New → Incomplete
information type: Private → Public
Revision history for this message
dino99 (9d9) wrote :

Confirm that issue on Vivid i386 booted with systemd, but without crashing:
- 'journalctl' does not find the journal
-'sudo journalctl' does (lp:1414409)

Changed in systemd (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

This is fixed in Ubuntu Vivid (and systemd/journal are not supported in 14.10 anyway).

Changed in systemd (Ubuntu):
status: Confirmed → Fix Released
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.