Bug 7388

Summary:	The systemd journal is empty.
Product:	[Runtime] General Runtime	Reporter:	Randy Witt <randy.e.witt>
Component:	General Runtime	Assignee:	Randy Witt <randy.e.witt>
Status:	VERIFIED FIXED	QA Contact:	Alexandru Georgescu <alexandru.c.georgescu>
Severity:	major
Priority:	Medium+	CC:	alexandru.c.georgescu, richard.purdie, sgw
Version:	unspecified
Target Milestone:	1.8 M4
Hardware:	x86
OS:	x86_64
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	Regression (Used to work)
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Randy Witt 2015-03-03 20:54:58 UTC

Running journalctl after boot produces no results and is empty. This is on core-image-sato built using 5c1c8af083ca7b57cc339d16ce0513b27c5dac90 from poky master.

This was tested using "runqemu qemux86-64 core-image-sato ext4"

Comment 1 Randy Witt 2015-03-04 18:11:32 UTC

I'm marking this a duplicate of 7393 because I believe the journal is empty as a side effect of the failures in 7393.

If the journal is restarted after boot, it is appears to start working.

*** This bug has been marked as a duplicate of bug 7393 ***

Comment 2 Randy Witt 2015-03-06 02:04:13 UTC

This is actually a different issue than what is in bug 7393.

Comment 3 Randy Witt 2015-03-25 17:08:10 UTC

This should be fixed in master:

commit d2690754febcaff134de2085294af4561c1d9214
Author: Randy Witt <randy.e.witt@linux.intel.com>
Date:   Tue Mar 24 10:26:36 2015 -0700

You can test it manually by making sure that the command "journalctl" contains information. I also added a test called test_systemd_journal to the testimage tests.

Comment 4 Alexandru Georgescu 2015-03-26 10:16:15 UTC

I can now see journalctl log.
Tested with core-image-minimal + systemd on fido:8b3d3e7c957ad06c390886487f69aeb8e145da6a