[Bug 1100877] Re: lxc-start fails after upgrade to raring

[Arne-Christian Blystad]

Hello,

so this bug just happened to me. I was running a local juju environment
(which uses LXC), and then my computer froze. I used SysRQ + REISUB to
reboot it and then my juju-local environment was unable to start. I've
destroyed the environment as well as all containers and rebooted after
that, but now I'm getting the exact same error as #7.

#11:

> ps-ef | grep dnsmasq
nobody    3229  1337  0 00:22 ?        00:00:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
root      5452  4582  0 00:39 pts/3    00:00:00 grep dnsmasq
-------------------------------
sudo netstat -anp | grep :53
tcp        0      0 172.16.182.1:53         0.0.0.0:*               LISTEN      1402/named      
tcp        0      0 192.168.171.1:53        0.0.0.0:*               LISTEN      1402/named      
tcp        0      0 172.17.42.1:53          0.0.0.0:*               LISTEN      1402/named      
tcp        0      0 192.168.1.137:53        0.0.0.0:*               LISTEN      1402/named      
tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN      3229/dnsmasq    
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      1402/named      
tcp        1      0 192.168.1.137:53152     173.194.70.18:80        CLOSE_WAIT  3646/chrome     
tcp        0      0 192.168.1.137:16088     83.227.238.201:53716    ESTABLISHED 4469/spotify    
tcp6       0      0 :::53                   :::*                    LISTEN      1402/named      
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           1136/avahi-daemon: 
udp        0      0 172.16.182.1:53         0.0.0.0:*                           1402/named      
udp        0      0 192.168.171.1:53        0.0.0.0:*                           1402/named      
udp        0      0 172.17.42.1:53          0.0.0.0:*                           1402/named      
udp        0      0 192.168.1.137:53        0.0.0.0:*                           1402/named      
udp        0      0 127.0.1.1:53            0.0.0.0:*                           3229/dnsmasq    
udp        0      0 127.0.0.1:53            0.0.0.0:*                           1402/named      
udp6       0      0 :::5353                 :::*                                1136/avahi-daemon: 
udp6       0      0 :::53                   :::*                                1402/named      
----------------------------------------------
Contents of /etc/dnsmasq.d/*:

cat /etc/dnsmasq.d/*
# Tell any system-wide dnsmasq instance to make sure to bind to interfaces
# instead of listening on 0.0.0.0
# WARNING: changes to this file will get lost if lxc is removed.
bind-interfaces
except-interface=lxcbr0
# Tell any system-wide dnsmasq instance to make sure to bind to interfaces
# instead of listening on 0.0.0.0
# WARNING: changes to this file will get lost if network-manager is removed.
bind-interfaces

/etc/dnsmasq.conf does not exist.

It is worth noting that I have docker installed (which also uses LXC),
but it is not currently active (no images nor containers running), nor
was it at the time of the incident.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1100877

Title:
  lxc-start fails after upgrade to raring

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