touch-packages team mailing list archive

[Simon Eisenmann <longsleep@xxxxxxxxx>]

Oct 08 10:00:19 odroid dhclient[587]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0xe7223b64)
Oct 08 10:00:19 odroid sh[578]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 (xid=0xe7223b64)
Oct 08 10:00:34 odroid dhclient[587]: No DHCPOFFERS received.
Oct 08 10:00:34 odroid dhclient[587]: No working leases in persistent database - sleeping.
Oct 08 10:00:34 odroid sh[578]: No DHCPOFFERS received.
Oct 08 10:00:34 odroid sh[578]: No working leases in persistent database - sleeping.
Oct 08 10:00:35 odroid sshd[836]: Received SIGHUP; restarting.
Oct 08 10:00:35 odroid systemd[1]: Reloaded OpenBSD Secure Shell server.
Oct 08 10:00:35 odroid sh[578]: ifup: interface eth0 already configured
Oct 08 10:00:35 odroid sshd[836]: Server listening on 0.0.0.0 port 22.
Oct 08 10:00:35 odroid sshd[836]: Server listening on :: port 22.

Now i killed dhclient for eth0
No dhclient is running now
Now i plug the network cable

Oct 08 10:03:17 odroid kernel: [adjust link] -> eth: full-duplex
Oct 08 10:03:17 odroid kernel: [adjust link] -> eth: phy_speed <> priv_speed)
Oct 08 10:03:17 odroid kernel: [adjust link -> eth: am_adjust_link state change (new_state=true)
Oct 08 10:03:17 odroid kernel: libphy: 0:01 - Link is Up - 1000/Full
Oct 08 10:03:17 odroid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Thats it, still no dhclient is running for eth0. @Oliver : no dhclient
is started if the link becomes ready

cat /etc/network/interfaces.d/eth0 
allow-hotplug eth0
iface eth0 inet dhcp

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1503680

Title:
  dhclient for eth0 does never exit and retries dhcp foerever

Status in Snappy:
  New
Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  When booting snappy without eth0 connected, dhclient runs forever
  trying to retrieve DHCP every 5 minutes.

  dhclient is run with the -1 parameter which is supposed to try only
  once and exit after trying.

         -1     Try  to  get  a  lease  once.   On failure exit with code 2.  In
                DHCPv6 this sets the maximum duration of the initial exchange to
                timeout (from dhclient.conf(5) with a default of sixty seconds).

  Though dhclient keeps running / does not exit.

  If dhclient is changed to exit after failure, it must be insured that
  it will be restarted when the network interface gets a physical link.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1503680/+subscriptions