Bug 759404

Summary: NetworkManager[2312]: <warn> could not spawn process '/etc/init.d/nscd condrestart': Failed to execute child process "/etc/init.d/nscd" (No such file or directory)
Product: [Fedora] Fedora Reporter: udo <udovdh>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: danw, dcbw, elstaal, ville.skytta
Target Milestone: ---Keywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-02 17:33:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Use /sbin/service to try-restart nscd none

Description udo 2011-12-02 10:22:03 UTC 
Description of problem:
NetworkManager[2312]: <warn> could not spawn process '/etc/init.d/nscd condrestart': Failed to execute child process "/etc/init.d/nscd" (No such file or directory)


Version-Release number of selected component (if applicable):
NetworkManager-0.9.1.90-5.git20110927.fc16.x86_64

How reproducible:
preupgarde upgrade to f16 fro 15

Steps to Reproduce:
1.
2.
3.
  
Actual results:
see below

Expected results:
No complaints. 
NM did work without issue on this box with fedora 15 unlike on the workstation I am typing this on.

Additional info:
NetworkManager[2312]: <warn> could not spawn process '/etc/init.d/nscd condrestart': Failed to execute child process "/etc/init.d/nscd" (No such file or directory)
Comment 1 Ville Skyttä 2011-12-29 21:06:06 UTC 
Created attachment 549998 [details]
Use /sbin/service to try-restart nscd

I suppose this patch would fix it in a way that could be done also in pre-F16 Fedora versions.
Comment 2 Erick 2012-04-29 02:34:00 UTC 
Given that credential caching is not perfect from a security point of view and that hostname caching breaks things like Round-Robin DNS, would it be possible to detect if nscd is disabled by the user/admin and only present a syslog warning by NetworkManager that nscd is disabled?

getting the status of nscd could become a simple call to:

systemctl status nscd.service

if it doesn't have the enabled status log the warning about that in /var/log/messages and continue.
Comment 3 Erick 2012-04-29 02:52:23 UTC 
determining if "systemctl show --property=UnitFileState nscd.service|grep -q enabled" gives a 0 or not, or something like that would perhaps just do the trick.
Comment 4 udo 2012-04-29 08:29:29 UTC 
and mrtg.service keeps on bugging.
I disabled it again.
stopped it
and systemd starts it.

BTW: I updated systemd today, but:

# ps -ef|grep systemd
root         1     0  0 Mar19 ?        00:03:41 /bin/systemd --log-level info --log-target syslog-or-kmsg --system --dump-core --show-status=1 --sysv-console=1 --deserialize 22
root      1297     1  0 Mar19 ?        00:00:26 /lib/systemd/systemd-stdout-syslog-bridge
dbus      2073     1  0 Mar19 ?        00:02:00 /bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation
root     23523     1  0 09:30 ?        00:00:08 /lib/systemd/systemd-logind
root     26033 24699  0 10:27 pts/1    00:00:00 grep --color=auto systemd

even a deamon-reload or reexec doesn't change the dates of the 'Mar19' items.
Comment 5 udo 2012-04-29 08:50:47 UTC 
Comment #4 was intended for another bug on my abundantly filled bugzilla frontpage.
Comment 6 Erick 2012-04-29 16:32:45 UTC 
determining if "systemctl show --property=UnitFileState nscd.service|grep -q enabled" gives a 0 or not, or something like that would perhaps just do the trick.
Comment 7 Dan Winship 2012-05-02 17:33:57 UTC 

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