Hi Daniel On 10/11/2010 04:37 AM, daniel@xxxxxxxxxx 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 -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
