From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: "daniel-2N1FInP7wozQT0dZR+AlfA@public.gmane.org"
<daniel-2N1FInP7wozQT0dZR+AlfA@public.gmane.org>
Cc: "<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>"
<initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Dracut NFS root DHCP timeouts
Date: Mon, 11 Oct 2010 14:25:21 +0200 [thread overview]
Message-ID: <4CB30231.80803@bfh.ch> (raw)
In-Reply-To: <20101011133718.205549hmcnjzr3a8-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
Hi Daniel
On 10/11/2010 04:37 AM, daniel-2N1FInP7wozQT0dZR+AlfA@public.gmane.org wrote:
> While the server boots and the interfaces initializers I see:
> Sending DHCP requets .....timed out
>
> The following happens 2-3 times
>
> The DHCP server logs report..
>
> Attempt 1:
> dhcpd: DHCPREQUEST for 201.0.0.0 (180.0.0.0) from 00:19:b9:eb:3d:4e
> via 10.197.220.241: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 201.0.0.0 (180.0.0.0) from 00:19:b9:eb:3d:50
> via eth1: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 201.0.0.0 (180.0.0.0) from 00:19:b9:eb:3d:4e
> via 10.197.220.241: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 201.0.0.0 (180.0.0.0) from 00:19:b9:eb:3d:50
> via eth1: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 201.0.0.0 (180.0.0.0) from 00:19:b9:eb:3d:4e
> via 10.197.220.241: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 201.0.0.0 (180.0.0.0) from 00:19:b9:eb:3d:50
> via eth1: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 201.0.0.0 (180.0.0.0) from 00:19:b9:eb:3d:4e
> via 10.197.220.241: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 201.0.0.0 (180.0.0.0) from 00:19:b9:eb:3d:50
> via eth1: ignored (not authoritative).
>
> Attempts 2:
> dhcpd: DHCPREQUEST for 255.255.255.255 (180.0.0.0) from
> 00:19:b9:eb:3d:4e via 10.197.220.241: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 255.255.255.255 (180.0.0.0) from
> 00:19:b9:eb:3d:50 via eth1: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 255.255.255.255 (180.0.0.0) from
> 00:19:b9:eb:3d:4e via 10.197.220.241: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 255.255.255.255 (180.0.0.0) from
> 00:19:b9:eb:3d:50 via eth1: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 255.255.255.255 (180.0.0.0) from
> 00:19:b9:eb:3d:4e via 10.197.220.241: ignored (not authoritative).
> dhcpd: DHCPREQUEST for 255.255.255.255 (180.0.0.0) from
> 00:19:b9:eb:3d:50 via eth1: ignored (not authoritative).
>
> Just before the pivot DHCP runs again and all works. The DHCP server reports:
>
> dhcpd: DHCPDISCOVER from 00:19:b9:eb:3d:50 via eth1
> dhcpd: DHCPOFFER on 10.197.170.30 to 00:19:b9:eb:3d:50 via eth1
> dhcpd: Dynamic and static leases present for 10.197.170.30.
> dhcpd: Remove host declaration san.n15-pizza1-3 or remove 10.197.170.30
> dhcpd: from the dynamic address pool for 10.197.170.0/24
> dhcpd: DHCPREQUEST for 10.197.170.30 (10.197.170.42) from
> 00:19:b9:eb:3d:50 via eth1
> dhcpd: DHCPACK on 10.197.170.30 to 00:19:b9:eb:3d:50 via eth1
>
> Gentoo boots and all seems to be ok except for a weird issue where the
> resolv.conf is not updated correctly.
Ummm... Just so that I understand this. The logs for Attempt 1 and 2 are
after the dracut pivot from the dhcp requests inside the nfs-rooted
system and the logs and the last one above is from dhcp inside dracut.
correct?
> Any ideas on what the causing the initial DHCP timeouts? It makes the
> boot process take a lot longer!
BTW: If you are using a recent pxelinux, why don't you try IPAPPEND=3
and remove all ip-options from dracut? (See
http://syslinux.zytor.com/wiki/index.php/SYSLINUX#IPAPPEND_flag_val_.5BPXELINUX_only.5D).
This should cause dracut not to issue any dhcp requests at all. Sorry I
haven't thought about this earlier.
Regards,
Philippe
next prev parent reply other threads:[~2010-10-11 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 2:37 Dracut NFS root DHCP timeouts daniel-2N1FInP7wozQT0dZR+AlfA
[not found] ` <20101011133718.205549hmcnjzr3a8-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-11 12:25 ` Seewer Philippe [this message]
[not found] ` <4CB30231.80803-omB+W0Dpw2o@public.gmane.org>
2010-10-11 22:44 ` daniel-2N1FInP7wozQT0dZR+AlfA
[not found] ` <20101012094412.14125sp7tc6dj7r4-2RFepEojUI3Y3UUic/vCjNBPR1lH4CV8@public.gmane.org>
2010-10-11 22:59 ` daniel-2N1FInP7wozQT0dZR+AlfA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CB30231.80803@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=daniel-2N1FInP7wozQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.