On Mon, Feb 29, 2016 at 09:45:14AM +0000, Tom Barber wrote: > Hi Serge > > I rebooted the host to see what happened and the lxc images that were > running fine all now have broken SSHD. This, to make absolutely clear > doesn't affect the Xenial image, just the trusty one I test with. > > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2 > Creating fix-server2 > Starting fix-server2 > > bugg@tomsdevbox:~$ lxc exec fix-server2 /bin/bash > root@fix-server2:~# ps aux |grep ssh > root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00 grep > --color=auto ssh > > exit > > umount and remount kernel debug.... > > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3 > Creating fix-server3 > Starting fix-server3 > bugg@tomsdevbox:~$ lxc exec fix-server3 /bin/bash > root@fix-server3:~# ps aux |grep ssh > root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00 > /usr/sbin/sshd -D > root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00 grep > --color=auto ssh
If you pull a fresh image using lxd-images import ubuntu --alias newtrusty trusty amd64 and launch that lxc launch newtrusty t1 does it have the same failure? What does lxc config show fix-server2 show? -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
