Beim Produkttest für DHCP in der Schulungsumgebung trat das Phänomenauf, daß das beim händischen Testen plötzlich mehrere dhclient's pro Interface aktiv wurden: 1. /etc/init.d/gdm stop 2. /etc/init.d/ifplugd 3. killall dhclient3 4. : > /var/lib/dhcp3/dhclient.leases 5. dhclient3 eth1 root@c27:~# : > /var/lib/dhcp3/dhclient.leases ; dhclient3 eth1 Internet Systems Consortium DHCP Client V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth1/00:11:22:33:44:82 Sending on LPF/eth1/00:11:22:33:44:82 Sending on Socket/fallback DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4 DHCPOFFER from 10.200.17.26 DHCPREQUEST on eth1 to 255.255.255.255 port 67 DHCPACK from 10.200.17.26 [ 5721.301055] skge eth1: disabling interface Internet Systems Consortium DHCP Client V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ [ 5721.389433] skge eth1: enabling interface [ 5721.392972] ADDRCONF(NETDEV_UP): eth1: link is not ready Listening on LPF/eth1/00:11:22:33:44:82 Sending on LPF/eth1/00:11:22:33:44:82 Sending on Socket/fallback DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 [ 5723.078479] skge eth1: Link is up at 100 Mbps, full duplex, flow control both [ 5723.078892] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13 DHCPOFFER from 10.200.17.26 DHCPREQUEST on eth1 to 255.255.255.255 port 67 DHCPACK from 10.200.17.26 bound to 10.200.17.136 -- renewal in 19688 seconds. /etc/network/if-up.d/05_auth: line 53: /etc/NetworkManager/dispatcher.d/01ifupdown: No such file or directory bound to 10.200.17.136 -- renewal in 16 seconds. root@c27:~# [ 5733.368091] eth1: no IPv6 routers present root@c27:~# pidof dhclient3 11242 11049 root@c27:~# ps `pidof dhclient3` PID TTY STAT TIME COMMAND 11049 ? Ss 0:00 dhclient3 -pf /var/run/dhclient.eth1.pid -lf /var/lib/dhcp3/dhclient.eth1.leases eth1 11242 ? Ss 0:00 dhclient3 eth1
Welche Systemrolle hatte das System? War das System aktualisiert worden? Gab es negative Auswirkungen durch Prozesse? Das Problem bzgl. mehrerer dhclients ist bereits bekannt. Bug #16652
Systemrolle: Managed Client Installation von CD mit Version UCS_2.3 ~2009-12-09 Auswirkungen: nein, habe ich nicht darauf geachtet, weil das gerade nicht mein Thema war. Auffällig war nur die sehr unterschiedliche Lease-Zeit der beiden Instanzen: bound to 10.200.17.136 -- renewal in 19688 seconds. bound to 10.200.17.136 -- renewal in 16 seconds.
*** This bug has been marked as a duplicate of bug 16652 ***