Bug 3551 - 2_alpha1: /etc/tmpfiles.d/legacy.conf Unknown group 'lock'
Summary: 2_alpha1: /etc/tmpfiles.d/legacy.conf Unknown group 'lock'
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks: 2120
  Show dependency treegraph
 
Reported: 2011-12-01 07:22 CET by Bit Twister
Modified: 2012-01-26 07:44 CET (History)
3 users (show)

See Also:
Source RPM: systemd
CVE:
Status comment:


Attachments

Description Bit Twister 2011-12-01 07:22:11 CET
Description of problem:
systemd-tmpfiles[1146]: [/etc/tmpfiles.d/legacy.conf:22] Unknown group 'lock'.

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


How reproducible: Always


Steps to Reproduce:
1. grep "Unknown group" /var/log/messages


Possible patch found here.
https://qa.mandriva.com/show_bug.cgi?id=63081
Manuel Hiebel 2011-12-01 17:34:34 CET

Keywords: (none) => PATCH
Blocks: (none) => 2120
Source RPM: (none) => systemd

Comment 1 Curtis Hildebrand 2012-01-19 22:44:30 CET
I have the same issue on a clean install from Cauldron post-alpha3:

from /var/log/daemons/errors.log:
Jan 19 11:58:58 localhost systemd-tmpfiles[17159]: [/usr/lib/tmpfiles.d/legacy.conf:22] Unknown group 'lock'.


Line 22 of /usr/lib/tmpfiles.d/legacy.conf :

d /run/lock/lockdev 0775 root lock -

CC: (none) => curtis.h.news

Comment 2 Bit Twister 2012-01-19 23:22:41 CET
(In reply to comment #1)
> I have the same issue on a clean install from Cauldron post-alpha3:

Yep, quick workaround solution is if grep lock /etc/group returns nothing:

/usr/sbin/groupadd -r lock
Comment 3 Dick Gevers 2012-01-21 13:22:30 CET
c#2: getent group lock :)

On up to date cauldron, after booting to kernel-server-3.2.1-1.mga2-1-1.mga2:

# systemctl status systemd-tmpfiles-setup.service 
systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories
  Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static)
  Active: failed since Sat, 21 Jan 2012 12:02:16 +0000; 6min ago
  Main PID: 946 (code=exited, status=1/FAILURE)
  CGroup: name=systemd:/system/systemd-tmpfiles-setup.service

Jan 21 12:02:14 dvg.homepower systemd-tmpfiles[946]: [/usr/lib/tmpfiles.d/legacy.conf:22] Unknown group 'lock'.

# systemctl start systemd-tmpfiles-setup.service 
Job failed. See system logs and 'systemctl status' for details.

# systemctl enable systemd-tmpfiles-setup.service 
Warning: unit files do not carry install information. No operation executed.

I suspect that systemd package scripts should useradd 'lock' if not present.

CC: (none) => dvgevers

Comment 4 Bit Twister 2012-01-21 15:48:59 CET
(In reply to comment #3)
> c#2: getent group lock :)

> 
> I suspect that systemd package scripts should useradd 'lock' if not present.

Not useradd, groupadd -r lock
Comment 5 D Morgan 2012-01-25 02:18:42 CET
please install lockdev rpm
and tell if the pb still exist

CC: (none) => dmorganec

Comment 6 Bit Twister 2012-01-25 08:35:34 CET
(In reply to comment #5)
> please install lockdev rpm
> and tell if the pb still exist

Sorry, bug 4144, bug 4035, bug 4124 has pretty much shutdown all my testing.
All my VirtualBox Mageia guests abort when startx is issued.
Comment 7 D Morgan 2012-01-26 07:44:43 CET
closing  as now lockdev is required by systemd ( and lockdev created the lock group )

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


Note You need to log in before you can comment on or make changes to this bug.