Confirmed, that breaks it for me. Will fix that.
** Changed in: lxc (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
** Summary changed:
- package lxc 0.7.5-3ubuntu54 failed to install/upgrade: subprocess installed
post-install
Hi, I have the same issue. I played around and got a good way through
the issue. Starting lxc itself is ok. It's starting lxc-net that is
problematic. It is the starting of dnsmasq that is the issue.
It appears to be (at least in my case) caused by having /bin/sh set to
bash.
If link /bin/sh to /
Perplexing.
Please do so, to make sure you don't get future failures with 'start
lxc' on boot or package upgrades. I'll mark this bug fix released for
now, but if and when you start looking into using lxc and want to debug
it, please feel free to reply and re-open this bug.
** Changed in: lxc (U
I did not change /etc/default/lxc.
On 05/17/2012 02:56 PM, Serge Hallyn wrote:
> Quoting Robert Blenis (1000...@bugs.launchpad.net):
>> rblenis@rblenis-laptop:/etc/init$ sudo stop lxc-net
>> stop: Unknown instance:
>> rblenis@rblenis-laptop:/etc/init$ sudo start lxc-net
>> start: Job failed to sta
Quoting Robert Blenis (1000...@bugs.launchpad.net):
> rblenis@rblenis-laptop:/etc/init$ sudo stop lxc-net
> stop: Unknown instance:
> rblenis@rblenis-laptop:/etc/init$ sudo start lxc-net
> start: Job failed to start
Since lxc started successfully, does that mean that you've set
USE_LXC_BRIDGE=fals
rblenis@rblenis-laptop:/etc/init$ sudo stop lxc-net
stop: Unknown instance:
rblenis@rblenis-laptop:/etc/init$ sudo start lxc-net
start: Job failed to start
On Thu, May 17, 2012 at 8:41 AM, Serge Hallyn <1000...@bugs.launchpad.net>wrote:
> Quoting Robert Blenis (1000...@bugs.launchpad.net):
> > s
Quoting Robert Blenis (1000...@bugs.launchpad.net):
> should I remove the 'console output' line from the init config file
> first?
No, it's what will hopefully show errors in your terminal.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
should I remove the 'console output' line from the init config file
first?
On 05/16/2012 09:15 PM, Serge Hallyn wrote:
> Interesting so when you restarted lxc, it worked. what if you do
>
> sudo stop lxc-net
> sudo start lxc-net
>
> ?
>
--
You received this bug notification because you are a me
Interesting so when you restarted lxc, it worked. what if you do
sudo stop lxc-net
sudo start lxc-net
?
--
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/1000174
Title:
package lxc 0.7.
On Wed, May 16, 2012 at 2:28 PM, Serge Hallyn
<1000...@bugs.launchpad.net>wrote:
> Sorry, these should have been
>
> sudo lxc stop
> sudo lxc start
>
rblenis@rblenis-laptop:/etc/init$ sudo stop lxc
lxc stop/waiting
rblenis@rblenis-laptop:/etc/init$ sudo start lxc
lxc start/running
>
> If you st
Sorry, these should have been
sudo lxc stop
sudo lxc start
If you still care to debug and provide that output, that would be great.
But if you aren't using lxc anyway, and simply wish to remove it, you
can do:
sudo apt-get purge lxc
You can also leave lxc installed, but stop it from starting it
also, before installing mdadm, I did let a bunch of updates install, and
I think it may have complained then as well, but I had to get some work
done, and everything else seemed ok. Then when I needed mdadm to test
an external raid box, this is when I had time to investigate further.
sorry I d
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 re
(note - actually dmesg shows that lxc-net is the one failing to start)
--
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/1000174
Title:
package lxc 0.7.5-3ubuntu54 failed to install/upgrad
(marking incomplete while awaiting response to get more information to
debug)
--
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/1000174
Title:
package lxc 0.7.5-3ubuntu54 failed to install
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?)
Can you add the line:
console output
right underneath the 'stop on' lines in
** Tags removed: need-duplicate-check
--
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/1000174
Title:
package lxc 0.7.5-3ubuntu54 failed to install/upgrade: subprocess
installed post-in
--
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/1000174
Title:
package lxc 0.7.5-3ubuntu54 failed to install/upgrade: subprocess
installed post-installation script returned error exit s
18 matches
Mail list logo
