[lxc-users] lxd 3.0.0: What is a "managed" network? Only managed networks can be modified.

2018-05-06 Thread Gaétan QUENTIN 
lxc network list
+-+--+-+-+-+
|  NAME   |   TYPE   | MANAGED | DESCRIPTION | USED BY |
+-+--+-+-+-+
+-+--+-+-+-+
| lxdbr0  | bridge   | NO  | | 71  |


what does mean managed network?


and why can i modify bridge.driver?


lxc network set lxdbr0 bridge.driver openvswitch
Error: Only managed networks can be modified.


Regards.

-- 
Gaétan QUENTIN
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] lxd 3.0.0: What is a "managed" network? Only managed networks can be modified.

2018-05-06 Thread Fajar A. Nugraha 
On Mon, May 7, 2018 at 2:10 AM, Gaétan QUENTIN  wrote:
>
> lxc network list
> +-+--+-+-+-+
> |  NAME   |   TYPE   | MANAGED | DESCRIPTION | USED BY |
> +-+--+-+-+-+
> +-+--+-+-+-+
> | lxdbr0  | bridge   | NO  | | 71  |
>
>
> what does mean managed network?
>

Someting lxd creates, i.e. during 'lxd init' or with 'lxc network create'

>
> and why can i modify bridge.driver?
>
>
> lxc network set lxdbr0 bridge.driver openvswitch
> Error: Only managed networks can be modified.

How did you install lxd? My guess is that an external program creates
it (e.g. you create it on /etc/network/interfaces, or leftover service
from an old lxd version)

-- 
Fajar
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] filesystem full -> lxd won't start after freeing space

2018-05-06 Thread Tomasz Chmielewski 

On 2018-05-06 17:27, Tomasz Chmielewski wrote:

On 2018-05-06 17:16, Tomasz Chmielewski wrote:

On 2018-05-06 17:07, Tomasz Chmielewski wrote:

I have a Ubuntu 16.04 server with LXD 3.0 installed from snap.

I've filled the disk to 100% to get "No space left on device".


(...)

The same error shows up after freeing space and restarting the 
server.


How to debug this?


Also found this (panic: txn not found):

# snap logs -n 1000 lxd


(...)


2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.57677: fsm:
restore=1101 filename: db.bin


I've copied /var/snap/lxd/common/lxd/database/global/db.bin to
/tmp/db.bin - and I'm able to open it with sqlite3.

Not sure what's broken there.


This issue is very similar:

https://github.com/lxc/lxd/issues/4465


Tomasz Chmielewski
https://lxadm.com
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] filesystem full -> lxd won't start after freeing space

2018-05-06 Thread Free Ekanayaka 
Hello,

Tomasz Chmielewski  writes:

> I have a Ubuntu 16.04 server with LXD 3.0 installed from snap.
>
> I've filled the disk to 100% to get "No space left on device".
>
> A while later, it was not possible to use "lxc shell container" or "lxc 
> list", because of:
>
> Error: Get http://unix.socket/1.0: dial unix 
> /var/snap/lxd/common/lxd/unix.socket: connect: connection refused
>
>
> The same error shows up after freeing space and restarting the server.
>
> How to debug this?
>
> No scary messages in /var/snap/lxd/common/lxd/logs/lxd.log"

[...]
> lvl=info msg="LXD isn't socket activated" t=2018-05-06T08:00:36+

This particular message seems weird. AFAIK LXD should be socket
activated when deployed with the snap.

Perhaps it's related to the disk full issue? Maybe Stephane has more
insight bout this.

About the panic, I assume it's still the case that you can't start the
LXD daemon because it panics at startup all the times?

Please would send us tar with the content /var/snap/lxd/common/lxd/database?
(or /var/snap/lxd/common/lxd/raft/, depending on which version of the
snap you use).

I believe this particular crash has been solved in our master branches,
but probably it's not the build you have. I'll give a look at the data
you send to confirm that, and possibly post a workaround.

Free
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] filesystem full -> lxd won't start after freeing space

2018-05-06 Thread Tomasz Chmielewski 

On 2018-05-06 17:55, Free Ekanayaka wrote:


Perhaps it's related to the disk full issue? Maybe Stephane has more
insight bout this.

About the panic, I assume it's still the case that you can't start the
LXD daemon because it panics at startup all the times?


Correct.


Please would send us tar with the content 
/var/snap/lxd/common/lxd/database?

(or /var/snap/lxd/common/lxd/raft/, depending on which version of the
snap you use).

I believe this particular crash has been solved in our master branches,
but probably it's not the build you have. I'll give a look at the data
you send to confirm that, and possibly post a workaround.


I've sent it to your free.*@canonical* address, let me know if you need 
more info.



Tomasz Chmielewski
https://lxadm.com
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Re: [lxc-users] filesystem full -> lxd won't start after freeing space

2018-05-06 Thread Tomasz Chmielewski 

On 2018-05-06 17:07, Tomasz Chmielewski wrote:

I have a Ubuntu 16.04 server with LXD 3.0 installed from snap.

I've filled the disk to 100% to get "No space left on device".


(...)


The same error shows up after freeing space and restarting the server.

How to debug this?


Also found this (panic: txn not found):

# snap logs -n 1000 lxd
(...)

2018-05-06T08:08:06Z systemd[1]: Stopping Service for snap application 
lxd.daemon...

2018-05-06T08:08:06Z lxd.daemon[4176]: => Stop reason is: crashed
2018-05-06T08:08:06Z systemd[1]: Stopped Service for snap application 
lxd.daemon.
2018-05-06T08:08:06Z systemd[1]: Started Service for snap application 
lxd.daemon.

2018-05-06T08:08:06Z lxd.daemon[4215]: => Preparing the system
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Loading snap configuration
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Setting up mntns symlink
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Setting up kmod wrapper
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Preparing /boot
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Preparing a clean copy of 
/run
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Preparing a clean copy of 
/etc

2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Setting up ceph configuration
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Setting up LVM configuration
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Rotating logs
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Escaping the systemd cgroups
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Escaping the systemd process 
resource limits
2018-05-06T08:08:06Z lxd.daemon[4215]: ==> Detected kernel with partial 
AppArmor support

2018-05-06T08:08:06Z lxd.daemon[4215]: => Re-using existing LXCFS
2018-05-06T08:08:06Z lxd.daemon[4215]: => Starting LXD
2018-05-06T08:08:06Z lxd.daemon[4215]: lvl=warn msg="CGroup memory swap 
accounting is disabled, swap limits will be ignored." 
t=2018-05-06T08:08:06+

2018-05-06T08:08:06Z lxd.daemon[4215]: panic: txn not found
2018-05-06T08:08:06Z lxd.daemon[4215]: trace:
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.57659: fsm: 
restore=1101 start
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.57659: fsm: 
restore=1101 database size: 4096
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.57660: fsm: 
restore=1101 wal size: 325512
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.57677: fsm: 
restore=1101 filename: db.bin
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.57677: fsm: 
restore=1101 transaction ID:
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.57732: fsm: 
restore=1101 open follower: db.bin
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.57817: fsm: 
restore=1101 done
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.58869: fsm: 
term=1 index=1102 cmd=frames txn=1101 pages=3 commit=1 start
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.59327: fsm: 
term=1 index=1102 cmd=frames txn=1101 pages=3 commit=1 unregister txn
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.59327: fsm: 
term=1 index=1102 cmd=frames txn=1101 pages=3 commit=1 done
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.59333: fsm: 
term=1 index=1103 cmd=frames txn=1102 pages=3 commit=1 start
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.59377: fsm: 
term=1 index=1103 cmd=frames txn=1102 pages=3 commit=1 unregister txn
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.59378: fsm: 
term=1 index=1103 cmd=frames txn=1102 pages=3 commit=1 done
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60338: fsm: 
term=1 index=1104 cmd=frames txn=1103 pages=3 commit=1 start
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60400: fsm: 
term=1 index=1104 cmd=frames txn=1103 pages=3 commit=1 unregister txn
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60400: fsm: 
term=1 index=1104 cmd=frames txn=1103 pages=3 commit=1 done
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60407: fsm: 
term=1 index=1105 cmd=frames txn=1104 pages=11 commit=1 start
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60461: fsm: 
term=1 index=1105 cmd=frames txn=1104 pages=11 commit=1 unregister txn
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60461: fsm: 
term=1 index=1105 cmd=frames txn=1104 pages=11 commit=1 done
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60462: fsm: 
term=1 index=1106 cmd=frames txn=1105 pages=3 commit=1 start
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60501: fsm: 
term=1 index=1106 cmd=frames txn=1105 pages=3 commit=1 unregister txn
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60501: fsm: 
term=1 index=1106 cmd=frames txn=1105 pages=3 commit=1 done
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60502: fsm: 
term=1 index=1107 cmd=frames txn=1106 pages=3 commit=1 start
2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.60540: fsm: 
term=1 index=1107 cmd=frames txn=1106 pages=3 commit=1 unregister txn

Re: [lxc-users] filesystem full -> lxd won't start after freeing space

2018-05-06 Thread Tomasz Chmielewski 

On 2018-05-06 17:16, Tomasz Chmielewski wrote:

On 2018-05-06 17:07, Tomasz Chmielewski wrote:

I have a Ubuntu 16.04 server with LXD 3.0 installed from snap.

I've filled the disk to 100% to get "No space left on device".


(...)


The same error shows up after freeing space and restarting the server.

How to debug this?


Also found this (panic: txn not found):

# snap logs -n 1000 lxd


(...)


2018-05-06T08:08:06Z lxd.daemon[4215]: 2018-05-06 08:08:06.57677: fsm:
restore=1101 filename: db.bin


I've copied /var/snap/lxd/common/lxd/database/global/db.bin to 
/tmp/db.bin - and I'm able to open it with sqlite3.


Not sure what's broken there.


Tomasz Chmielewski
https://lxadm.com
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users