touch-packages team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

Seems on bare-metal servers I have, I do not see this. The VM as well as
well as bare-metal server of the team mate I asked are booting rather
quickly. That as side note. I upgraded the VM today and now run on
systemd/udev 221-1ubuntu2.

Still the same. One observation that looks odd: There is a pid file in
/run: /run/dhclient.eth0.pid which contains PID 684. However in the
journal as well as in "systemctl status ifup@eth0" there is a different
PID for dhclient. The pid file is re-created each boot (/run is tmpfs
and I also deliberately deleted it before reboot). From the number it
seems the file is from a later start of dhclient. But that seems to have
left no tracks in the log at all.

● ifup@eth0.service - ifup for eth0
   Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: enabled)
   Active: active (exited) since Di 2015-06-30 10:14:31 CEST; 10min ago
  Process: 729 ExecStartPost=/sbin/ifquery --state %I (code=exited, status=0/SUCCESS)
  Process: 450 ExecStartPost=/sbin/ifup --allow=auto %I (code=exited, status=0/SUCCESS)
  Process: 448 ExecStart=/sbin/ifup --allow=hotplug %I (code=exited, status=0/SUCCESS)
 Main PID: 448 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/system-ifup.slice/ifup@eth0.service

Jun 30 10:14:31 lam-wily6401 dhclient[477]: DHCPREQUEST of 192.168.2.189 on ...)
Jun 30 10:14:31 lam-wily6401 dhclient[477]: DHCPOFFER of 192.168.2.189 from ...1
Jun 30 10:14:31 lam-wily6401 ifup[450]: DHCPREQUEST of 192.168.2.189 on eth0...)
Jun 30 10:14:31 lam-wily6401 ifup[450]: DHCPOFFER of 192.168.2.189 from 192....1
Jun 30 10:14:31 lam-wily6401 dhclient[477]: DHCPACK of 192.168.2.189 from 19...1
Jun 30 10:14:31 lam-wily6401 ifup[450]: DHCPACK of 192.168.2.189 from 192.16...1
Jun 30 10:14:31 lam-wily6401 dhclient[477]: bound to 192.168.2.189 -- renewa....
Jun 30 10:14:31 lam-wily6401 ifup[450]: bound to 192.168.2.189 -- renewal in....
Jun 30 10:14:31 lam-wily6401 ifquery[729]: eth0=eth0
Jun 30 10:14:31 lam-wily6401 systemd[1]: Started ifup for eth0.

** Attachment added: "Output of journalctl after addind VERBOSE=yes"
   https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1466790/+attachment/4422243/+files/journal.txt

-- 
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:
  Incomplete

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