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

2013-01-18 Thread Martin Albisetti
beuno@beuno-laptop:~$ sudo cat /var/log/upstart/lxc-net.log

dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign
requested address

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2013-01-17 Thread Martin Albisetti
Public bug reported:

After the upgrade to raring, my lxc containers no longer start:

beuno@beuno-desktop:~/canonical/ubuntuone$ sudo lxc-start -n u1-servers-precise
lxc-start: failed to attach 'vethYpmRvz' to the bridge 'lxcbr0' : No such device
lxc-start: failed to create netdev
lxc-start: failed to create the network
lxc-start: failed to spawn 'u1-servers-precise'
lxc-start: No such file or directory - failed to remove cgroup 
'/sys/fs/cgroup/cpuset//lxc/u1-servers-precise'

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: lxc 0.8.0~rc1-4ubuntu48
ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
ApportVersion: 2.8-0ubuntu1
Architecture: amd64
Date: Thu Jan 17 14:32:17 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-07-31 (169 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: Upgraded to raring on 2012-10-03 (105 days ago)
lxcsyslog:

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apparmor apport-bug raring running-unity

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2013-01-17 Thread Martin Albisetti
** Description changed:

  After the upgrade to raring, my lxc containers no longer start:
  
  beuno@beuno-desktop:~/canonical/ubuntuone$ sudo lxc-start -n 
u1-servers-precise
  lxc-start: failed to attach 'vethYpmRvz' to the bridge 'lxcbr0' : No such 
device
  lxc-start: failed to create netdev
  lxc-start: failed to create the network
  lxc-start: failed to spawn 'u1-servers-precise'
  lxc-start: No such file or directory - failed to remove cgroup 
'/sys/fs/cgroup/cpuset//lxc/u1-servers-precise'
+ 
+ Upon inspection, the folder /sys/fs/cgroup/cpuset/lxc/ does not exist.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: lxc 0.8.0~rc1-4ubuntu48
  ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 17 14:32:17 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-31 (169 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: Upgraded to raring on 2012-10-03 (105 days ago)
  lxcsyslog:

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2013-01-17 Thread Martin Albisetti
beuno@beuno-desktop:~$ brctl show
bridge name bridge id   STP enabled interfaces
beuno@beuno-desktop:~$ ls -l /var/log/upstart/lxc*
-rw-r- 1 root root 92 Jan 16 23:41 /var/log/upstart/lxc-net.log
beuno@beuno-desktop:~$ cat /etc/default/lxc
# MIRROR to be used by ubuntu template at container creation:
# Leaving it undefined is fine
#MIRROR=http://archive.ubuntu.com/ubuntu;
# or 
#MIRROR=http://host-ip-addr:3142/archive.ubuntu.com/ubuntu

# LXC_AUTO - whether or not to start containers symlinked under
# /etc/lxc/auto
LXC_AUTO=true

# Leave USE_LXC_BRIDGE as true if you want to use lxcbr0 for your
# containers.  Set to false if you'll use virbr0 or another existing
# bridge, or mavlan to your host's NIC.
USE_LXC_BRIDGE=true

# If you change the LXC_BRIDGE to something other than lxcbr0, then
# you will also need to update your /etc/lxc/lxc.conf as well as the
# configuration (/var/lib/lxc/container/config) for any containers
# already created using the default config to reflect the new bridge
# name.
# If you have the dnsmasq daemon installed, you'll also have to update
# /etc/dnsmasq.d/lxc and restart the system wide dnsmasq daemon.
LXC_BRIDGE=lxcbr0
LXC_ADDR=10.0.3.1
LXC_NETMASK=255.255.255.0
LXC_NETWORK=10.0.3.0/24
LXC_DHCP_RANGE=10.0.3.2,10.0.3.254
LXC_DHCP_MAX=253

LXC_SHUTDOWN_TIMEOUT=120
beuno@beuno-desktop:~$ cat /etc/init/lxc-net.conf
description lxc network
author Serge Hallyn serge.hal...@canonical.com

start on starting lxc
stop on stopped lxc

env USE_LXC_BRIDGE=false
env LXC_BRIDGE=lxcbr0
env LXC_ADDR=10.0.3.1
env LXC_NETMASK=255.255.255.0
env LXC_NETWORK=10.0.3.0/24
env LXC_DHCP_RANGE=10.0.3.2,10.0.3.254
env LXC_DHCP_MAX=253
env varrun=/var/run/lxc

pre-start script
[ -f /etc/default/lxc ]  . /etc/default/lxc

[ x$USE_LXC_BRIDGE = xtrue ] || { stop; exit 0; }

cleanup() {
# dnsmasq failed to start, clean up the bridge
iptables -t nat -D POSTROUTING -s ${LXC_NETWORK} ! -d 
${LXC_NETWORK} -j MASQUERADE || true
ifconfig ${LXC_BRIDGE} down || true
brctl delbr ${LXC_BRIDGE} || true
}

if [ -d /sys/class/net/${LXC_BRIDGE} ]; then
if [ ! -f ${varrun}/network_up ]; then
# bridge exists, but we didn't start it
stop;
fi
exit 0;
fi

# set up the lxc network
echo 1  /proc/sys/net/ipv4/ip_forward
mkdir -p ${varrun}
brctl addbr ${LXC_BRIDGE}
ifconfig ${LXC_BRIDGE} ${LXC_ADDR} netmask ${LXC_NETMASK} up
iptables -t nat -A POSTROUTING -s ${LXC_NETWORK} ! -d ${LXC_NETWORK} -j 
MASQUERADE
dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces 
--pid-file=${varrun}/dnsmasq.pid --conf-file= --listen-address ${LXC_ADDR} 
--dhcp-range ${LXC_DHCP_RANGE} --dhcp-lease-max=${LXC_DHCP_MAX} 
--dhcp-no-override --except-interface=lo --interface=${LXC_BRIDGE} 
--dhcp-leasefile=/var/lib/misc/dnsmasq.${LXC_BRIDGE}.leases 
--dhcp-authoritative || cleanup
touch ${varrun}/network_up
end script

post-stop script
[ -f /etc/default/lxc ]  . /etc/default/lxc
[ -f ${varrun}/network_up ] || exit 0;
# if $LXC_BRIDGE has attached interfaces, don't shut it down
ls /sys/class/net/${LXC_BRIDGE}/brif/*  /dev/null 21  exit 0;

if [ -d /sys/class/net/${LXC_BRIDGE} ]; then
ifconfig ${LXC_BRIDGE} down
iptables -t nat -D POSTROUTING -s ${LXC_NETWORK} ! -d 
${LXC_NETWORK} -j MASQUERADE || true
pid=`cat ${varrun}/dnsmasq.pid 2/dev/null`  kill -9 $pid || 
true
rm -f ${varrun}/dnsmasq.pid
brctl delbr ${LXC_BRIDGE}
fi
rm -f ${varrun}/network_up
end script


** Changed in: lxc (Ubuntu)
   Status: Incomplete = New

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


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

2013-01-17 Thread Martin Albisetti
Also, I have a completely different machine that I upgraded, exact same
problem.

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 948447] Re: Starting an LXC changes the volume (sound!) of the host

2012-03-06 Thread Martin Albisetti
-- 
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/948447

Title:
  Starting an LXC changes the volume (sound!) of the host

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 948447] [NEW] Starting an LXC changes the volume (sound!) of the host

2012-03-06 Thread Martin Albisetti
Public bug reported:

This has been happening at least since 11.10 on several different computers.
Whenever I start an LXC, it changes the volume of the host computer. Sometimes 
it turns it up, sometimes down.
It's quite puzzling  :)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lxc 0.7.5-3ubuntu33
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu2
Architecture: amd64
Date: Tue Mar  6 18:16:57 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120215.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise

-- 
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/948447

Title:
  Starting an LXC changes the volume (sound!) of the host

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 938752] Re: Lucid containers don't have sudo set up

2012-02-22 Thread Martin Albisetti
-- 
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/938752

Title:
  Lucid containers don't have sudo set up

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 938752] [NEW] Lucid containers don't have sudo set up

2012-02-22 Thread Martin Albisetti
Public bug reported:

With the latest ubuntu template change, the ubuntu user in the Lucid
containers no longer have sudo access and needs to be manually added.

There's a temporary workaround (from outside your container): chroot
/var/lib/lxc/container/rootfs passwd

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lxc 0.7.5-3ubuntu29
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Wed Feb 22 12:20:50 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: Upgraded to precise on 2011-12-02 (82 days ago)

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise

-- 
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/938752

Title:
  Lucid containers don't have sudo set up

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 938765] Re: Container will no longer start under 12.04

2012-02-22 Thread Martin Albisetti
-- 
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/938765

Title:
  Container will no longer start under 12.04

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 938765] [NEW] Container will no longer start under 12.04

2012-02-22 Thread Martin Albisetti
Public bug reported:

beuno@beuno-laptop:~/canonical/ubunet/trunk$ sudo lxc-start -n u1-server-lp
lxc-start: failed to create the command service point
lxc-start: failed to add command handler to mainloop
lxc-start: mainloop exited with an error

Debug log: http://paste.ubuntu.com/852806/

/var/lib/lxc/u1-server-lp/config: http://paste.ubuntu.com/852821/
/var/lib/lxc/u1-server-lp/fstab: http://paste.ubuntu.com/852822/

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lxc 0.7.5-3ubuntu29
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Wed Feb 22 12:42:04 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: Upgraded to precise on 2011-12-02 (82 days ago)

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise

-- 
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/938765

Title:
  Container will no longer start under 12.04

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs