Debian Bug report logs - #519325
Error "NFS over TCP not available from ..."

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Gustavo Lima <gustavopml@gmail.com>

To: submit@bugs.debian.org

Subject: Error "NFS over TCP not available from ..."

Date: Wed, 11 Mar 2009 18:29:32 -0300

Package: ltsp-server
Version: 5.1.10-2
Severity: normal

--- Please enter the report below this line. ---

1. Xen dom0 running on lenny amd64 with 12 vlan interfaces
2. domU running lenny amd64 with 12 network interfaces, bridged on those
vlans, running dhcp server on almost all networks
3. On the same domU where dhcp is running I installed
ltsp-server-standalone
4. My dhcpd.conf for the network where the ltsp-clients are running is:

subnet 10.1.20.0 netmask 255.255.255.0 {
        authoritative;
        range                           10.1.20.11 10.1.20.254;
        use-host-decl-names             on;
        option routers                  10.1.20.1;
        option domain-name-servers      10.1.20.57, 10.1.20.58;
        option domain-name              "domain.com";
        option netbios-name-servers     10.1.20.47, 10.1.20.24;
        next-server                     10.1.20.2;
        option root-path                "10.1.20.2:/opt/ltsp/i386";
        if substring (option vendor-class-identifier, 0, 9) =
"PXEClient" {
                filename "/ltsp/i386/pxelinux.0";
        } else {
                filename "/ltsp/i386/nbi.img";
        }

host ws0020 {
    hardware ethernet    00:50:04:E3:A9:D5;
    fixed-address        10.1.20.6;
    filename             "ltsp/i386/nbi.img";
}

5. I ran ltsp-build-client with the following sintaxe: 

ltsp-build-client --arch i386

I followed the steps on http://wiki.debian.org/LTSP/Howto but didn't
found /etc/lts.conf and /etc/default/ltsp-client-setup on the system
nether the docs at /usr/share/doc/ltsp-client*. Am I suposed to install
any other packages like ltsp-client? I don't believe so as the
disclaimer at the package description tells me not to do so.

My dhcp is running fine and tftp server either.

I boot my client and it gets the IP address, loads de image and right
after that starts a loop message "NFS over TCP not available from
10.1.20.2" until it stops giving me 3 mount error messages when trying
to mount /dev, /sys, /proc and at last "No init found. Try passing init=
bootarg."

Looking at ltsp_nbd I found declarations to /scripts/nfs-top but it is not in /scripts/.
I believe this a severe bug or the tutorials are not complete about the packages that are
needed for this installation to work.

--- System information. ---
Architecture: amd64
Kernel:       Linux 2.6.26-1-xen-amd64

Debian Release: lenny

Message #10 received at 519325@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: Gustavo Lima <gustavopml@gmail.com>, 519325@bugs.debian.org

Subject: Re: Bug#519325: Error "NFS over TCP not available from ..."

Date: Wed, 11 Mar 2009 16:20:33 -0700

thanks for the bug report!

On Wed, Mar 11, 2009 at 06:29:32PM -0300, Gustavo Lima wrote:
> 1. Xen dom0 running on lenny amd64 with 12 vlan interfaces
> 2. domU running lenny amd64 with 12 network interfaces, bridged on those
> vlans, running dhcp server on almost all networks
> 3. On the same domU where dhcp is running I installed
> ltsp-server-standalone

most of my real LTSP installs run from xen domU servers as well... though not
with quite so many vlans...

> 4. My dhcpd.conf for the network where the ltsp-clients are running is:
> 
> subnet 10.1.20.0 netmask 255.255.255.0 {
>         authoritative;
>         range                           10.1.20.11 10.1.20.254;
>         use-host-decl-names             on;
>         option routers                  10.1.20.1;
>         option domain-name-servers      10.1.20.57, 10.1.20.58;
>         option domain-name              "domain.com";
>         option netbios-name-servers     10.1.20.47, 10.1.20.24;
>         next-server                     10.1.20.2;
>         option root-path                "10.1.20.2:/opt/ltsp/i386";
>         if substring (option vendor-class-identifier, 0, 9) =
> "PXEClient" {
>                 filename "/ltsp/i386/pxelinux.0";
>         } else {
>                 filename "/ltsp/i386/nbi.img";
>         }
> 
> host ws0020 {
>     hardware ethernet    00:50:04:E3:A9:D5;
>     fixed-address        10.1.20.6;
>     filename             "ltsp/i386/nbi.img";
> }
> 
> 5. I ran ltsp-build-client with the following sintaxe: 
> 
> ltsp-build-client --arch i386

> I followed the steps on http://wiki.debian.org/LTSP/Howto 

4. Configure /etc/exports:

/opt/ltsp *(ro,no_root_squash,async,no_subtree_check)

is that what you have in /etc/exports ?

> but didn't found /etc/lts.conf and /etc/default/ltsp-client-setup on the
> system nether the docs at /usr/share/doc/ltsp-client*. Am I suposed to
> install any other packages like ltsp-client? I don't believe so as the
> disclaimer at the package description tells me not to do so.

correct, ltsp-client should only be installed in the chroot
(/opt/ltsp/i386), not on the server itself. the files you mentioned
should be in /opt/ltsp/i386/etc/lts.conf and
/opt/ltsp/i386/etc/default/ltsp-client-setup.  i updated the wiki page
to make this more clear.  but your boot hasn't even gotten far enough to
read those files yet. 
 
> My dhcp is running fine and tftp server either.

DHCP, TFTP and NFS server are all on the same machine? they're all reachable as
10.1.20.2?

> I boot my client and it gets the IP address, loads de image and right
> after that starts a loop message "NFS over TCP not available from
> 10.1.20.2" until it stops giving me 3 mount error messages when trying
> to mount /dev, /sys, /proc and at last "No init found. Try passing init=
> bootarg."

what is in the file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default?
it should contain a "boot=nfs" parameter.


does /opt/ltsp/i386 exist on the NFS server?

can you sucessfully:

  mount 10.1.20.2:/opt/ltsp/i386 /mnt 

from the server itself? from another machine on the 10.1.20.* network?

do you have a firewall running on the server that may be blocking NFS traffic?

what's the results of:

  dpkg -l nfs-kernel-server

if it's installed, did you try restarting nfs-kernel-server:

  invoke-rc.d nfs-kernel-server restart

or do you have a different nfs server installed?


live well,
  vagrant

Message #15 received at 519325@bugs.debian.org (full text, mbox, reply):

From: "Oded Naveh" <skilinux@gmail.com>

To: <519325@bugs.debian.org>, "'Gustavo Lima'" <gustavopml@gmail.com>

Subject: Re: Bug#519325: Error "NFS over TCP not available from ..."

Date: Fri, 13 Mar 2009 13:36:41 +0200

[Vagrant Cascadian] 
> what is in the file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default?
> it should contain a "boot=nfs" parameter.

At 5.1.10-2 the boot=nfs is missing from BOOTPROMPT_OPTS.

Hi Gustavo,
	The messages you quoted are slightly different from those I received, but I still think it's the same issue. 
Instructions for working around this provided by Vagrant Cascadian and
verified:

  # step 1: ensure boot=nfs in BOOTPROMPT_OPTS
  # for example: BOOTPROMPT_OPTS="quiet splash boot=nfs"
  $EDITOR /opt/ltsp/i386/etc/ltsp/update-kernels.conf

  # step 2: run update-kernels script in the chroot
  chroot /opt/ltsp/i386 /usr/share/ltsp/update-kernels

  # step 3: run ltsp-update-kernels on the server
  ltsp-update-kernels

see: <http://lists.debian.org/debian-edu/2008/11/msg00069.html>


Hi Vagrant,
	I found this bug report while doing a follow-up for:
http://bugs.skolelinux.no/cgi-bin/bugzilla/show_bug.cgi?id=1320

In http://lists.debian.org/debian-edu/2008/11/msg00072.html
You wrote:
"i probably should've patched the default in the packages directly ... *sigh*"
Have you patched it in Sid? :)
I could find no trace of it in the Changelog.

live well too, Odd.

Message #20 received at 519325@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: Oded Naveh <skilinux@gmail.com>, 519325@bugs.debian.org

Cc: 'Gustavo Lima' <gustavopml@gmail.com>

Subject: Re: [Pkg-ltsp-devel] Bug#519325: Error "NFS over TCP not available from ..."

Date: Fri, 13 Mar 2009 07:45:19 -0700

On Fri, Mar 13, 2009 at 01:36:41PM +0200, Oded Naveh wrote:
> [Vagrant Cascadian] 
> > what is in the file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default?
> > it should contain a "boot=nfs" parameter.
> 
> At 5.1.10-2 the boot=nfs is missing from BOOTPROMPT_OPTS.
> 
> Hi Gustavo,
> 	The messages you quoted are slightly different from those I received, but I still think it's the same issue. 
> Instructions for working around this provided by Vagrant Cascadian and
> verified:
> 
>   # step 1: ensure boot=nfs in BOOTPROMPT_OPTS
>   # for example: BOOTPROMPT_OPTS="quiet splash boot=nfs"
>   $EDITOR /opt/ltsp/i386/etc/ltsp/update-kernels.conf
> 
>   # step 2: run update-kernels script in the chroot
>   chroot /opt/ltsp/i386 /usr/share/ltsp/update-kernels
> 
>   # step 3: run ltsp-update-kernels on the server
>   ltsp-update-kernels
> 
> see: <http://lists.debian.org/debian-edu/2008/11/msg00069.html>

BOOTPROMPT_OPTS is not needed in lenny or sid by default- it is because
debian-edu sets BOOTPROMPT_OPTS that it was necessary to set in
debian-edu installs.

> Hi Vagrant,
> 	I found this bug report while doing a follow-up for:
> http://bugs.skolelinux.no/cgi-bin/bugzilla/show_bug.cgi?id=1320
> 
> In http://lists.debian.org/debian-edu/2008/11/msg00072.html
> You wrote:
> "i probably should've patched the default in the packages directly ... *sigh*"
> Have you patched it in Sid? :)
> I could find no trace of it in the Changelog.

i haven't patched the file that would make it unnecessary to set "boot=nfs" in
the bootloader.  will add it to the next upload.

though i don't think this is really the bug Gustavo encountered- it
sounded like it was *trying* to mount NFS and failing, rather that
trying to mount using NBD.

live well,
  vagrant

Message #25 received at 519325@bugs.debian.org (full text, mbox, reply):

From: "Oded Naveh" <skilinux@gmail.com>

To: "'Vagrant Cascadian'" <vagrant@freegeek.org>, <519325@bugs.debian.org>

Subject: RE: [Pkg-ltsp-devel] Bug#519325: Error "NFS over TCP not available from ..."

Date: Fri, 13 Mar 2009 17:20:40 +0200

My apology Vagrant,
Turns out I was too hasten.

Gustavo has replied to me, saying:
> It turned 
> to be some odd problem with the modules at /lib that were not 
> upgraded with the new kernel after I apt-get dist-upgrade the 
> old etch installation.
> 
> Made a fresh install of lenny and everything ran smoothly.

So I guess you can close this bug.

Vagrant Cascadian: Friday, March 13, 2009 4:45 PM
> BOOTPROMPT_OPTS is not needed in lenny or sid by default- it 
> is because debian-edu sets BOOTPROMPT_OPTS that it was 
> necessary to set in debian-edu installs.
	I see you've changed the bits in debian-edu-config.

> > Have you patched it in Sid? :)
> > I could find no trace of it in the Changelog.
> 
> i haven't patched the file that would make it unnecessary to 
> set "boot=nfs" in the bootloader.  will add it to the next upload.
	I'll run debian-edu installation to test it and report on the
mailing list. Hope to report issue solved.

Best regards, Odd.

Message #30 received at 519325@bugs.debian.org (full text, mbox, reply):

From: Gustavo Lima <gustavopml@gmail.com>

To: 519325@bugs.debian.org

Subject: Re: [Pkg-ltsp-devel] Bug#519325: Error "NFS over TCP not available from ..."

Date: Fri, 13 Mar 2009 12:26:42 -0300

[Message part 1 (text/plain, inline)]

Oded and Vagrant,

Thank you for all the help and usefull information.

It turned out to be some odd problem with the modules at /lib that were not
upgraded with the new kernel after I apt-get dist-upgrade the old etch
installation. So it had an influence on NFS.

Made a fresh install of lenny and everything ran smoothly.

My best regards and have a great weekend.

Gustavo

2009/3/13 Vagrant Cascadian <vagrant@freegeek.org>

> On Fri, Mar 13, 2009 at 01:36:41PM +0200, Oded Naveh wrote:
> > [Vagrant Cascadian]
> > > what is in the file /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default?
> > > it should contain a "boot=nfs" parameter.
> >
> > At 5.1.10-2 the boot=nfs is missing from BOOTPROMPT_OPTS.
> >
> > Hi Gustavo,
> >       The messages you quoted are slightly different from those I
> received, but I still think it's the same issue.
> > Instructions for working around this provided by Vagrant Cascadian and
> > verified:
> >
> >   # step 1: ensure boot=nfs in BOOTPROMPT_OPTS
> >   # for example: BOOTPROMPT_OPTS="quiet splash boot=nfs"
> >   $EDITOR /opt/ltsp/i386/etc/ltsp/update-kernels.conf
> >
> >   # step 2: run update-kernels script in the chroot
> >   chroot /opt/ltsp/i386 /usr/share/ltsp/update-kernels
> >
> >   # step 3: run ltsp-update-kernels on the server
> >   ltsp-update-kernels
> >
> > see: <http://lists.debian.org/debian-edu/2008/11/msg00069.html>
>
> BOOTPROMPT_OPTS is not needed in lenny or sid by default- it is because
> debian-edu sets BOOTPROMPT_OPTS that it was necessary to set in
> debian-edu installs.
>
> > Hi Vagrant,
> >       I found this bug report while doing a follow-up for:
> > http://bugs.skolelinux.no/cgi-bin/bugzilla/show_bug.cgi?id=1320
> >
> > In http://lists.debian.org/debian-edu/2008/11/msg00072.html
> > You wrote:
> > "i probably should've patched the default in the packages directly ...
> *sigh*"
> > Have you patched it in Sid? :)
> > I could find no trace of it in the Changelog.
>
> i haven't patched the file that would make it unnecessary to set "boot=nfs"
> in
> the bootloader.  will add it to the next upload.
>
> though i don't think this is really the bug Gustavo encountered- it
> sounded like it was *trying* to mount NFS and failing, rather that
> trying to mount using NBD.
>
> live well,
>   vagrant
>

[Message part 2 (text/html, inline)]

Message #37 received at 519325-done@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: 519325-done@bugs.debian.org

Subject: Re: Bug#519325: Error "NFS over TCP not available from ..."

Date: Fri, 13 Mar 2009 09:22:52 -0700

notfound 519325 5.1.10-2
thanks

Version: 5.1.10-2

On Fri, Mar 13, 2009 at 12:26:42PM -0300, Gustavo Lima wrote:
> It turned out to be some odd problem with the modules at /lib that were not
> upgraded with the new kernel after I apt-get dist-upgrade the old etch
> installation. So it had an influence on NFS.
> 
> Made a fresh install of lenny and everything ran smoothly.

glad to hear it. closing this bug report.

> My best regards and have a great weekend.

you too.

live well,
  vagrant

Send a report that this bug log contains spam.