Comment 5 for bug 1000174

 I don't know if lxc was previously working or not. Another person has used
this computer recently, and I don't know what they may have done to it. I
remember installing lxc some time ago, but never had time to actually do
anything with it.

On 05/16/2012 11:04 AM, Serge Hallyn wrote:

Thanks for reporting this bug. Interesting - so installing mdadm
stopped lxc from starting? I can't reproduce that here, unfortunately.

Do you have autostart containers defined? (what does ls -l
/etc/lxc/auto show?)

total 0

 Can you add the line:

console output

right underneath the 'stop on' lines in both /etc/init/lxc.conf and
/etc/init/lxc-net.conf, then do

stop lxc
start lxc

and show the output here?

rblenis@rblenis-laptop:/etc/init$ stop lxc stop: Rejected send message, 1
matched rules; type="method_call", sender=":1.73" (uid=1000 pid=2862
comm="stop lxc ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error
name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0
pid=1 comm="/sbin/init")

rblenis@rblenis-laptop:/etc/init$ start lxc start: Rejected send message, 1
matched rules; type="method_call", sender=":1.74" (uid=1000 pid=2870
comm="start lxc ") interface="com.ubuntu.Upstart0_6.Job" member="Start"
error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart"
(uid=0 pid=1 comm="/sbin/init")

** Changed in: lxc (Ubuntu)
   Importance: Undecided => Medium

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