[systemd-devel] systemd-journald.service failed to start with systemd v189

Lennart Poettering lennart at poettering.net
Mon Sep 24 04:05:49 PDT 2012

On Mon, 24.09.12 11:43, Nicolas Aguirre (aguirre.nicolas at gmail.com) wrote:

> Hi,
> Sometimes (around 1% of the time) my system doesn't start correctly.
> the init process takes 100% CPU. systemd-journal.service is not
> started correctly, and systemd tries to restart it in a loop.
> The log is here : http://pastebin.ca/2207127
> >From my understanding, the problem begins with
> [   12.169769] systemd[1]: Child 138 died (code=exited, status=1/FAILURE)
> [   12.169799] systemd[1]: Child 138 belongs to systemd-journald.service
> [   12.169830] systemd[1]: systemd-journald.service: main process
> exited, code=exited, status=1
> I would like to activate journald logs to see if there is debug output
> for this error. But i have no idea how to activate journal logs.
> I'm running angstrom and systemd v189 with a linux kernel v3.2.19 on
> arm cortex a8 CPU.
> Maybe somebody will have an idea ?

Hmm, most likely there's something in server_init() in journald.c
failing. Normally, if something fails there it should print a message to
kmsg about that. But apparently we missued something there... :-(

Could you try to add "log_notice()" messages at various spots in
server_init() and check if you can spot where the problem is generated?
you should see the messages in kmsg.


Lennart Poettering - Red Hat, Inc.

More information about the systemd-devel mailing list