[SOLVED] Disabled rc-local.service because it was taking so long during the boot up process!

[Saman111]

Hi everyone,

I used the "systemd-analyze blame" command in Fedora 17 to see what service was taking so much time during the boot up process . The worst one was rc-local.service using around 425678 ms! So, I disabled it and now that I reboot the system it just goes to the "emergency mode" and all I get is the "#" prompt. How can I get myself out of this misery?! I feel so stupid to disable this service!!

My system does boot to Windows 7.

Please help me...... Thank you

[PabloTwo]

At the "#" prompt that you see, type these commands and see if that doesn't fix things.

systemctl enable rc-local.service
reboot

I'm assuming you used a the same command to "disable" that service. If not, how did you disable it?

[dd_wizard]

The odd thing about your problem is that rc-local.service in not enabled by default in F17. So I'm wondering how and why you enabled it in the first place. If disabling it kept you from booting, you must be doing some pretty important stuff in /etc/rc.d/rc.local.

dd_wizard

[Saman111]

Originally Posted by PabloTwo

At the "#" prompt that you see, type these commands and see if that doesn't fix things.

systemctl enable rc-local.service
reboot

I'm assuming you used a the same command to "disable" that service. If not, how did you disable it?

"systemctl disable rc-local.service" was used to disable. When I use "systemctl enable rc-local.service", I get an error message. Thank you.

---------- Post added at 11:53 PM ---------- Previous post was at 11:52 PM ----------

Originally Posted by dd_wizard

The odd thing about your problem is that rc-local.service in not enabled by default in F17. So I'm wondering how and why you enabled it in the first place. If disabling it kept you from booting, you must be doing some pretty important stuff in /etc/rc.d/rc.local.

dd_wizard

I had not enabled the service, it was enabled by itself and obviously it is very much needed to boot up. I upgraded my system from Fedora 16 to Fedora 17 using the "preupgrade" command. Thank you.

---------- Post added at 11:58 PM ---------- Previous post was at 11:53 PM ----------

Pablo,

Would you like me to put the error message here?! Thank you.

[PabloTwo]

Originally Posted by Saman111

Pablo,

Would you like me to put the error message here?! Thank you.

Posting the error message would certainly help.

[Saman111]

Originally Posted by PabloTwo

Posting the error message would certainly help.

Thank you. The error message is:

"Warning: unit files do not carry install information. No operation executed.".

Thank you.

[Saman111]

In the emrgency mode, when I got the prompt "#", I typed "startx" and the following error messages in the following order received and then I got the Fedora 17 window and immediately after a black screen. When I press "Alt + F2", I receive a blank filed that I can type commands, some of them work, some do not. For example "Network Manager" pops an error indicating a bug, "Nautilus" brings up a file manager!

[DEPEND] Dependency failed for /home
[DEPEND] Dependency failed for Local File Systems
[DEPEND] Dependency failed for Relabel all filesystems, if necessary
[DEPEND] Dependency failed for Mark the need to relabel after reboot
[DEPEND] Dependency failed for D-Bus System Message Bus Socket
[DEPEND] Dependency failed for Login Service
[DEPEND] Dependency failed for D-Bus System Message Bus
[DEPEND] Dependency failed for Avahi mDNS/DNS-SD Stack
[DEPEND] Dependency failed for Network Manager
[DEPEND] Dependency failed for Bluetooth Manager
[DEPEND] Dependency failed for Avahi mDNS/DNS-SD Stack Activation Socket
[DEPEND] Dependency failed for RPCbind Server Activation Socket
[DEPEND] Dependency failed for RPC bind service
[DEPEND] Dependency failed for NFS Server
[DEPEND] Dependency failed for NFS-v4 ID-name mapping daemon
[DEPEND] Dependency failed for NFS Remote Quota Server
[DEPEND] Dependency failed for NFS Mount Daemon
[DEPEND] Dependency failed for NFS file locking service
[DEPEND] Dependency failed for CUPS Printing Service Sockets
[DEPEND] Dependency failed for Basic System
[DEPEND] Dependency failed for Display Manager
[DEPEND] Dependency failed for Permit User Sessions
[DEPEND] Dependency failed for System Setup Keyboard
[DEPEND] Dependency failed for Multi-User
[DEPEND] Dependency failed for Grafical Interface
Welcome to emergency mode. Use "systemctl default"or ^D to enter default mode.
Give root password for maintenance
(or type Control-D to continue):

At this point, what do I need to do?!

Thank you.

[stevea]

rc-local..service is created to execute the /etc/rc.d/rc.local script *IF* it exists. It doesn't by default.


Even if you had a legacy script file - from like F14 - it still only had "touch /var/lock/subsys/local" by default and that never takes 435 seconds to execute.

No - it's something you added to that file that is biting your boots.

Post the contents of /etc/rc.d/rc.local

[Saman111]

Thank you for your post. Here is the content of the rc.local:
touch /var/lock/subsys/local
mount /dev/sda3/ /NTFS

I modified the rc.local to make sure that there is nothing after the ""touch /var/lock/subsys/local". Still the same behaviour.....it messes up everything, really weird. Thank you.

[stevea]

touch /var/lock/subsys/local
mount /dev/sda3/ /NTFS

Well that's no way to do a mount.
Why did you do that instead of making a /etc/fstab entry ?
Does it actually get mounted ?

What sort of filesystem is on /dev/sda3/ ? The output of
su -c "file -s /dev/sda3"
<passwd>
might help.

[Saman111]

I did it that way because it simply worked from the "#" prompt and then I decided to put it in rc.local. the /dev/sda3 is a NTFS partition where I run Windows 7 from. For now, I have commented out that line and yet the result is the same as before......thank you for your help, much appreciated.

[stevea]

Well now it simply doesn't work !

Anyway - you say "result is the same as before". Please reboot and post the output of
systemd-analyze blame

[Saman111]

Thanks again. The boot time is not the issue anymore. Like I said the system is not fully functional, hence no access to the Internet when fedora 17 is booted, so I use Windows 7 to post in Fedora Forum. therefore I can not copy and paste the result.

Like said in previous messages, the "Network Manager" fails, therefor no access to the Internet when Fedora 17 is booted. Please see below:

[DEPEND] Dependency failed for Network Manager

Having said this, the command "Systemd-analyze blame" does not work and produces error messages shown in my previous posts.

I can boot the system off Fedora 17 installation CD, is there anything we can do there to fix some of the corrupt files?

Thank you for your time, much appreciated.

[Saman111]

Ended up getting my data and then re-installing from scratch...this was a faster soloution. Thanks to those who tried to help.....

Thank you