On Wed, Nov 12, 2014 at 05:33:09PM -0500, Michael H. Warfield wrote:
> On Wed, 2014-11-12 at 15:35 -0600, Tycho Andersen wrote:
> > On Wed, Nov 12, 2014 at 01:42:23PM -0600, Tycho Andersen wrote:
> > > On Wed, Nov 12, 2014 at 06:55:22PM +, Serge Hallyn wrote:
> > > > Make sure no other lxd is r
On Wed, 2014-11-12 at 15:35 -0600, Tycho Andersen wrote:
> On Wed, Nov 12, 2014 at 01:42:23PM -0600, Tycho Andersen wrote:
> > On Wed, Nov 12, 2014 at 06:55:22PM +, Serge Hallyn wrote:
> > > Make sure no other lxd is running
> > >
> > > sudo killall -9 lxd
> > >
> > > and remove the sock by h
On Wed, Nov 12, 2014 at 01:42:23PM -0600, Tycho Andersen wrote:
> On Wed, Nov 12, 2014 at 06:55:22PM +, Serge Hallyn wrote:
> > Make sure no other lxd is running
> >
> > sudo killall -9 lxd
> >
> > and remove the sock by hand
> >
> > sudo rm /var/lib/lxd/unix.socket
> >
> > Now it should st
On Wed, Nov 12, 2014 at 06:55:22PM +, Serge Hallyn wrote:
> Make sure no other lxd is running
>
> sudo killall -9 lxd
>
> and remove the sock by hand
>
> sudo rm /var/lib/lxd/unix.socket
>
> Now it should start fine.
>
> If we are leaving that socket around when we error out bc of no
> ava
On Thu, 2014-11-13 at 00:05 +0530, Kunal Kushwaha wrote:
> Hi
> Thanks for your quick reply.
> It has resolved the issue, but now I am facing another issue.
I haven't done anything with lxd up to this point so I'm just making a
general observation. I think you have a couple of things mixed up...
Thanks Serge,
It worked :)
I had killed the lxd process forcefully, I think due to that the
socket file was not deleted.
Regards,
Kunal Kushwaha
On Thu, Nov 13, 2014 at 12:25 AM, Serge Hallyn wrote:
> Make sure no other lxd is running
>
> sudo killall -9 lxd
>
> and remove the sock by hand
>
>
Make sure no other lxd is running
sudo killall -9 lxd
and remove the sock by hand
sudo rm /var/lib/lxd/unix.socket
Now it should start fine.
If we are leaving that socket around when we error out bc of no
availalbe subuids, then that is definately a bug.
Quoting Kunal Kushwaha (kunalkushwaha.
Hi
Thanks for your quick reply.
It has resolved the issue, but now I am facing another issue.
$sudo ./lxd --tcp 10.0.3.1:
error: cannot listen on unix socket: listen unix
/var/lib/lxd/unix.socket: bind: address already in use
I confirmed these port are not used, and have tried other ports t
Hi Stéphane,
I am now setting up my dev environment in ubuntu-trusty-32 with
kernel 3.13.0-39-generic.
Now I am getting problem
root@vagrant-ubuntu-trusty-32:/home/vagrant/go/src/github.com/lxc/lxd/lxd# ./lxd
error: User "root" has no subuids.
Basically I am creating dev environment in vagran
On Wed, Nov 12, 2014 at 11:38:17PM +0530, Kunal Kushwaha wrote:
> Hi Stéphane,
>
> I am now setting up my dev environment in ubuntu-trusty-32 with
> kernel 3.13.0-39-generic.
> Now I am getting problem
>
> root@vagrant-ubuntu-trusty-32:/home/vagrant/go/src/github.com/lxc/lxd/lxd#
> ./lxd
> erro
I tested Tokudb long ago but strange enough you cannot have huge-pages
enabled in the server. My servers have a minimum of 500 G of RAM, so the
idea is a no-go. All virtualization technologies benefit from huge-pages. I
don´t know if the Tokudb developers live in a parallel universe.
On Tue, Nov 1
Hello again,
I think I figured out the issue.
lxcbr0 and one of the lxc containers seem to assuming same mac address,
thus during the database exchange stage(which is unicast with duplicated
mac address) , the lxcbr0 which has assumed the destination mac address
simply drops the DB description req
12 matches
Mail list logo
