Bug 1187503 - Systemd do not find initscripts even for service that is removed
Summary: Systemd do not find initscripts even for service that is removed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 21
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-30 09:29 UTC by Knut J BJuland
Modified: 2015-02-25 23:46 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-05 19:17:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Knut J BJuland 2015-01-30 09:29:29 UTC
Description of problem:
It is strange output in dmesg and slow down booting

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


How reproducible:
It show as each start

Steps to Reproduce:
1. Upgrade from Fedora 20 using fedup without any trouble
2.
3.

Actual results:

[30650.523346] systemd-sysv-generator[603]: Could not find init script for sep3_10.service
[30650.523350] systemd-sysv-generator[603]: Could not find init script for ipmievd.service
[30650.523352] systemd-sysv-generator[603]: Could not find init script for yum-cron.service
[30650.523355] systemd-sysv-generator[603]: Could not find init script for smartd.service
[30650.523356] systemd-sysv-generator[603]: Could not find init script for ebtables.service
[30650.523358] systemd-sysv-generator[603]: Could not find init script for sssd.service
[30650.523360] systemd-sysv-generator[603]: Could not find init script for ntpdate.service
[30650.523361] systemd-sysv-generator[603]: Could not find init script for smolt.service
[30650.523363] systemd-sysv-generator[603]: Could not find init script for ksmtuned.service
[30650.523365] systemd-sysv-generator[603]: Could not find init script for firstboot.service
[30650.523367] systemd-sysv-generator[603]: Could not find init script for abrt-ccpp.service
[30650.523368] systemd-sysv-generator[603]: Could not find init script for restorecond.service
[30650.523370] systemd-sysv-generator[603]: Could not find init script for wpa_supplicant.service
[30650.523372] systemd-sysv-generator[603]: Could not find init script for clvmd.service
[30650.523374] systemd-sysv-generator[603]: Could not find init script for speech-dispatcherd.service
[30650.523375] systemd-sysv-generator[603]: Could not find init script for capi.service
[30650.523377] systemd-sysv-generator[603]: Could not find init script for radvd.service
[30650.523379] systemd-sysv-generator[603]: Could not find init script for rpcsvcgssd.service
[30650.523381] systemd-sysv-generator[603]: Could not find init script for irda.service
[30650.523383] systemd-sysv-generator[603]: Could not find init script for named.service
[30650.523385] systemd-sysv-generator[603]: Could not find init script for atd.service
[30650.523387] systemd-sysv-generator[603]: Could not find init script for cgconfig.service
[30650.523389] systemd-sysv-generator[603]: Could not find init script for rpcidmapd.service
[30650.523390] systemd-sysv-generator[603]: Could not find init script for rpcgssd.service
[30650.523392] systemd-sysv-generator[603]: Could not find init script for dkms_autoinstaller.service
[30650.523394] systemd-sysv-generator[603]: Could not find init script for nfslock.service
[30650.523395] systemd-sysv-generator[603]: Could not find init script for nfs.service
[30650.523397] systemd-sysv-generator[603]: Could not find init script for abrtd.service
[30650.523399] systemd-sysv-generator[603]: Could not find init script for bluetooth.service
[30650.523400] systemd-sysv-generator[603]: Could not find init script for isdn.service
[30650.523402] systemd-sysv-generator[603]: Could not find init script for slapd.service
[30650.523404] systemd-sysv-generator[603]: Could not find init script for rsyslog.service
[30650.523405] systemd-sysv-generator[603]: Could not find init script for ypserv.service
[30650.523407] systemd-sysv-generator[603]: Could not find init script for puppet.service
[30650.523409] systemd-sysv-generator[603]: Could not find init script for hsqldb.service
[30650.523411] systemd-sysv-generator[603]: Could not find init script for akmods.service
[30650.523412] systemd-sysv-generator[603]: Could not find init script for mediatomb.service
[30650.523414] systemd-sysv-generator[603]: Could not find init script for gpsd.service
[30650.523416] systemd-sysv-generator[603]: Could not find init script for yppasswdd.service
[30650.523418] systemd-sysv-generator[603]: Could not find init script for sipwitch.service
[30650.523419] systemd-sysv-generator[603]: Could not find init script for ksm.service
[30650.523421] systemd-sysv-generator[603]: Could not find init script for ypxfrd.service
[30650.523423] systemd-sysv-generator[603]: Could not find init script for auditd.service
[30650.523424] systemd-sysv-generator[603]: Could not find init script for httpd.service
[30650.523426] systemd-sysv-generator[603]: Could not find init script for mdmonitor.service
[30650.523428] systemd-sysv-generator[603]: Could not find init script for libvirt-guests.service
[30650.523430] systemd-sysv-generator[603]: Could not find init script for nscd.service
[30650.523431] systemd-sysv-generator[603]: Could not find init script for avahi-daemon.service
[30650.523433] systemd-sysv-generator[603]: Could not find init script for racoon.service
[30650.523435] systemd-sysv-generator[603]: Could not find init script for cgred.service
[30650.523437] systemd-sysv-generator[603]: Could not find init script for udev-post.service
[30650.523438] systemd-sysv-generator[603]: Could not find init script for tcsd.service
[30650.523440] systemd-sysv-generator[603]: Could not find init script for NetworkManager.service
[30650.523442] systemd-sysv-generator[603]: Could not find init script for lldpad.service
[30650.523444] systemd-sysv-generator[603]: Could not find init script for messagebus.service
[30650.523445] systemd-sysv-generator[603]: Could not find init script for ntpd.service
[30650.523447] systemd-sysv-generator[603]: Could not find init script for cups.service
[30650.523449] systemd-sysv-generator[603]: Could not find init script for libvirtd.service
[30650.523459] systemd-sysv-generator[603]: Could not find init script for sep3_10.service
[30650.523471] systemd-sysv-generator[603]: Could not find init script for sep3_10.service
[30650.523482] systemd-sysv-generator[603]: Could not find init script for sep3_10.service
[30650.523494] systemd-sysv-generator[603]: Could not find init script for sep3_10.service
[30650.523505] systemd-sysv-generator[603]: Could not find init script for sep3_10.service
[30650.523517] systemd-sysv-generator[603]: Could not find init script for sep3_10.service


Expected results:


Additional info:

Comment 1 Jóhann B. Guðmundsson 2015-01-30 09:52:40 UTC
Interesting

Is this an endless upgraded machine ( FC1 - F21 or something similar )

check and remove any dangling symlinks to sysv-initscripts in /etc/rc.d/ /etc/init.d/ directories

Try that and reboot and report back

Comment 2 Knut J BJuland 2015-01-30 15:38:38 UTC
Yes. Should I use a fresh install when I upgrade to F22? I found some dangling symlinks in /etc/rc1.d.

Please answar the first question then you can close the bug.

Comment 3 Zbigniew Jędrzejewski-Szmek 2015-01-30 15:52:04 UTC
(In reply to Knut J BJuland from comment #2)
> Yes. Should I use a fresh install when I upgrade to F22? 
No. At least not because of this bug.

> I found some dangling symlinks in /etc/rc1.d.
Should be harmless apart from the warnings.
I almost certainly does not slow down booting in any measurable way.

> Please answar the first question then you can close the bug.

sysv-generator has been cleaned up recently upstream and those patches can be backported to F21. For now the solution of remoing the symlinks should be enough.

Comment 4 Jóhann B. Guðmundsson 2015-01-30 16:17:23 UTC
(In reply to Knut J BJuland from comment #2)
> Yes. Should I use a fresh install when I upgrade to F22? I found some
> dangling symlinks in /etc/rc1.d.

Personal preference. 

I personally just keep /home and do fresh install and flush everything else out since I do lot's of hacking and testing and I can spent just the same amount and or less time to get everything up to speed after upgrades due to the fact I have experiencing weird states ( including Gnome configurations ) after upgrades

Comment 5 Knut J BJuland 2015-01-31 16:22:41 UTC
Resolved. Please close this bug.

Comment 6 Marek Zdunek 2015-02-25 23:46:54 UTC
I can confirm removing broken symlinks fixed that


su -
[root password]
cd /etc/rc.d
symlinks -dr


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