[gentoo-user] DHCP-based eth0 startup failure.

[gentoo-user] DHCP-based eth0 startup failure.

[dnebinger]

Hey, all.  Suffered power outtage yesterday.  Not much of a big deal as the
ups brought the system down on battery...

That's the good news.  The bad news is that, upon system boot, my dhcp-based
eth0 interface no longer comes up and I don't know why...

When the init script is run it reports that it is bringing the card up in 
DHCP and that it is calling dhclient.  At that point, however, the startup
shows the [!!] indicating a failure occurred but I have no real details why.

The only thing in the system log is a message from dhclient: 
receive_packet failed on eth0: Network is down.

dmesg doesn't report any errors related to the network card.

After the system is up I can log in at the console and run dhclient manually
as root and eth0 comes up fine.

The system previously came up fine, so it's got to be something from the last
couple of weeks (the system is up 24x7 so it has been awhile since the last
boot).

The only significant change to the box recently was the new baselayout, but
I think I got everything migrated successfully.

Anyone out there have a suggestion as to how to diagnose and resolve this?

Thanks in advance,

Dave

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP-based eth0 startup failure.

[Ow Mun Heng]

On Sat, 2005-07-09 at 17:22 -0400, dnebinger@joat.com wrote:
> Hey, all.  Suffered power outtage yesterday.  Not much of a big deal as the
> ups brought the system down on battery...
> 
> That's the good news.  The bad news is that, upon system boot, my dhcp-based
> eth0 interface no longer comes up and I don't know why...
> 
> When the init script is run it reports that it is bringing the card up in 
> DHCP and that it is calling dhclient.  At that point, however, the startup
> shows the [!!] indicating a failure occurred but I have no real details why.
> 
> The only thing in the system log is a message from dhclient: 
> receive_packet failed on eth0: Network is down.

I suspect dhclient's pid was still around and you need to manually
kill/zap it before it will restart itself.

I believe also that if you were to restart your PC/server now, all will
be oK

-- 
Ow Mun Heng
Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM
98% Microsoft(tm) Free!! 
Neuromancer 15:00:59 up 4 days, 22:57, 7 users, load average: 1.44,
1.23, 1.62 


-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] DHCP-based eth0 startup failure.

[Dave Nebinger]

> On Sat, 2005-07-09 at 17:22 -0400, dnebinger@joat.com wrote:
> > Hey, all.  Suffered power outtage yesterday.  Not much of a big deal as
> the
> > ups brought the system down on battery...
> >
> > That's the good news.  The bad news is that, upon system boot, my dhcp-
> based
> > eth0 interface no longer comes up and I don't know why...
> >
> > When the init script is run it reports that it is bringing the card up
> in
> > DHCP and that it is calling dhclient.  At that point, however, the
> startup
> > shows the [!!] indicating a failure occurred but I have no real details
> why.
> >
> > The only thing in the system log is a message from dhclient:
> > receive_packet failed on eth0: Network is down.
> 
> I suspect dhclient's pid was still around and you need to manually
> kill/zap it before it will restart itself.
> 
> I believe also that if you were to restart your PC/server now, all will
> be oK

Cycled the system many times with pretty much the same result.  Initially
dmesg was showing that ifconfig was failing due to some SMP issue so I
updated the kernel to 2.6.12.2 and installed and this failure went away.

But now any boot results in the dhcp starting for eth0 but then failing
completely.

When the system comes up I can log in as root and manually start eth0 by
running the dhcp command as /etc/init.d/net.eth0 start should be trying to
do (although I can't tell that it is doing as I suspect).


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP-based eth0 startup failure.

[Alexander Kirillov]

> Cycled the system many times with pretty much the same result.  Initially
> dmesg was showing that ifconfig was failing due to some SMP issue so I
> updated the kernel to 2.6.12.2 and installed and this failure went away.
> 
> But now any boot results in the dhcp starting for eth0 but then failing
> completely.
> 
> When the system comes up I can log in as root and manually start eth0 by
> running the dhcp command as /etc/init.d/net.eth0 start should be trying to
> do (although I can't tell that it is doing as I suspect).

Don't know if the problem you're having is related
to the one I had with 3rd party usb adsl modem init script
but try to add related modules to /etc/modules.autoload.d/kernel-2.6
Sasha

-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] DHCP-based eth0 startup failure.

[Dave Nebinger]

> Don't know if the problem you're having is related
> to the one I had with 3rd party usb adsl modem init script
> but try to add related modules to /etc/modules.autoload.d/kernel-2.6

Nope.  I consider the networking support critical enough to warrant being
compiled into the kernel rather than loaded as a module.  Module loading,
therefore, is not an issue.


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] DHCP-based eth0 startup failure.

[Daniel da Veiga]

What's the dhcp server? A router or a computer? I had the same
problem, my router refused to give me the dhcp response upon reboot,
rebooting the router itself solved the problem, its like the router
refuses to give dhcp right after the lease of the client.

Maybe check the configuration of the dhcp server...

On 7/12/05, Dave Nebinger <dnebinger@joat.com> wrote:
> > Don't know if the problem you're having is related
> > to the one I had with 3rd party usb adsl modem init script
> > but try to add related modules to /etc/modules.autoload.d/kernel-2.6
> 
> Nope.  I consider the networking support critical enough to warrant being
> compiled into the kernel rather than loaded as a module.  Module loading,
> therefore, is not an issue.
> 
> 
> --
> gentoo-user@gentoo.org mailing list
> 
> 


-- 
Daniel da Veiga
Computer Operator - RS - Brazil

-- 
gentoo-user@gentoo.org mailing list

RE: [gentoo-user] DHCP-based eth0 startup failure.

[Dave Nebinger]

> What's the dhcp server? A router or a computer? I had the same
> problem, my router refused to give me the dhcp response upon reboot,
> rebooting the router itself solved the problem, its like the router
> refuses to give dhcp right after the lease of the client.
> 
> Maybe check the configuration of the dhcp server...

It's a gentoo box using iptables to act as a router.  It talks to an adsl
modem connected to ISP which, for the last year now, has not offered similar
problems.

The configuration would appear to be correct in that manually starting dhcp
client results in the network card coming up.

The issue, from my perspective, is that some failure is occurring during
net.eth0 startup that, because of the various script files involved, hides
the component that is actually failing.  There's no messages in the syslog
nor does dmesg show anything of value.

So the recently redone base layout update, where net.eth0 was supposed to
become a symlink (etc) somewhere introduced a point of failure.  And for all
of the pieces involved one of them is crapping out but the failure reason is
not getting rolled up to a point where it is made obvious.

I'm afraid I'm going to have to dig into /etc/init.d/net.eth0 and try to
find how it's actually trying to bring the card up.  Gotta love bash
debugging!



-- 
gentoo-user@gentoo.org mailing list