Hi!
Both lxd.log are empty :(
ps output - in attachment
пт, 17 авг. 2018 г. в 18:06, Stéphane Graber :
> On Fri, Aug 17, 2018 at 05:56:24PM +0300, Andriy Tovstik wrote:
> > Hi!
> >
> > пт, 17 авг. 2018 г. в 17:46, Stéphane Graber :
> >
> > > On Fri, Aug 17, 2018 at 01:20:42PM +0300, Andriy Tovs
That's somewhat unlikely though it's hard to tell post-reboot.
It could be that something upset the kernel (zfs has been known to do
that sometimes) and LXD couldn't be killed anymore as it was stuck on
the kernel.
If this happens to you again, try recording the following before rebooting:
- jou
I tried snap refresh alone but did not fix the problem.
Could it be something involved with the kernel update
linux-image-4.15.0-32?
On Friday, August 17, 2018 11:56 PM, Stéphane Graber wrote:
Apt upgrades shouldn't really be needed, though certainly good to make
sure the rest of the system s
Apt upgrades shouldn't really be needed, though certainly good to make
sure the rest of the system stays up to date :)
The most important part is ensuring that all cluster nodes run the same
version of LXD (3.4 in this case), once they all do, the cluster should
allow queries.
This upgrade proced
I just had roughly the same problem.
The way I cured it was to snap refresh
then sudo apt update and then
sudo apt upgrade
current lxd snap is 3.4
current linux-image-4.15.0-32-generic
I then rebooted.
(same procedure on all machines)
On Friday, August 17, 2018 10:46 PM, Stéphane Graber w
On Fri, Aug 17, 2018 at 05:56:24PM +0300, Andriy Tovstik wrote:
> Hi!
>
> пт, 17 авг. 2018 г. в 17:46, Stéphane Graber :
>
> > On Fri, Aug 17, 2018 at 01:20:42PM +0300, Andriy Tovstik wrote:
> > > Hi, all!
> > >
> > > Some time ago I installed a dual node LXD cluster. Today I logged in to
> > the
Hi!
пт, 17 авг. 2018 г. в 17:46, Stéphane Graber :
> On Fri, Aug 17, 2018 at 01:20:42PM +0300, Andriy Tovstik wrote:
> > Hi, all!
> >
> > Some time ago I installed a dual node LXD cluster. Today I logged in to
> the
> > node and tried to execute
> > lxc exec container -- bash
> > but command hang
Hello,
does "ps aux | grep lxd" show more than one lxd process running? (on
either of the two nodes).
Andriy Tovstik writes:
> Hi, all!
>
> Some time ago I installed a dual node LXD cluster. Today I logged in to the
> node and tried to execute
> lxc exec container -- bash
> but command hanged.
On Fri, Aug 17, 2018 at 01:20:42PM +0300, Andriy Tovstik wrote:
> Hi, all!
>
> Some time ago I installed a dual node LXD cluster. Today I logged in to the
> node and tried to execute
> lxc exec container -- bash
> but command hanged.
> Also, all lxc commands are unresponsible: i'm not able to inte
Hi, all!
Some time ago I installed a dual node LXD cluster. Today I logged in to the
node and tried to execute
lxc exec container -- bash
but command hanged.
Also, all lxc commands are unresponsible: i'm not able to interact with my
cluster and my containers.
I tried to restart snap.lxd.daemon but
On Thu, Aug 16, 2018 at 09:07:16PM +0200, Dr. Todor Dimitrov wrote:
> A follow-up: I assume the same applies to sys:mixed vs. sys:rw, correct?
Yes. Newever LXC versions will always set sys:rw for unpriv containers.
Christian
>
> Todor
>
> > On 23. May 2018, at 19:09, Christian Brauner wrote:
11 matches
Mail list logo
