On 11/8/2013 1:42 PM, Jay Goldberg wrote:
On Fri, Nov 8, 2013 at 11:51 AM, John Hupp <l...@prpcompany.com
<mailto:l...@prpcompany.com>> wrote:
On 11/7/2013 4:23 PM, David Burgess wrote:
On Thu, Nov 7, 2013 at 1:18 PM, John Hupp <l...@prpcompany.com
<mailto:l...@prpcompany.com>> wrote:
On 11/6/2013 5:53 PM, John Hupp wrote:
> I finished a new installation of LTSP-PNP on Lubuntu 13.10,
but I find
> that clients won't boot.
>
> After the Plymouth splash screen, a text screen reads:
>
> Error: socket failed: connection refused.
> Exiting.
Forgive me for not combing through all of the machine output, but
at a glance your symptoms look like something I have encountered
where the nbd server does not start automatically on the server.
The quick fix was to start the service, and then I don't recall
if it started automatically after a reboot or if I had to turn
that on in a config file somewhere. Try 'netstat -lt' to see what
ports you're listening on.
db
Thanks for a good lead (though it leads to more questions rather
than an immediate solution).
I find that nbd-server is running, but comparing the output of
'netstat -lt' on a Lubuntu 13.04 LTSP server that works fine, and
the misbehaving 13.10 server, I find that on
13.04 nbd-server listens on *: 60603, but on 13.10 it listens on
*:nbd.
Otherwise the output is the same for tcp on both servers (I don't
list the tcp6 results):
tcp 0 0 *:9571 *:* LISTEN
tcp 0 0 localhost:55213 *:* LISTEN
tcp 0 0 Lubuntu:domain *:* LISTEN
tcp 0 0 192.168.1.117:domain *:*
LISTEN
tcp 0 0 localhost:domain *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 localhost:ipp *:* LISTEN
The nbd-server configuration file
(/etc/nbd-server/conf.d/ltsp_i386.conf) has the same contents on
both installations.
The script that launches nbd-server appears to be
/etc/init.d/nbd-server, and it does not specify ip addresses or
ports to listen to. At least for the ip addresses,
http://manpages.ubuntu.com/manpages/saucy/man1/nbd-server.1.html
states that when the ip address parameter is not specified,
nbd-server will listen on all local addresses on both IPv4 and IPv6.
I don't know how to interpret the difference in how nbd-server is
listening.
Forgive me if I seem out of the loop, I have not used LTSP in over a year
However, it does look like a port issue. Looking at my Debian system,
/etc/services reports that NBD is on port 10809
nbd 10809/tcp # Linux Network Block Device
And in the man page for nbd-server for the -port option:
The port on which to listen for new-style nbd-client
connections. If not specified, the IANA-assigned port of 10809
is used.
The netstat output will replace port numbers with friendly names if it
can match up ports with entries in /etc/services
I recall that LTSP does use its own NBD server on a non-standard port
with a config file in a non-standard location as well, so it would
seem that your 13.10 system should not show listening on *:nbd.
Check that the nbd-server is running on the port that the client
expects. "Connection refused" would support that the port the client
is connecting to is "closed".
For fun, also post the output of # iptables -L to make sure there are
no firewall rules filtering things.
Cheers,
--
Jay Goldberg | AvianBLUE Network Systems
I don't know how to check that the nbd-server is running on the port
that the client expects. Can you tell me?
But perhaps related to this, even though the topic was NBD Swap, Alkis
Georgopoulos wrote in
http://osdir.com/ml/LTSP-cluster-thin-clients/2012-08/msg00047.html that
for Ubuntu 12.04, the NBD_PORT section [for NBD Swap] is obsolete since
NBD is now using the IANA assigned port 10809 and name-based exports
instead of port-based.
------------------------------
Iptables -L shows the default, no-rules setup:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&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
