<div dir="ltr">On Mon, Feb 29, 2016 at 5:35 PM, Serge E. Hallyn <span dir="ltr"><<a href="mailto:serge@hallyn.com" target="_blank">serge@hallyn.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Casey,<br>
<br>
I haven't reproduced that here in VMs. If you can reproduce this at will (by<br>
rebooting the host) could you file a bug against the kernel (<a href="http://pad.lv/u/linux" rel="noreferrer" target="_blank">pad.lv/u/linux</a>) ?<br></blockquote><div><br></div><div>Saw it again after booting up my laptop this morning, opened a bug:<br><br><a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551854">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551854</a><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
thanks,<br>
-serge<br>
<span class=""><br>
Quoting Casey Marshall (<a href="mailto:casey.marshall@canonical.com">casey.marshall@canonical.com</a>):<br>
> On Mon, Feb 29, 2016 at 4:57 PM, Tom Barber <<a href="mailto:tom@analytical-labs.com">tom@analytical-labs.com</a>> wrote:<br>
><br>
> > Seemingly the image name and key are the same, LXD and Juju are the same,<br>
> > so you've either done something magic or I'm confused with its now seeming<br>
> > happiness of the kernel debug mountpoint! :)<br>
> ><br>
><br>
> I ran into a similar issue today. xenial host, running latest juju out of<br>
> master for LXD API compatibility. I was unable to bootstrap and sshd was<br>
> not starting in the controller instance.<br>
><br>
> Remounted kernel debug on the host, and bootstrap started working, sshd<br>
> starting up now in my trusty instances.<br>
><br>
> Did not refresh my images. If it happens after rebooting the host, I'll try<br>
> to collect more info.<br>
><br>
> -Casey<br>
><br>
><br>
> > --------------<br>
> ><br>
> > Director Meteorite.bi - Saiku Analytics Founder<br>
> > Tel: <a href="tel:%2B44%280%295603641316" value="+445603641316">+44(0)5603641316</a><br>
> ><br>
> > (Thanks to the Saiku community we reached our Kickstart<br>
</span>> > <<a href="http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/" rel="noreferrer" target="_blank">http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/</a>><br>
<span class="">> > goal, but you can always help by sponsoring the project<br>
</span>> > <<a href="http://www.meteorite.bi/products/saiku/sponsorship" rel="noreferrer" target="_blank">http://www.meteorite.bi/products/saiku/sponsorship</a>>)<br>
<div><div class="h5">> ><br>
> > On 29 February 2016 at 22:43, Tom Barber <<a href="mailto:tom@analytical-labs.com">tom@analytical-labs.com</a>> wrote:<br>
> ><br>
> >> Hi Serge<br>
> >><br>
> >> Fresh reboot and updated image, image boots with SSHD working fine, so<br>
> >> whatever you did, i assume worked or is a freak occurrence. I don't have<br>
> >> any old images kicking around and the import I copied from your email<br>
> >> appears to have stomped on the old image.<br>
> >><br>
> >> FYI<br>
> >><br>
> >> bugg@tomsdevbox:~$ lxc config show t1<br>
> >> name: t1<br>
> >> profiles:<br>
> >> - default<br>
> >> config:<br>
> >> volatile.base_image:<br>
> >> 510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a<br>
> >> volatile.eth0.hwaddr: 00:16:3e:94:d5:66<br>
> >> volatile.last_state.idmap:<br>
> >> '[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'<br>
> >> volatile.lo.hwaddr: 00:16:3e:d2:98:62<br>
> >> devices:<br>
> >> root:<br>
> >> path: /<br>
> >> type: disk<br>
> >> ephemeral: false<br>
> >><br>
> >><br>
> >> juju bootstrap now seems to run fine without remounting the kernel debug.<br>
> >><br>
> >> Thanks for your help!<br>
> >><br>
> >> Tom<br>
> >><br>
> >><br>
> >> --------------<br>
> >><br>
> >> Director Meteorite.bi - Saiku Analytics Founder<br>
> >> Tel: +44(0)5603641316<br>
> >><br>
> >> (Thanks to the Saiku community we reached our Kickstart<br>
</div></div>> >> <<a href="http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/" rel="noreferrer" target="_blank">http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/</a>><br>
<span class="">> >> goal, but you can always help by sponsoring the project<br>
</span>> >> <<a href="http://www.meteorite.bi/products/saiku/sponsorship" rel="noreferrer" target="_blank">http://www.meteorite.bi/products/saiku/sponsorship</a>>)<br>
<div class=""><div class="h5">> >><br>
> >> On 29 February 2016 at 21:45, Serge E. Hallyn <<a href="mailto:serge@hallyn.com">serge@hallyn.com</a>> wrote:<br>
> >><br>
> >>> On Mon, Feb 29, 2016 at 09:45:14AM +0000, Tom Barber wrote:<br>
> >>> > Hi Serge<br>
> >>> ><br>
> >>> > I rebooted the host to see what happened and the lxc images that were<br>
> >>> > running fine all now have broken SSHD. This, to make absolutely clear<br>
> >>> > doesn't affect the Xenial image, just the trusty one I test with.<br>
> >>> ><br>
> >>> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2<br>
> >>> > Creating fix-server2<br>
> >>> > Starting fix-server2<br>
> >>> ><br>
> >>> > bugg@tomsdevbox:~$ lxc exec fix-server2 /bin/bash<br>
> >>> > root@fix-server2:~# ps aux |grep ssh<br>
> >>> > root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00 grep<br>
> >>> > --color=auto ssh<br>
> >>> ><br>
> >>> > exit<br>
> >>> ><br>
> >>> > umount and remount kernel debug....<br>
> >>> ><br>
> >>> > bugg@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3<br>
> >>> > Creating fix-server3<br>
> >>> > Starting fix-server3<br>
> >>> > bugg@tomsdevbox:~$ lxc exec fix-server3 /bin/bash<br>
> >>> > root@fix-server3:~# ps aux |grep ssh<br>
> >>> > root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00<br>
> >>> > /usr/sbin/sshd -D<br>
> >>> > root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00 grep<br>
> >>> > --color=auto ssh<br>
> >>><br>
> >>> If you pull a fresh image using<br>
> >>><br>
> >>> lxd-images import ubuntu --alias newtrusty trusty amd64<br>
> >>><br>
> >>> and launch that<br>
> >>><br>
> >>> lxc launch newtrusty t1<br>
> >>><br>
> >>> does it have the same failure?<br>
> >>><br>
> >>> What does<br>
> >>><br>
> >>> lxc config show fix-server2 show?<br>
> >>><br>
> >><br>
> >><br>
> ><br>
> > --<br>
> > Juju mailing list<br>
> > <a href="mailto:Juju@lists.ubuntu.com">Juju@lists.ubuntu.com</a><br>
> > Modify settings or unsubscribe at:<br>
> > <a href="https://lists.ubuntu.com/mailman/listinfo/juju" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju</a><br>
> ><br>
> ><br>
</div></div></blockquote></div><br></div></div>