On 12/7/2013 9:43 PM, Vagrant Cascadian wrote:
> On Thu, Dec 05, 2013 at 11:31:46AM -0500, John Hupp wrote:
>> I'm still troubleshooting the problem in which (on *buntu 13.10) client
>> boot fails after the splash screen with 'Error: socket failed:
>> connection refused.'
> First hunch sounds like a firewalling problem, or running old-style nbd (each
> export gets a port, launched from inetd), vs. new-style nbd (uses port 10809,
> exports are named)... ltsp has been using new-style nbd since ltsp 5.3.x, I
> think.
>
>
>> My current working premise is that this is an nbd error.
>>
>> So I want to see the nbd-client command line and configuration in the
>> client initramfs. I'm assuming that loads from the initramfs /init
>> script, but 'cat /init' produces rather useless scrolls-by-in-a-flash
>> output, and the initramfs does not support 'cat /init | less.'
>>
>> Can I locate the init script somewhere on the server?
> Look in /opt/ltsp/<arch>/usr/share/initramfs-tools/ for all the code used to
> build the initramfs.
>
> You might want to put "set -x" near the top of
> ../initramfs-tools/local-top/nbd and maybe a "read pause" in there somewhere,
> and a few "echo $FOO" in there to help with debugging.
>
> Then rebuild the initramfs:
>
> sudo ltsp-chroot update-initramfs -u
>
> Update your tftp dirs:
>
> sudo ltsp-update-kernels
>
> And try and boot it again.
>
>
> live well,
> vagrant
Thanks, Vagrant, for the useful info about initramfs. But under *buntu,
is the location /opt/ltsp/<arch>/usr/share/initramfs-tools? I don't
find that under Ubuntu/Lubuntu Saucy.
I had been wondering about a possible old-style/new-style nbd conflict,
but as you may now read in the thread that was the source of this
question ("Clients fail to boot: 'Error: socket failed: connection
refused' (like bug 951526)"), I now think that this is a bug in
kernel-level nbd support. But I still need to sharpen up the details
before submitting it as a bug. You may review what I wrote in my last
post in that thread and see if you have any advice.
But here is one question about troubleshooting: As I was trying to
install kernels and test them on the client, I updated
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default (so the new kernel
would be available during client boot) via ltsp-update-image, which is a
slow process. I'm thinking that I probably don't need that big gun.
You mention ltsp-update-kernels above -- is that all I really need?
--John
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
