Tada! Works now, thanks a lot!
# systemctl status snap.lxd.daemon
● snap.lxd.daemon.service - Service for snap application lxd.daemon
Loaded: loaded (/etc/systemd/system/snap.lxd.daemon.service; enabled;
vendor preset: enabled)
Active: active (running) since Mon 2018-05-07 14:45:31 CEST; 2min 35s
ago
Process: 39652 ExecStop=/usr/bin/snap run --command=stop lxd.daemon
(code=exited, status=0/SUCCESS)
Main PID: 39893 (daemon.start)
CGroup: /system.slice/snap.lxd.daemon.service
‣ 39893 /bin/sh /snap/lxd/6954/commands/daemon.start
May 07 14:45:33 lxd05 lxd.daemon[3336]: 5: fd: 13: pids
May 07 14:45:33 lxd05 lxd.daemon[3336]: 6: fd: 14: devices
May 07 14:45:33 lxd05 lxd.daemon[3336]: 7: fd: 15: cpuset
May 07 14:45:33 lxd05 lxd.daemon[3336]: 8: fd: 16: blkio
May 07 14:45:33 lxd05 lxd.daemon[3336]: 9: fd: 17: cpu,cpuacct
May 07 14:45:33 lxd05 lxd.daemon[3336]: 10: fd: 18: freezer
May 07 14:45:33 lxd05 lxd.daemon[3336]: 11: fd: 19: name=systemd
May 07 14:45:33 lxd05 lxd.daemon[3336]: lxcfs.c: 105: do_reload: lxcfs:
reloaded
May 07 14:45:35 lxd05 lxd.daemon[39893]: => LXD is ready
May 07 14:46:55 lxd05 lxd.daemon[39893]: lvl=warn msg="Detected
poll(POLLNVAL) event." t=2018-05-07T12:46:55+0000
Tomasz
On 2018-05-07 20:56, Free Ekanayaka wrote:
Hello,
I set a tarball of the repaired database to Tomasz privately.
I simply deleted the last raft log entry which was broken, although
there was not enough information to understand what caused the issue.
There have been several fixes in dqlite in that area (rollback of
failed
transactions), so hopefully this won't happen again with LXD 3.1.0.
Free
Free Ekanayaka <[email protected]> writes:
Hello,
yes, I received it. I'm going to get through in the next few hours and
get back to you.
Cheers
Tomasz Chmielewski <[email protected]> writes:
On 2018-05-06 18:02, Tomasz Chmielewski wrote:
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.
Could you confirm if you've received the archive?
It would be great to know if it's possible to make LXD run again, or
if
it crashed for good and I have to recreate the containers somehow.
Tomasz Chmielewski
https://lxadm.com
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users
