View previous topic :: View next topic |
Author |
Message |
StoneC0ld n00b
Joined: 27 Jul 2006 Posts: 56
|
Posted: Sat Dec 23, 2006 11:53 am Post subject: net.eth0 related services failing to start @ boot |
|
|
I'm having troubles getting all services requiring net.eth0 as a dependency to boot @ start....
Net.eth0 appears to start ok at the moment, because ssh connections are refused and not timing out, but I get syslog messages saying that each of the services requiring net.eth0 (including sshd) failed to start because net.eth0 was not running.... Datacenter support staff are able to login and start sshd manually, though don't know if they're using the init script or sshd command directly....
Any ideas how I might fix this? It's getting rather annoying having to ticket the datacenter to start sshd every time I reboot, and I'm having to reboot fairly frequently trying to get vmware server to work.....
Thanks.. |
|
Back to top |
|
|
nixnut Bodhisattva
Joined: 09 Apr 2004 Posts: 10974 Location: the dutch mountains
|
Posted: Sat Dec 23, 2006 12:19 pm Post subject: |
|
|
Is net.eth0 in the default runlevel? check with rc-update show _________________ Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
Back to top |
|
|
StoneC0ld n00b
Joined: 27 Jul 2006 Posts: 56
|
Posted: Sat Dec 23, 2006 3:53 pm Post subject: |
|
|
It is..... It does start, because until the datacenter starts sshd, ssh connections are refused.... While it's down, connections time out, so if net.eth0 really fails to start, it would continue to time out.... |
|
Back to top |
|
|
abc0815 n00b
Joined: 07 Jul 2004 Posts: 54
|
Posted: Sat Dec 23, 2006 4:41 pm Post subject: |
|
|
hi,
can you post rc-status show ? Bay "datacenter" you mean that you have a server leased right ?
cheers |
|
Back to top |
|
|
StoneC0ld n00b
Joined: 27 Jul 2006 Posts: 56
|
Posted: Sat Dec 23, 2006 5:19 pm Post subject: |
|
|
monitor ~ # rc-status default
Runlevel: default
netmount [ stopped ]
local [ started ]
net.eth0 [ started ]
syslog-ng [ started ]
vixie-cron [ started ]
sshd [ started ]
xinetd [ started ]
oidentd [ stopped ]
vmware [ broken ]
* You have some broken symbolic links as reported by the broken
* status above. This can be fixed by removing the broken service
* from its runlevel and re-adding it back using rc-update.
vmware I'm not surprised about it, it's being nothing but problems.....
Yes, it's a leased (or something like that) server at a remote datacenter, so I don't have physical access..... |
|
Back to top |
|
|
abc0815 n00b
Joined: 07 Jul 2004 Posts: 54
|
Posted: Sat Dec 23, 2006 7:24 pm Post subject: |
|
|
hm not rc-status default.
Since now the box is reachable rc-status default gets us nowhere
cheers |
|
Back to top |
|
|
erik258 Advocate
Joined: 12 Apr 2005 Posts: 2650 Location: Twin Cities, Minnesota, USA
|
Posted: Sat Dec 23, 2006 9:53 pm Post subject: |
|
|
have you tried running the sshd init script by hand and seeing what happens?
I know the datacenter people manage to start it, but perhaps they just run sshd itself, as you previously suggested. _________________ Configuring a Firewall? Try my iptables configuration
LinuxCommando.com is my blog for linux-related scraps and tidbits. Stop by for a visit! |
|
Back to top |
|
|
StoneC0ld n00b
Joined: 27 Jul 2006 Posts: 56
|
Posted: Sat Dec 23, 2006 11:45 pm Post subject: |
|
|
Code: | monitor ~ # rc-status show
* show is not a valid run level !
* Valid runlevels (obtained from `rc-status --list`):
boot
default
nonetwork
single
monitor ~ # |
I'm guessing you mean this:
Code: | monitor ~ # rc-update show
bootmisc | boot
checkfs | boot
checkroot | boot
clock | boot
coldplug | boot
consolefont | boot
hostname | boot
keymaps | boot
local | default nonetwork
localmount | boot
modules | boot
net.eth0 | default
net.lo | boot
netmount | default
oidentd | default
rmnologin | boot
sshd | default
syslog-ng | default
urandom | boot
vixie-cron | default
vmware | default
xinetd | default
monitor ~ # |
init-scripts work fine when I get to it, though all I can do with sshd is restart..... |
|
Back to top |
|
|
StoneC0ld n00b
Joined: 27 Jul 2006 Posts: 56
|
Posted: Thu Dec 28, 2006 4:18 am Post subject: |
|
|
*bump*
Any solution? |
|
Back to top |
|
|
erik258 Advocate
Joined: 12 Apr 2005 Posts: 2650 Location: Twin Cities, Minnesota, USA
|
Posted: Thu Dec 28, 2006 4:54 am Post subject: |
|
|
if only dmesg would explain it!
you wrote: | syslog-ng | default |
maybe syslog would capture what happens if it were starting in default runlevel...? Then you could get perhaps a helpful error from the logs... _________________ Configuring a Firewall? Try my iptables configuration
LinuxCommando.com is my blog for linux-related scraps and tidbits. Stop by for a visit! |
|
Back to top |
|
|
StoneC0ld n00b
Joined: 27 Jul 2006 Posts: 56
|
Posted: Thu Dec 28, 2006 5:11 am Post subject: |
|
|
no error from net.eth0 in the logs
From what I can remember, the logs had the nic driver output showing a successful initialization, immediately followed by rc-scripts error messages for each rc script that depends on net.eth0....
Not running gentoo at this moment, but looking to go back to it if we can find a solution..... |
|
Back to top |
|
|
erik258 Advocate
Joined: 12 Apr 2005 Posts: 2650 Location: Twin Cities, Minnesota, USA
|
Posted: Thu Dec 28, 2006 5:16 am Post subject: |
|
|
not a great solution, but i think i would just remove the net.eth0 dependancy lines, or maybe before that try letting the lines do the trick and removing the net.eth0 in the default runlevel. _________________ Configuring a Firewall? Try my iptables configuration
LinuxCommando.com is my blog for linux-related scraps and tidbits. Stop by for a visit! |
|
Back to top |
|
|
bandreabis Advocate
Joined: 18 Feb 2005 Posts: 2495 Location: イタリアのロディで
|
Posted: Fri Jan 12, 2007 9:43 pm Post subject: |
|
|
Don't know last changes in unstable but Code: | rc-update del net.eth0 default | solved. _________________ Il numero di post non fa di me un esperto! Anzi! |
|
Back to top |
|
|
|