PDA

View Full Version : [SOLVED] Several services don't start at boot



trx64
January 29th, 2010, 07:58 PM
I'm having some strange problems in my system (Ubuntu 9.10 32 bits). Several services (Cups, MySQL, VirtualBox kernel driver, etc) aren't starting during boot time. It's possible start them manually (e.g. /etc/init.d/cups start). The other problem is that my virtual terminals (ctrl + alt + f[1-6]) aren't starting with the system too. Any idea?

blwegrzyn
January 31st, 2010, 07:44 PM
i have exact same problem, it just started, not sure when,
almost all of the services dont start and i must start them manually, is there a way to do some interactive boot to see what is happening?

thx

chronniff
February 3rd, 2010, 08:25 AM
I too am having issues with services I installed, notably at the moment nfs-kernel-server and the vmware modules for my vmware workstation, not starting up. I have all their runlevels set up correctly, or at least what has been correct on linux for about 20 years....although I'm guessing this new upstart service is the cause of all this frustration....I'm running ubuntu 9.10 btw

chronniff
February 3rd, 2010, 08:46 AM
Just to let you guys know, I figured out what was going on with my services...don't know if this will help you, but I had forgotten that I changed a setting in /etc/init.d/rc that enabled concurrent booting, which must have messed up the order of my services starting, because after changing the setting back, all my problems were fixed

trx64
February 3rd, 2010, 01:36 PM
That didn't work here. I've started a bug report in Launchpad (https://bugs.launchpad.net/ureadahead/+bug/515788).

blwegrzyn
February 3rd, 2010, 04:17 PM
same here ,
i tried to modify it to startpar and i run insserv same problem

blwegrzyn
February 17th, 2010, 04:28 AM
this helped:
https://answers.launchpad.net/upstart/+question/98037

trx64
February 17th, 2010, 08:29 PM
Problem solved. I've edited the file rc-sysinit.conf:

$ sudo gedit /etc/init/rc-sysinit.conf


And changed the line:


start on filesystem and net-device-up IFACE=lo

to:

start on filesystem #and net-device-up IFACE=lo


That solved the tty problem and the problems with the services.

sjorsvb
February 18th, 2010, 10:26 AM
This also worked for me, thank you very much!
I am a little curious about the meaning of it though.

trx64
February 18th, 2010, 12:19 PM
This also worked for me, thank you very much!
I am a little curious about the meaning of it though.

That line stated that services should only be started after the loopback network device is ready. The problem is that, in Karmic, the network device initializes later and the services that depend on its start can not be initialized correctly.

Commenting the line, the services will no longer wait for the loopback device, then they will start up normally.

alecz20
March 22nd, 2010, 10:15 PM
Problem solved. I've edited the file rc-sysinit.conf:

$ sudo gedit /etc/init/rc-sysinit.conf


...

<code>
-bash: cd: /etc/init: No such file or directory
</code>

Apparently there is no directory called init in /etc

Also, in /etc/init.d there is no rc-sysinit.conf file..

So.. what's happening?

RazTaz
June 23rd, 2010, 08:37 PM
Problem solved. I've edited the file rc-sysinit.conf:

$ sudo gedit /etc/init/rc-sysinit.conf


And changed the line:


start on filesystem and net-device-up IFACE=lo

to:

start on filesystem #and net-device-up IFACE=lo


That solved the tty problem and the problems with the services.

I ran into the same problem after upgrading from Karmic to Lucid. Thank you for the solution. It worked for me.