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.'
When I thought the problem was nbd-related, you suggested the following: > 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. > I'm trying to use that method in my latest attempts to locate the failure point. For my ltsp-pnp setup, I edited /usr/share/initramfs-tools/scripts/init-bottom/ltsp, adding "set -x" and "read pause" as the first commands in that script. But I'm tripping on the rebuild/update steps. "sudo ltsp-chroot update-initramfs -u" generated some sort of an error. Then I tried just "sudo ltsp-chroot -b /" and that generated "chroot: failed to run command '/bin/bash'" no such file or directory." I've also been trying to understand what difference there may be between ltsp-update-kernels (as above) and /usr/share/ltsp/update-kernels (as in the ltsp-pnp setup). ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&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
