| View previous topic :: View next topic |
| Author |
Message |
the_bard
n00b
Joined: 03 Dec 2002
Posts: 60
Location: Albany, NY
|
 Posted: Wed Oct 01, 2003 3:23 pm Post subject: Oddity: net.eth0 is brought down on boot first, then back up |
 |
|
For the past few days, I've noticed that "/etc/init.d/net.eth0 stop" is being called on boot, before it's brought up. My system:
- Does a lot of stuff I'm not gonna get into...
- Remounts the root fs read/write
- Sets the hostname
- Calculates module dependencies
- Autoloads modules
- Checks the filesystems
- Mounts local filesystems
- Activates all the swap
- Caches all the service dependencies
- Brings eth0 down.
It then continues on, to bring eth0 back up.
I've got a connection to the 'net... everything's working as far as I can tell (with the exception of dnsdomainname... I still don't have that configured correctly, I believe). It's just a pet peeve of mine. It's my system, and I ought to know what's going on with it, and why. And right now, I don't  .
Is there any way to trace my way through the boot (at boot time or other) to figure out why "/etc/init.d/net.eth0 stop" is being called? |
|
| Back to top |
|
 |
the_bard
n00b
Joined: 03 Dec 2002
Posts: 60
Location: Albany, NY
|
| Posted: Sat Oct 04, 2003 1:00 am Post subject: |
|
|
Seein' as this has only been viewed 12 times, I'm guessing that it's not all that interesting  .
What I'm after at this point is whether anybody else has this... and if somebody can explain to me why it's happening. That is what's bothering me... why it's happening, not so much the event itself. |
|
| Back to top |
|
|
andrew_j_w
Guru
Joined: 28 Jun 2003
Posts: 534
Location: York, UK
|
| Posted: Sat Oct 04, 2003 10:53 am Post subject: |
|
|
I have no idea why that's happening, but have you tried doing a
rc-update del net.eth0
rc-update add net.eth0 boot
to see if that clears the problems up?
HTH,
Andrew |
|
| Back to top |
|
|
the_bard
n00b
Joined: 03 Dec 2002
Posts: 60
Location: Albany, NY
|
| Posted: Sat Oct 04, 2003 12:26 pm Post subject: |
|
|
Yep. Before I noticed this, I had net.eth0 added to the default runlevel. If I change it to the boot level, via
| Code: | rc-update del net.eth0
rc-update add net.eth0 boot |
then I do not get a "Bringing eth0 up now" notification on boot. It is brought up (ifconfig shows an IP address, I can access the web, etc.), but it's just not shown.
From what it looks like to me, if I've got it set in the default runlevel, somewhere there must be a script that requires it not be up (why else would it shut eth0 down?). Before that happens though, either something's bringing it up (and not outputting 'Bringing eth0 up'), or changing whatever flags the dependency checker's using to determine its status.
And I have no clue why the net.eth0 script isn't outputting it status when it's added to the boot runlevel. I wonder if my scripts aren't corrupted somehow... there any place I can get a copy, and compare 'em? |
|
| Back to top |
|
|
andrew_j_w
Guru
Joined: 28 Jun 2003
Posts: 534
Location: York, UK
|
|
| Back to top |
|
|
Hansoj
n00b
Joined: 18 Sep 2003
Posts: 21
|
| Posted: Thu Nov 06, 2003 1:40 pm Post subject: |
|
|
I almost have the same problem. But if I "rc-update add net.eth0 default"
I get an error on startup saying that "net.eth0 has already been started".
If I remove it says "Bringing eth0 down" but it still workes...
However I got one more problem.
I can't get the eth1 to work. If I add "net.eth1 default" I get the same error
as if i add "net.eth0". "Warning net.eth0 has already been started"
To bring eth1 up manuelly works fine.
What to do? |
|
| Back to top |
|
|
Mravouk
n00b
Joined: 07 Nov 2003
Posts: 3
Location: Prague, Czech Republic
|
| Posted: Fri Nov 07, 2003 11:29 am Post subject: |
|
|
| Quote: | | then I do not get a "Bringing eth0 up now" notification on boot. It is brought up (ifconfig shows an IP address, I can access the web, etc.), but it's just not shown. |
I have exactly the same problem (or not problem). I had "eth0 down" at startup, I removed net.eth0 from default level and put it to boot. After that I don't see "bringing up" at startup anymore, but eth0 is configured correctly.
Does anybody find out the reason for this wierd behaviour? |
|
| Back to top |
|
|
|
Networking & Security
