Bug 11264

Summary: 4_a2: systemd[1]: Failed to start Recreate Volatile Files and Directories
Product: Mageia Reporter: Bit Twister <bittwister2>
Component: RPM PackagesAssignee: Colin Guthrie <mageia>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: bittwister2
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: systemd-207-1.mga4.src.rpm CVE:
Status comment:

Description Bit Twister 2013-09-21 15:52:35 CEST
Description of problem:

Unit systemd-tmpfiles-setup.service entered failed state.

snippet from systemctl status systemd-tmpfiles-setup.service


systemd-tmpfiles[538]: snippet
    [/usr/lib/tmpfiles.d/systemd.conf:29] Unknown group 'systemd-journal'.
    [/usr/lib/tmpfiles.d/systemd.conf:30] Unknown group 'systemd-journal'.



Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. upgrade to systemd 207
2. reboot
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Bit Twister 2013-09-21 16:08:43 CEST
My workaround solution was to create a systemd-journal with a gid less than 500 and reboot.
Jani Välimaa 2013-09-22 11:59:10 CEST

Assignee: bugsquad => mageia

Comment 2 Colin Guthrie 2013-09-22 13:34:33 CEST
Ahh yes, I forget to set this up in the latest packages... thanks!
Comment 3 Colin Guthrie 2013-09-22 19:39:05 CEST
Should be fixed in the next build which creates the group.
Comment 4 Colin Guthrie 2013-09-22 19:39:17 CEST
Closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 5 Bit Twister 2013-10-03 17:14:21 CEST
problem still there on a clean alpha3 install, with all updates applied.

Status: RESOLVED => REOPENED
CC: (none) => junknospam
Resolution: FIXED => (none)

Comment 6 Colin Guthrie 2013-10-05 11:57:18 CEST
Yeah I actually noticed this myself the other day too. It's due to rpm-helper not being installed early enough for the group creation macros.

This has actually changed slightly in next systemd (not in concept, just in implementation - to avoid NSS lookups in journald to prevent potential deadlocks), but in so doing the folder should be owned by this group, so I need to create it at %pre. Will make sure I have the right deps installed when I push that one.
Comment 7 Colin Guthrie 2013-10-08 22:56:41 CEST
OK, fingers crossed I've fixed this properly in the new systemd.... (should repair current installs too) will leave it open for now tho' until you confirm I'm not being stupid still... ;)
Comment 8 Bit Twister 2013-10-09 02:06:48 CEST
systemd-208-1 appears to fix the problem. Install on a VirtuaBox guest with the systemd-journal group did not change it. Install on a host with it removed, reinstalled the group.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED