[Dev] smack setup incomplete, systemd-journal fails

Schaufler, Casey casey.schaufler at intel.com
Wed Dec 18 19:31:45 GMT 2013

> -----Original Message-----
> From: dev-bounces at lists.tizen.org [mailto:dev-bounces at lists.tizen.org] On
> Behalf Of Lukasz Stelmach
> Sent: Wednesday, December 18, 2013 9:52 AM
> To: dev at lists.tizen.org
> Subject: [Dev] smack setup incomplete, systemd-journal fails
> Hi,
> I've got quite a recent RD-PQ image: tizen_20131217.8. There is a problem
> with systemd-journald failing to start because

Where did you get this image? What are you running it on?

> + "Failed to open /dev/kmsg, ignoring: Permission denied"

This looks like you don't have the systemd rules file 55-udev-default-smack-rules. This might indicate that the images do not have a current version of systemd. A temporary workaround is:

	chsmack -a '*' /dev/kmsg

> + "Failed to open runtime journal: No such file or directory"

This is most likely the Smack label on /var/log. A fix is in the works for the general problem of /var/log. A temporary workaround is

	chsmack -a '*' /var/log

> Apparently something wrong happens with smack settings because, the
> problem does not appear with security=none present at kernel
> commandline.

What shows up in /sys/fs/smackfs/load2?

> Help wanted.
> --
> Łukasz Stelmach
> Samsung R&D Institute Poland
> Samsung Electronics

More information about the Dev mailing list