← Back to team overview

touch-packages team mailing list archive

[Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE

 

I suggest that README.Debian (or Ubuntu) mention the workarounds
regarding bind9 and ipv6.

It might save some time in debugging lxc problems.

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
     Loaded: loaded (/etc/init.d/networking)
    Drop-In: /run/systemd/generator/networking.service.d
             └─50-insserv.conf-$network.conf
          /lib/systemd/system/networking.service.d
             └─systemd.conf
     Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 459 ExecStart=/etc/init.d/networking start (code=killed, signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
     Loaded: loaded (/etc/init.d/networking)
    Drop-In: /run/systemd/generator/networking.service.d
             └─50-insserv.conf-$network.conf
          /lib/systemd/system/networking.service.d
             └─systemd.conf
     Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, status=0/SUCCESS)
    Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS)
     CGroup: /user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
             ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0
             ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
             ├─1109 lockfile-touch /var/lock/ntpdate-ifup
             ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
             ├─1128 lockfile-create /var/lock/ntpdate-ifup
             └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

  root@vivid:/# ip a
  ...
  22: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
  ...
      inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 08:53:02 2015
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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


References