touch-packages team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

Comparing to output of a vivid VM, the sysctl status differs in one
important detail. The initial dhclient again is gone but under the
system-ifup.slice there is the new pid...

● ifup@eth0.service - ifup for eth0
   Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: enabled)
   Active: active (exited) since Tue 2015-06-30 15:08:44 CEST; 20s ago
  Process: 403 ExecStart=/bin/sh -ec ifup --allow=hotplug %I; ifup --allow=auto %I;      if ifquery %I >/dev/null; then ifquery --state %I >/dev/null; fi (code=exited, status=0/SUCCESS)
 Main PID: 403 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/system-ifup.slice/ifup@eth0.service
           └─736 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/...

Jun 30 15:08:45 lam-vivid6401 sh[403]: Sending on   Socket/fallback
Jun 30 15:08:45 lam-vivid6401 sh[403]: DHCPDISCOVER on eth0 to 255.255.255....7)
Jun 30 15:08:46 lam-vivid6401 dhclient[430]: DHCPREQUEST of 192.168.2.159 on...)
Jun 30 15:08:46 lam-vivid6401 dhclient[430]: DHCPOFFER of 192.168.2.159 from...1
Jun 30 15:08:46 lam-vivid6401 sh[403]: DHCPREQUEST of 192.168.2.159 on eth0...7)
Jun 30 15:08:46 lam-vivid6401 sh[403]: DHCPOFFER of 192.168.2.159 from 192.....1
Jun 30 15:08:47 lam-vivid6401 dhclient[430]: DHCPACK of 192.168.2.159 from 1...1
Jun 30 15:08:47 lam-vivid6401 sh[403]: DHCPACK of 192.168.2.159 from 192.168.2.1
Jun 30 15:08:47 lam-vivid6401 dhclient[430]: bound to 192.168.2.159 -- renew....
Jun 30 15:08:47 lam-vivid6401 sh[403]: bound to 192.168.2.159 -- renewal in...s.
Hint: Some lines were ellipsized, use -l to show in full.
ubuntu@lam-vivid6401:~$ cat /run/dhclient.eth0.pid 
736

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

Title:
  dhclient does not remain running on boot

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Not sure whether this is a systemd or ifupdown issue. I just happened to notice today for a Wily VM (set up from server iso) that I failed to get a DNS resolution for a VM I started earlier the day. DNS updates in my case are related to DHCP updates. And on the DHCP/DNS server I noticed that the IP address had been removed at some point. Looking at the VM, I find no dhclient being started. When I manually run ifdown and ifup on the interface this does happen. But not whenever I boot.
  Curious about this I also checked a Vivid VM (also server install) and this looks the same. However for Vivid this seems fixed in the latest versions.

  Network config in /etc/network/interfaces:
  auto eth0
  iface eth0 inet dhcp

  Expected result:
  dhclient running for eth0

  Actual result after boot:
  No dhclient process is running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1466790/+subscriptions