View previous topic :: View next topic |
Author |
Message |
sharkie n00b
Joined: 26 Apr 2005 Posts: 19
|
Posted: Fri May 13, 2005 6:25 pm Post subject: rc-scripts broken |
|
|
Hey,
I recently did an emerge --update world. I reviewed all the new configs so I have now 0 pending config changes. Everything went well, except the rc-scripts ran at boot. I used to start several services at bootime, but now only a few succeed. For the rest, when i boot, i get this:
Code: |
May 13 01:14:03 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:03 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:04 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:04 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:04 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:04 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:04 aicon rc-scripts: ERROR: Problem starting needed services.
May 13 01:14:04 aicon rc-scripts: "sshd" was not started.
May 13 01:14:04 aicon rc-scripts: ERROR: Problem starting needed services.
May 13 01:14:04 aicon rc-scripts: "apache2" was not started.
May 13 01:14:04 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:05 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:05 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:05 aicon rc-scripts: ERROR: Problem starting needed services.
May 13 01:14:05 aicon rc-scripts: "proftpd" was not started.
May 13 01:14:05 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:05 aicon rc-scripts: /sbin/rc: cannot start until the runlevel boot has completed
May 13 01:14:05 aicon init: Entering runlevel: 3
|
After boot sequence is completed, my services listed above are not started. But if i manually try starting them, i get the message that they are already running. I have to manually zap each of them and then start :
Code: |
/etc/init.d/apache2 zap
* Manually resetting apache2 to stopped state.
/etc/init.d/apache2 start
* Starting apache2 ...
|
Any idea how can i correct this ? Or at least what files should i check ?
Thanks in advance! |
|
Back to top |
|
|
Master Shake l33t
Joined: 10 Apr 2005 Posts: 755 Location: Wilmington, Delaware
|
Posted: Fri May 13, 2005 9:36 pm Post subject: |
|
|
yeah instead of starting them at boot why don't you start them at default?
Code: | rc-update add *** default |
_________________ System Specs:
64-bit gentoo linux
Q6600 @ 3.2Ghz
P35 Chipset
4 Gigs 800mhz 4-4-4-12
Nvidia GeForce 8800 GTX @ 630mhz |
|
Back to top |
|
|
sharkie n00b
Joined: 26 Apr 2005 Posts: 19
|
Posted: Sat May 14, 2005 4:03 pm Post subject: |
|
|
yeah, that worked. thanks a lot!
i now have 3 services that fail to start but no name is shown so i have no idea which of them failed. does rc have a verbose mode to show info about everything it starts?
thanks much. |
|
Back to top |
|
|
|