Discussion:
Instabilties
(too old to reply)
Pierre Couderc
2018-08-30 10:34:41 UTC
Permalink
Currently I heve many instabilities with lxd.
When I try to start it, I get :
***@couderc:~$ export GOPATH=~/***@couderc:~$ sudo -E -***@couderc:~# echo $LD_LIBRARY_PATH/home/nous/go/deps/sqlite/.libs/:/home/nous/go/deps/dqlite/.libs/***@couderc:~# cd go/***@couderc:~/go/bin# lsdeps  fuidshift  lxc  lxc-to-lxd  lxd  lxd-benchmark  lxd-p2c  macaroon-***@couderc:~/go/bin# nohup lxd --group sudo &[1] ***@couderc:~/go/bin# nohup: les entrées sont ignorées et la sortie est ajoutée à 'nohup.out'lsdeps  fuidshift  lxc  lxc-to-lxd  lxd  lxd-benchmark  lxd-p2c  macaroon-identity  nohup.out[1]+  Termine 2               nohup lxd --group ***@couderc:~/go/bin# lxc lsError: Get http://unix.socket/1.0: dial unix /var/lib/lxd/unix.socket: connect: connection ***@couderc:~/go/bin# cat nohup.outlvl=warn msg="AppArmor support has been disabled because of lack of kernel support" t=2018-08-30T12:23:21+0200lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored." t=2018-08-30T12:23:21+0200panic: unknown data type
goroutine 1 [running]:github.com/CanonicalLtd/go-dqlite/internal/client.(*Rows).Next(0xc42000d660, 0xc4203ec6c0, 0x3, 0x3, 0xc420044070, 0xc4204b8bd0)        /home/nous/go/src/github.com/CanonicalLtd/go-dqlite/internal/client/message.go:549 +0x914github.com/CanonicalLtd/go-dqlite.(*Rows).Next(0xc42000d660, 0xc4203ec6c0, 0x3, 0x3, 0xf24e40, 0xc4200dd268)        /home/nous/go/src/github.com/CanonicalLtd/go-dqlite/driver.go:515 +0x4bdatabase/sql.(*Rows).nextLocked(0xc4201ecc00, 0xc420240000)        /usr/lib/go-1.10/src/database/sql/sql.go:2622 +0xc4database/sql.(*Rows).Next.func1()        /usr/lib/go-1.10/src/database/sql/sql.go:2600 +0x3cdatabase/sql.withLock(0x11fa640, 0xc4201ecc30, 0xc4204b8c88)        /usr/lib/go-1.10/src/database/sql/sql.go:3032 +0x63database/sql.(*Rows).Next(0xc4201ecc00, 0xc4203ed080)        /usr/lib/go-1.10/src/database/sql/sql.go:2599 +0x7agithub.com/lxc/lxd/lxd/db/query.SelectObjects(0xc4201eca00, 0xc4203e9c70, 0xc4203ba000, 0xc0, 0xc4203e9b70, 0x1, 0x1, 0x0, 0x0)        /home/nous/go/src/github.com/lxc/lxd/lxd/db/query/objects.go:18 +0xdagithub.com/lxc/lxd/lxd/db.(*ClusterTx).containerArgsList(0xc4203e9b30, 0x1201201, 0xc4200ba030, 0x0, 0xc420270101, 0xc4201eca00, 0x0)        /home/nous/go/src/github.com/lxc/lxd/lxd/db/containers.go:442 +0x5a7github.com/lxc/lxd/lxd/db.(*ClusterTx).ContainerArgsNodeList(0xc4203e9b30, 0x0, 0x0, 0xc4204b90a8, 0x771d7c, 0xc420018dc0)        /home/nous/go/src/github.com/lxc/lxd/lxd/db/containers.go:347 +0x30main.containerLoadNodeAll.func1(0xc4203e9b30, 0x0, 0x0)        /home/nous/go/src/github.com/lxc/lxd/lxd/container.go:1200 +0x38github.com/lxc/lxd/lxd/db.(*Cluster).transaction.func1.1(0xc4201eca00, 0xc4201eca00, 0x0)        /home/nous/go/src/github.com/lxc/lxd/lxd/db/db.go:309 +0x42github.com/lxc/lxd/lxd/db/query.Transaction(0xc420018dc0, 0xc4204b9130, 0x7, 0x8)        /home/nous/go/src/github.com/lxc/lxd/lxd/db/query/transaction.go:17 +0x5agithub.com/lxc/lxd/lxd/db.(*Cluster).transaction.func1(0x7f3554e01000, 0x0)        /home/nous/go/src/github.com/lxc/lxd/lxd/db/db.go:307 +0x55github.com/lxc/lxd/lxd/db/query.Retry(0xc4204b91e0, 0xc4203e9b30, 0x434b69)        /home/nous/go/src/github.com/lxc/lxd/lxd/db/query/retry.go:20 +0xaegithub.com/lxc/lxd/lxd/db.(*Cluster).transaction(0xc42026ca50, 0xc4204b9290, 0xc42026ca60, 0xc420272b60)        /home/nous/go/src/github.com/lxc/lxd/lxd/db/db.go:306 +0x6dgithub.com/lxc/lxd/lxd/db.(*Cluster).Transaction(0xc42026ca50, 0xc4204b9290, 0x0, 0x0)        /home/nous/go/src/github.com/lxc/lxd/lxd/db/db.go:270 +0x80main.containerLoadNodeAll(0xc4203ec420, 0x1902720, 0x4, 0xc42003e270, 0x2b, 0x1928910)        /home/nous/go/src/github.com/lxc/lxd/lxd/container.go:1198 +0x67main.deviceInotifyDirRescan(0xc4203ec420)        /home/nous/go/src/github.com/lxc/lxd/lxd/devices.go:1844 +0x43main.(*Daemon).init(0xc4202c2750, 0xc4202a78f0, 0x40e446)        /home/nous/go/src/github.com/lxc/lxd/lxd/daemon.go:628 +0x13c4main.(*Daemon).Init(0xc4202c2750, 0xc4202c2750, 0xc420092a80)        /home/nous/go/src/github.com/lxc/lxd/lxd/daemon.go:363 +0x2fmain.(*cmdDaemon).Run(0xc420272980, 0xc4202b8500, 0xc420272a80, 0x0, 0x2, 0x0, 0x0)        /home/nous/go/src/github.com/lxc/lxd/lxd/main_daemon.go:61 +0x266main.(*cmdDaemon).Run-fm(0xc4202b8500, 0xc420272a80, 0x0, 0x2, 0x0, 0x0)        /home/nous/go/src/github.com/lxc/lxd/lxd/main_daemon.go:36 +0x52github.com/spf13/cobra.(*Command).execute(0xc4202b8500, 0xc4200a4160, 0x2, 0x2, 0xc4202b8500, 0xc4200a4160)        /home/nous/go/src/github.com/spf13/cobra/command.go:762 +0x468github.com/spf13/cobra.(*Command).ExecuteC(0xc4202b8500, 0x0, 0xc4202c0c80, 0xc4202c0c80)        /home/nous/go/src/github.com/spf13/cobra/command.go:852 +0x30agithub.com/spf13/cobra.(*Command).Execute(0xc4202b8500, 0xc4202a7e00, 0x1)        /home/nous/go/src/github.com/spf13/cobra/command.go:800 +0x2bmain.main()        /home/nous/go/src/github.com/lxc/lxd/lxd/main.go:164 +***@couderc:~/go/bin# ^***@couderc:~/go/bin#

The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
Free Ekanayaka
2018-08-30 11:02:39 UTC
Permalink
Hello,

this seems the same failure you reported earlier (thread with subject
"lxd refuses to start ...").

When you sent me the database tarball last time, I didn't see any issue
and I could not reproduce the failure. Can you please double check that
your version of the dqlite C library is up to date (tag v0.2.2) and the
go-dqlite git close under GOPATH actually points to the master version
on github? Just run "git status" under $GOPATH/github.com/CanonicalLtd/go-dqlite
and compare it with github.

If all your dependencies turn out to be up-to-date, you may want to
again send me a tarball of your /var/lib/lxd/database directory, and
I'll double check too.

Free
Post by Pierre Couderc
Currently I heve many instabilities with lxd.
The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users
Pierre Couderc
2018-08-30 11:40:54 UTC
Permalink
I am with lasts releases from git. For dqlite, last log is:

commit f160665d9e50e39d156591546732a2e0b3712f73
Author: Free Ekanayaka <***@canonical.com>
Date:   Mon Aug 20 19:04:10 2018 +0200

Mmm, I can send you again my tarball but it will be the same as I did send you before...
 It seems th eproblem is linked with my computer... Maybe I could enavle some traces on my computer ?



Le jeudi 30 août 2018 à 13:02:44 UTC+2, Free Ekanayaka <***@canonical.com> a écrit :

Hello,

this seems the same failure you reported earlier (thread with subject
"lxd refuses to start ...").

When you sent me the database tarball last time, I didn't see any issue
and I could not reproduce the failure. Can you please double check that
your version of the dqlite C library is up to date (tag v0.2.2) and the
go-dqlite git close under GOPATH actually points to the master version
on github? Just run "git status" under $GOPATH/github.com/CanonicalLtd/go-dqlite
and compare it with github.

If all your dependencies turn out to be up-to-date, you may want to
again send me a tarball of your /var/lib/lxd/database directory, and
I'll double check too.

Free
Post by Pierre Couderc
Currently I heve many instabilities with lxd.
The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users
Free Ekanayaka
2018-08-30 12:07:16 UTC
Permalink
I have a few questions:

1) Does the failure happen when you start with a fresh lxd instance?

2) If the answer to 1) is "no", is there are repeatable process that you
have that brings you from a fresh lxd instance to the point were it
crashes with the failure you pasted?

3) Regardless of the answers to 1) and 2), does the failure happen
consistently? I.e. does it happen every time you run "lxc ls".

Free
Post by Pierre Couderc
commit f160665d9e50e39d156591546732a2e0b3712f73
Date:   Mon Aug 20 19:04:10 2018 +0200
Mmm, I can send you again my tarball but it will be the same as I did send you before...
 It seems th eproblem is linked with my computer... Maybe I could enavle some traces on my computer ?
Hello,
this seems the same failure you reported earlier (thread with subject
"lxd refuses to start ...").
When you sent me the database tarball last time, I didn't see any issue
and I could not reproduce the failure. Can you please double check that
your version of the dqlite C library is up to date (tag v0.2.2) and the
go-dqlite git close under GOPATH actually points to the master version
on github? Just run "git status" under $GOPATH/github.com/CanonicalLtd/go-dqlite
and compare it with github.
If all your dependencies turn out to be up-to-date, you may want to
again send me a tarball of your /var/lib/lxd/database directory, and
I'll double check too.
Free
Post by Pierre Couderc
Currently I heve many instabilities with lxd.
The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users
Pierre Couderc
2018-08-30 12:14:56 UTC
Permalink
When I start a new clean lxd instance, I can lxd init, launch first.
Then I try to work, it works, I success import from other lxd.
At some point, some lxc command fails, such as lxc copy (local).
Then nothing works more, any lxc command get soxket error.
If I reboot, "lxc ls" gives the same error and the messages that I have sent.
I hope I am clear...

Le jeudi 30 août 2018 à 14:07:19 UTC+2, Free Ekanayaka <***@canonical.com> a écrit :

I have a few questions:

1) Does the failure happen when you start with a fresh lxd instance?

2) If the answer to 1) is "no", is there are repeatable process that you
  have that brings you from a fresh lxd instance to the point were it
  crashes with the failure you pasted?

3) Regardless of the answers to 1) and 2), does the failure happen
  consistently? I.e. does it happen every time you run "lxc ls".

Free
Post by Pierre Couderc
commit f160665d9e50e39d156591546732a2e0b3712f73
Date:   Mon Aug 20 19:04:10 2018 +0200
Mmm, I can send you again my tarball but it will be the same as I did send you before...
 It seems th eproblem is linked with my computer... Maybe I could enavle some traces on my computer ?
 
  Hello,
this seems the same failure you reported earlier (thread with subject
"lxd refuses to start ...").
When you sent me the database tarball last time, I didn't see any issue
and I could not reproduce the failure. Can you please double check that
your version of the dqlite C library is up to date (tag v0.2.2) and the
go-dqlite git close under GOPATH actually points to the master version
on github? Just run "git status" under $GOPATH/github.com/CanonicalLtd/go-dqlite
and compare it with github.
If all your dependencies turn out to be up-to-date, you may want to
again send me a tarball of your /var/lib/lxd/database directory, and
I'll double check too.
Free
Post by Pierre Couderc
Currently I heve many instabilities with lxd.
The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users
Free Ekanayaka
2018-08-30 12:56:34 UTC
Permalink
Hello,

yes, I believe I understand. What's puzzling is that I should be able to
reproduce your problem using database. Would you mind sending me again a
tarball of the /var/lib/lxd/database directory of a LXD which is
currently broken? Just to double check. I don't have any other idea atm.
Post by Pierre Couderc
When I start a new clean lxd instance, I can lxd init, launch first.
Then I try to work, it works, I success import from other lxd.
At some point, some lxc command fails, such as lxc copy (local).
Then nothing works more, any lxc command get soxket error.
If I reboot, "lxc ls" gives the same error and the messages that I have sent.
I hope I am clear...
1) Does the failure happen when you start with a fresh lxd instance?
2) If the answer to 1) is "no", is there are repeatable process that you
  have that brings you from a fresh lxd instance to the point were it
  crashes with the failure you pasted?
3) Regardless of the answers to 1) and 2), does the failure happen
  consistently? I.e. does it happen every time you run "lxc ls".
Free
Post by Pierre Couderc
commit f160665d9e50e39d156591546732a2e0b3712f73
Date:   Mon Aug 20 19:04:10 2018 +0200
Mmm, I can send you again my tarball but it will be the same as I did send you before...
 It seems th eproblem is linked with my computer... Maybe I could enavle some traces on my computer ?
 
  Hello,
this seems the same failure you reported earlier (thread with subject
"lxd refuses to start ...").
When you sent me the database tarball last time, I didn't see any issue
and I could not reproduce the failure. Can you please double check that
your version of the dqlite C library is up to date (tag v0.2.2) and the
go-dqlite git close under GOPATH actually points to the master version
on github? Just run "git status" under $GOPATH/github.com/CanonicalLtd/go-dqlite
and compare it with github.
If all your dependencies turn out to be up-to-date, you may want to
again send me a tarball of your /var/lib/lxd/database directory, and
I'll double check too.
Free
Post by Pierre Couderc
Currently I heve many instabilities with lxd.
The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users
Pierre Couderc
2018-08-30 13:31:34 UTC
Permalink
Maybe it is linked or not.
On another computer, I try to compile on stretch, but I cannot install liblixc-dev (does not iexist une stretch).
I compile anyway and get  :
  CCLD     libdqlite.la
/usr/bin/ld: cannot find -lsqlite3
collect2: error: ld returned 1 exit status
Makefile:812: recipe for target 'libdqlite.la' failed
make[2]: *** [libdqlite.la] Error 1
make[2]: Leaving directory '/root/go/deps/dqlite'
Makefile:697: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/root/go/deps/dqlite'
Makefile:30: recipe for target 'deps' failed
make: *** [deps] Error 2

So I apt install libsqlite3_dev and then deps build.
But is it the "good" libsqlite3 ?
Le jeudi 30 août 2018 à 15:16:55 UTC+2, Pierre Couderc <***@yahoo.fr> a écrit :

Well, I prepare it and I send it you. First time I had removed the containers this time I let them. Please consider them as private data
Le jeudi 30 août 2018 à 14:56:36 UTC+2, Free Ekanayaka <***@canonical.com> a écrit :

Hello,

yes, I believe I understand. What's puzzling is that I should be able to
reproduce your problem using database. Would you mind sending me again a
tarball of the /var/lib/lxd/database directory of a LXD which is
currently broken? Just to double check. I don't have any other idea atm.
Post by Pierre Couderc
When I start a new clean lxd instance, I can lxd init, launch first.
Then I try to work, it works, I success import from other lxd.
At some point, some lxc command fails, such as lxc copy (local).
Then nothing works more, any lxc command get soxket error.
If I reboot, "lxc ls" gives the same error and the messages that I have sent.
I hope I am clear...
 
1) Does the failure happen when you start with a fresh lxd instance?
2) If the answer to 1) is "no", is there are repeatable process that you
  have that brings you from a fresh lxd instance to the point were it
  crashes with the failure you pasted?
3) Regardless of the answers to 1) and 2), does the failure happen
  consistently? I.e. does it happen every time you run "lxc ls".
Free
Post by Pierre Couderc
commit f160665d9e50e39d156591546732a2e0b3712f73
Date:   Mon Aug 20 19:04:10 2018 +0200
Mmm, I can send you again my tarball but it will be the same as I did send you before...
 It seems th eproblem is linked with my computer... Maybe I could enavle some traces on my computer ?
 
  Hello,
this seems the same failure you reported earlier (thread with subject
"lxd refuses to start ...").
When you sent me the database tarball last time, I didn't see any issue
and I could not reproduce the failure. Can you please double check that
your version of the dqlite C library is up to date (tag v0.2.2) and the
go-dqlite git close under GOPATH actually points to the master version
on github? Just run "git status" under $GOPATH/github.com/CanonicalLtd/go-dqlite
and compare it with github.
If all your dependencies turn out to be up-to-date, you may want to
again send me a tarball of your /var/lib/lxd/database directory, and
I'll double check too.
Free
Post by Pierre Couderc
Currently I heve many instabilities with lxd.
The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users  
Free Ekanayaka
2018-08-30 15:16:57 UTC
Permalink
It's not the "good one". You need to build it from source from:

github.com/CanonicalLtd/sqlite

or there debs here:

https://launchpad.net/~dqlite-maintainers/+archive/ubuntu/master
Post by Pierre Couderc
Maybe it is linked or not.
On another computer, I try to compile on stretch, but I cannot install liblixc-dev (does not iexist une stretch).
  CCLD     libdqlite.la
/usr/bin/ld: cannot find -lsqlite3
collect2: error: ld returned 1 exit status
Makefile:812: recipe for target 'libdqlite.la' failed
make[2]: *** [libdqlite.la] Error 1
make[2]: Leaving directory '/root/go/deps/dqlite'
Makefile:697: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/root/go/deps/dqlite'
Makefile:30: recipe for target 'deps' failed
make: *** [deps] Error 2
So I apt install libsqlite3_dev and then deps build.
But is it the "good" libsqlite3 ?
Well, I prepare it and I send it you. First time I had removed the containers this time I let them. Please consider them as private data
Hello,
yes, I believe I understand. What's puzzling is that I should be able to
reproduce your problem using database. Would you mind sending me again a
tarball of the /var/lib/lxd/database directory of a LXD which is
currently broken? Just to double check. I don't have any other idea atm.
Post by Pierre Couderc
When I start a new clean lxd instance, I can lxd init, launch first.
Then I try to work, it works, I success import from other lxd.
At some point, some lxc command fails, such as lxc copy (local).
Then nothing works more, any lxc command get soxket error.
If I reboot, "lxc ls" gives the same error and the messages that I have sent.
I hope I am clear...
 
1) Does the failure happen when you start with a fresh lxd instance?
2) If the answer to 1) is "no", is there are repeatable process that you
  have that brings you from a fresh lxd instance to the point were it
  crashes with the failure you pasted?
3) Regardless of the answers to 1) and 2), does the failure happen
  consistently? I.e. does it happen every time you run "lxc ls".
Free
Post by Pierre Couderc
commit f160665d9e50e39d156591546732a2e0b3712f73
Date:   Mon Aug 20 19:04:10 2018 +0200
Mmm, I can send you again my tarball but it will be the same as I did send you before...
 It seems th eproblem is linked with my computer... Maybe I could enavle some traces on my computer ?
 
  Hello,
this seems the same failure you reported earlier (thread with subject
"lxd refuses to start ...").
When you sent me the database tarball last time, I didn't see any issue
and I could not reproduce the failure. Can you please double check that
your version of the dqlite C library is up to date (tag v0.2.2) and the
go-dqlite git close under GOPATH actually points to the master version
on github? Just run "git status" under $GOPATH/github.com/CanonicalLtd/go-dqlite
and compare it with github.
If all your dependencies turn out to be up-to-date, you may want to
again send me a tarball of your /var/lib/lxd/database directory, and
I'll double check too.
Free
Post by Pierre Couderc
Currently I heve many instabilities with lxd.
The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users  
Pierre Couderc
2018-08-30 15:38:44 UTC
Permalink
- About the problem "Instabiltie", I have found a mistake of mine that maybe may  explain : I had another release of lxd (dated 12 august) on the same computer, and I may  have started it by mistake ans this could explin the "instabilities". So let us wait and now that I have cleared the old release


Le jeudi 30 août 2018 à 17:17:00 UTC+2, Free Ekanayaka <***@canonical.com> a écrit :

It's not the "good one". You need to build it from source from:

github.com/CanonicalLtd/sqlite

or there debs here:

https://launchpad.net/~dqlite-maintainers/+archive/ubuntu/master
Post by Pierre Couderc
Maybe it is linked or not.
On another computer, I try to compile on stretch, but I cannot install liblixc-dev (does not iexist une stretch).
  CCLD     libdqlite.la
/usr/bin/ld: cannot find -lsqlite3
collect2: error: ld returned 1 exit status
Makefile:812: recipe for target 'libdqlite.la' failed
make[2]: *** [libdqlite.la] Error 1
make[2]: Leaving directory '/root/go/deps/dqlite'
Makefile:697: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/root/go/deps/dqlite'
Makefile:30: recipe for target 'deps' failed
make: *** [deps] Error 2
So I apt install libsqlite3_dev and then deps build.
But is it the "good" libsqlite3 ?
 
  Well, I prepare it and I send it you. First time I had removed the containers this time I let them. Please consider them as private data
 
  Hello,
yes, I believe I understand. What's puzzling is that I should be able to
reproduce your problem using database. Would you mind sending me again a
tarball of the /var/lib/lxd/database directory of a LXD which is
currently broken? Just to double check. I don't have any other idea atm.
Post by Pierre Couderc
When I start a new clean lxd instance, I can lxd init, launch first.
Then I try to work, it works, I success import from other lxd.
At some point, some lxc command fails, such as lxc copy (local).
Then nothing works more, any lxc command get soxket error.
If I reboot, "lxc ls" gives the same error and the messages that I have sent.
I hope I am clear...
 
1) Does the failure happen when you start with a fresh lxd instance?
2) If the answer to 1) is "no", is there are repeatable process that you
  have that brings you from a fresh lxd instance to the point were it
  crashes with the failure you pasted?
3) Regardless of the answers to 1) and 2), does the failure happen
  consistently? I.e. does it happen every time you run "lxc ls".
Free
Post by Pierre Couderc
commit f160665d9e50e39d156591546732a2e0b3712f73
Date:   Mon Aug 20 19:04:10 2018 +0200
Mmm, I can send you again my tarball but it will be the same as I did send you before...
 It seems th eproblem is linked with my computer... Maybe I could enavle some traces on my computer ?
 
  Hello,
this seems the same failure you reported earlier (thread with subject
"lxd refuses to start ...").
When you sent me the database tarball last time, I didn't see any issue
and I could not reproduce the failure. Can you please double check that
your version of the dqlite C library is up to date (tag v0.2.2) and the
go-dqlite git close under GOPATH actually points to the master version
on github? Just run "git status" under $GOPATH/github.com/CanonicalLtd/go-dqlite
and compare it with github.
If all your dependencies turn out to be up-to-date, you may want to
again send me a tarball of your /var/lib/lxd/database directory, and
I'll double check too.
Free
Post by Pierre Couderc
Currently I heve many instabilities with lxd.
The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users     
Pierre Couderc
2018-08-30 19:00:37 UTC
Permalink
Post by Pierre Couderc
- About the problem "Instabiltie", I have found a mistake of mine that
maybe may  explain : I had another release of lxd (dated 12 august) on
the same computer, and I may  have started it by mistake ans this
could explin the "instabilities". So let us wait and now that I have
cleared the old release
The problem has come back. I try :

 lxd import debian
Error: Post http://unix.socket/internal/containers: EOF

and then I can no more "lxc ls" (it loops)...

May it be that by mistake I did key "lxc import debian" before "lxd
import debian" ?

But all my containers are active while I do not reboot.

Pierre Couderc
2018-08-30 15:52:18 UTC
Permalink
But I have built following the instructions of "Installing LXD from source" from github.com/lxc/lxd/The only point is that I did not find liblxc-dev in stretch repository. Le jeudi 30 août 2018 à 17:17:00 UTC+2, Free Ekanayaka <***@canonical.com> a écrit :

It's not the "good one". You need to build it from source from:

github.com/CanonicalLtd/sqlite

or there debs here:

https://launchpad.net/~dqlite-maintainers/+archive/ubuntu/master
Post by Pierre Couderc
Maybe it is linked or not.
On another computer, I try to compile on stretch, but I cannot install liblixc-dev (does not iexist une stretch).
  CCLD     libdqlite.la
/usr/bin/ld: cannot find -lsqlite3
collect2: error: ld returned 1 exit status
Makefile:812: recipe for target 'libdqlite.la' failed
make[2]: *** [libdqlite.la] Error 1
make[2]: Leaving directory '/root/go/deps/dqlite'
Makefile:697: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/root/go/deps/dqlite'
Makefile:30: recipe for target 'deps' failed
make: *** [deps] Error 2
So I apt install libsqlite3_dev and then deps build.
But is it the "good" libsqlite3 ?
 
  Well, I prepare it and I send it you. First time I had removed the containers this time I let them. Please consider them as private data
 
  Hello,
yes, I believe I understand. What's puzzling is that I should be able to
reproduce your problem using database. Would you mind sending me again a
tarball of the /var/lib/lxd/database directory of a LXD which is
currently broken? Just to double check. I don't have any other idea atm.
Post by Pierre Couderc
When I start a new clean lxd instance, I can lxd init, launch first.
Then I try to work, it works, I success import from other lxd.
At some point, some lxc command fails, such as lxc copy (local).
Then nothing works more, any lxc command get soxket error.
If I reboot, "lxc ls" gives the same error and the messages that I have sent.
I hope I am clear...
 
1) Does the failure happen when you start with a fresh lxd instance?
2) If the answer to 1) is "no", is there are repeatable process that you
  have that brings you from a fresh lxd instance to the point were it
  crashes with the failure you pasted?
3) Regardless of the answers to 1) and 2), does the failure happen
  consistently? I.e. does it happen every time you run "lxc ls".
Free
Post by Pierre Couderc
commit f160665d9e50e39d156591546732a2e0b3712f73
Date:   Mon Aug 20 19:04:10 2018 +0200
Mmm, I can send you again my tarball but it will be the same as I did send you before...
 It seems th eproblem is linked with my computer... Maybe I could enavle some traces on my computer ?
 
  Hello,
this seems the same failure you reported earlier (thread with subject
"lxd refuses to start ...").
When you sent me the database tarball last time, I didn't see any issue
and I could not reproduce the failure. Can you please double check that
your version of the dqlite C library is up to date (tag v0.2.2) and the
go-dqlite git close under GOPATH actually points to the master version
on github? Just run "git status" under $GOPATH/github.com/CanonicalLtd/go-dqlite
and compare it with github.
If all your dependencies turn out to be up-to-date, you may want to
again send me a tarball of your /var/lib/lxd/database directory, and
I'll double check too.
Free
Post by Pierre Couderc
Currently I heve many instabilities with lxd.
The only way I have found is to renitialze and import every container, and only when it wants....
Thank you for any help
PC
_______________________________________________
lxc-users mailing list
http://lists.linuxcontainers.org/listinfo/lxc-users     
Loading...