Heureka, I resolved the problem. My own question eventually led me 
there, (and reading the f*ing manual helped, as usually ;-) ). I would 
not have managed if I hadn't asked the question at this list. Thanks!

First observation:
------------------
Yes, as Peter confirmed, the entries in /etc/inetd.conf referring to nbd 
exports (i.e., nbdrootd on port 2000, nbdswapd on port 9572) are 
obsolete since nbd-server switched to the name based protocol. They are 
now managed by nbd-server.conf files in /ect/nbd-server/conf.d/.

If you have these entries in /etc/inedtd.conf left over from former 
versions of LTSP, you may safely remove them. They do no harm if you 
leave them, either.

However, do *not* remove the entry refering to ldminfod on port 9571, it 
is still used for thin clients!

Second observation:
-------------------
Between 12.04 and 13.04, the names that LTSP uses for NBD exports have 
changed. That's what caused our boot problem.

Note: If you use the standard ltsp setup, you will not be concerned by 
this change, everyhing will work as expected, and you can stop reading here.

For those interested in the internals:

I thought that during negotiation, the client asks for the file name of 
the nbd image he wants exported. But that's not true, its actually the 
name of the config section in the nbd-server.conf file it asks for!

This name has changed between 12.04 and 13.04:
In 12.04, /etc/nbd-server/conf.d/ltsp_i386.conf looked like this:

---
[ltsp_i386]
exportname = /opt/ltsp/images/i386.img
readonly = true
---

In 13.04, it looks like this:
---
[/opt/ltsp/i386]
exportname = /opt/ltsp/images/i386.img
readonly = true
authfile = /etc/ltsp/nbd-server.allow
---

The file name of the image is the same, but the section name has changed 
(the string between square brackets). It used to be "ltsp_i386" and now 
reads "/opt/ltsp/i386".

At our site, we have hand-tuned the PXE boot process, so that every 
client displays a PXE boot menu at startup, allowing the user to select 
what server to boot from. (We use seven LTSP-servers, one Rembo-Server 
and one Linbo-Server that all serve their images via PXE.)
In order to manually boot from a distinct LTSP server, we needed to 
specify the PXE option "nbdroot", which refers to the name of the 
export. And boom! This name has silently changed between releases.

It would be easy to track down if the nbd-server had printed out a 
proper error message (like "image not found"). Instead, the client 
complained about the image being too big, which is plain wrong. There 
was no image served. I'd speculate that the server actually sent an 
error message, which the client interpreted as the image size. The world 
of server protocols is dark and mysterious.

One thing I learned, again: Praise good error messages, and praise good 
documentation...

Regards,
Rüdiger


Am 01.07.2013 18:12, schrieb Peter D Knight:
> I took my entry out as well.
> Peter
>
>
> On Mon, Jul 1, 2013 at 12:43 PM, Rüdiger Kupper <k...@kg-fds.de
> <mailto:k...@kg-fds.de>> wrote:
>
>     Hello Ben!
>
>     The server log reads:
>
>     Jul  1 11:23:09 ltsp6 nbd_server[5300]: negotiation failed
>     Jul  1 11:23:09 ltsp6 nbd_server[5300]: Exiting.
>
>     My config files look exactly as yours do.
>
>     Question: this means that the nbd-server uses the name-based protocol,
>     right? There still is en entry in /etc/inetd.conf:
>
>     2000               stream  tcp nowait  nobody /usr/sbin/tcpd
>     /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
>
>     I believe this is not needed any more, right?
>
>     Thanks for further ideas,
>     Rüdiger
>
>
>     Am 01.07.2013 11:14, schrieb Ben Green:
>      > Quoting Rüdiger Kupper <k...@kg-fds.de <mailto:k...@kg-fds.de>>:
>      >
>      >> Hi Peter,
>      >> thanks for the idea.
>      >>
>      >> You mean some unmounted device in the chroot has been packed
>     into the
>      >> BSD image? No, the BSD image is actually quite moderate, it has
>     505M:
>      >>
>      >
>      > I've had this problem, its was the nbd-server having an incorrect
>      > configuration. Check your server logs and see what happens when the
>      > client tries to connect.
>      >
>      >       For /etc/nbd-server I have:
>      >
>      > [generic]
>      > # If you want to run everything as root rather than the nbd user, you
>      > # may either say "root" in the two following lines, or remove them
>      > # altogether. Do not remove the [generic] section, however.
>      >           user = nbd
>      >           group = nbd
>      >           includedir = /etc/nbd-server/conf.d
>      >
>      > # What follows are export definitions. You may create as much of
>     them as
>      > # you want, but the section header has to be unique.
>      >
>      >      and for /etc/nbd-server/conf.d/ltsp_i386.conf:
>      >
>      > [/opt/ltsp/i386]
>      > exportname = /opt/ltsp/images/i386.img
>      > readonly = true
>      >
>      >
>      > How about you?
>      >
>      > Cheers,
>      > Ben
>      >
>      >
>      >
>      >
>     
> ------------------------------------------------------------------------------
>      > This SF.net email is sponsored by Windows:
>      >
>      > Build for Windows Store.
>      >
>      > http://p.sf.net/sfu/windows-dev2dev
>      > _____________________________________________________________________
>      > 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
>     <http://irc.freenode.net>
>      >
>
>
>     --
>     StR Dr. R. Kupper
>     Kepler-Gymnasium Freudenstadt
>
>     
> ------------------------------------------------------------------------------
>     This SF.net email is sponsored by Windows:
>
>     Build for Windows Store.
>
>     http://p.sf.net/sfu/windows-dev2dev
>     _____________________________________________________________________
>     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
>     <http://irc.freenode.net>
>
>
>
>
> --
> Peter D Knight
> 22 Westfort Rd
> Houtbay
> 7806
> +27(21)7903579
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
>
>
>
> _____________________________________________________________________
> 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
>


-- 
StR Dr. R. Kupper
Kepler-Gymnasium Freudenstadt

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_____________________________________________________________________
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

Reply via email to