Bug 6866

Summary:	systemd start doesn't create /var/db/nscd as /etc/init.d/nscd was doing
Product:	Mageia	Reporter:	Philippe Weill <Philippe.Weill>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	glibc	CVE:
Status comment:

Description Philippe Weill 2012-07-25 15:04:16 CEST

Description of problem:

 /var/db/nscd not created at start 

Jul 25 14:48:18 localhost systemd[1]: PID file /var/run/nscd/nscd.pid not readable (yet?) after start.
Jul 25 14:48:18 localhost nscd: 28086 ne peut créer /var/db/nscd/passwd; aucune base de données persistante utilisée
Jul 25 14:48:18 localhost nscd: 28086 ne peut créer /var/db/nscd/group; aucune base de données persistante utilisée
Jul 25 14:48:18 localhost nscd: 28086 ne peut créer /var/db/nscd/services; aucune base de données persistante utilisée


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

just read log when nscd start

Manuel Hiebel 2012-07-25 15:56:01 CEST

Assignee: bugsquad => tmb
Source RPM: nscd-2.14.1-8.mga2 => glibc

Comment 1 Dave Hodgins 2013-04-05 00:27:17 CEST

Just ran into this while trying to test the update for sssd.

SYSTEMCTL_SKIP_REDIRECT=1 bash /etc/init.d/nscd start
works.

The two lines in the init script
    [ -d /var/run/nscd ] || mkdir /var/run/nscd
    [ -d /var/db/nscd ] || mkdir /var/db/nscd
need to be handled by tmpfiles.

Adding the file /etc/tmpfiles.d/nscd.conf with the two lines
d /var/run/nscd 0755 root root -
d /var/db/nscd 0755 root root -
should be all that's needed to fix this problem.

CC: (none) => davidwhodgins

Comment 2 Dave Hodgins 2013-04-05 00:31:20 CEST

Also had to remove $NSCD_OPTIONS from the start command in
/lib/systemd/system/nscd.service

Comment 3 Manuel Hiebel 2013-10-22 12:10:26 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 4 Manuel Hiebel 2013-11-23 16:13:53 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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