NFS need path error
 

I have a new install of Feisty and the clients, different ones, all get
an error from NFS saying "need path". The path /opt/ltsp/i386 is in the
default DHCP server file, where I edited my IP range.

I did try Gutsy first which had other NFS problems and could not mount
anything, even after an update, which did at least allow me to start
the nfs server. In Gutsy even the initial ltsp build failed with a red
screen and had to be installed manually.

Can anybody help me past this point?

Thanks,

Marcus


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

NFS need path error
 

Add this: nfsroot=SERVER_IP_ADDRESS:/opt/ltsp/i386

...to the end of this line: DEFAULT vmlinuz ro initrd=initrd.img quiet
splash root=/dev/nfs ip=dhcp

...in this file:
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default

And that should do the trick.

-Tim


On 12/13/07 9:02 PM, "marcus" <lists@wordit.com> wrote:

> I have a new install of Feisty and the clients, different ones, all get
> an error from NFS saying "need path". The path /opt/ltsp/i386 is in the
> default DHCP server file, where I edited my IP range.
>
> I did try Gutsy first which had other NFS problems and could not mount
> anything, even after an update, which did at least allow me to start
> the nfs server. In Gutsy even the initial ltsp build failed with a red
> screen and had to be installed manually.
>
> Can anybody help me past this point?
>
> Thanks,
>
> Marcus
>


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

NFS need path error
 

On Fri, December 14, 2007 12:05, Timothy Boyden wrote:
> Add this: nfsroot=SERVER_IP_ADDRESS:/opt/ltsp/i386

Thanks, I got a step further, but not there yet. I had to add
ALL: LOCAL to hosts.allow in order to get the server IP and
filepath. It now shows:

rootserver 192.168.1.64, rootpath /opt/ltsp/i386
and filename /ltsp/i386/nbi.img. But then I get the errors:

connection: Connection refused
read: Connection refused
read: Connection refused
..... (repeated)


What does this mean?

Syslog shows an error from NFS on restarting:

Dec 15 06:52:32 eduserver mountd[8034]: Caught signal 15,
un-registering and exiting.
Dec 15 06:52:32 eduserver kernel: [ 2617.052000] nfsd: last
server has exited
Dec 15 06:52:32 eduserver kernel: [ 2617.052000] nfsd:
unexporting all filesystems
Dec 15 06:52:32 eduserver kernel: [ 2617.052000] RPC: failed to
contact portmap (errno -5).
Dec 15 06:52:33 eduserver exportfs[8274]: /etc/exports [1]:
Neither 'subtree_check' or 'no_subtree_check' specified for
export "*:/opt/ltsp/i386". Assuming default behaviour
('subtree_check'). NOTE: this default will change with
nfs-utils version 1.1.0
Dec 15 06:52:33 eduserver nfsd[8287]: nfssvc: writing fds to
kernel failed: errno 0 (Success)
Dec 15 06:52:33 eduserver nfsd[8287]: nfssvc: writing fds to
kernel failed: errno 0 (Success)
Dec 15 06:52:33 eduserver kernel: [ 2618.156000] NFSD: Using
/var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Dec 15 06:52:33 eduserver kernel: [ 2618.176000] NFSD: starting
90-second grace period
--------------------------

Am I getting close to connecting a client?


Thanks,

Marcus





--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users

NFS need path error
 

I think you have two problems there based on what you wrote:

"Connection refused" means your clients don't have permission or access to
connect, so you may need to revisit your hosts.allow config and maybe put an
entry for the subnet like: 192.168.1.0/24

I'm not sure of the exact way to write that. Google is your friend there...

The NFS errors seem to be an indication of a bad NFS server install. You may
need to uninstall and reinstall the NFS server package.

-Tim


On 12/15/07 12:57 AM, "Marcus" <lists@wordit.com> wrote:

> On Fri, December 14, 2007 12:05, Timothy Boyden wrote:
>> Add this: nfsroot=SERVER_IP_ADDRESS:/opt/ltsp/i386
>
> Thanks, I got a step further, but not there yet. I had to add
> ALL: LOCAL to hosts.allow in order to get the server IP and
> filepath. It now shows:
>
> rootserver 192.168.1.64, rootpath /opt/ltsp/i386
> and filename /ltsp/i386/nbi.img. But then I get the errors:
>
> connection: Connection refused
> read: Connection refused
> read: Connection refused
> ..... (repeated)
>
>
> What does this mean?
>
> Syslog shows an error from NFS on restarting:
>
> Dec 15 06:52:32 eduserver mountd[8034]: Caught signal 15,
> un-registering and exiting.
> Dec 15 06:52:32 eduserver kernel: [ 2617.052000] nfsd: last
> server has exited
> Dec 15 06:52:32 eduserver kernel: [ 2617.052000] nfsd:
> unexporting all filesystems
> Dec 15 06:52:32 eduserver kernel: [ 2617.052000] RPC: failed to
> contact portmap (errno -5).
> Dec 15 06:52:33 eduserver exportfs[8274]: /etc/exports [1]:
> Neither 'subtree_check' or 'no_subtree_check' specified for
> export "*:/opt/ltsp/i386". Assuming default behaviour
> ('subtree_check'). NOTE: this default will change with
> nfs-utils version 1.1.0
> Dec 15 06:52:33 eduserver nfsd[8287]: nfssvc: writing fds to
> kernel failed: errno 0 (Success)
> Dec 15 06:52:33 eduserver nfsd[8287]: nfssvc: writing fds to
> kernel failed: errno 0 (Success)
> Dec 15 06:52:33 eduserver kernel: [ 2618.156000] NFSD: Using
> /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
> Dec 15 06:52:33 eduserver kernel: [ 2618.176000] NFSD: starting
> 90-second grace period
> --------------------------
>
> Am I getting close to connecting a client?
>
>
> Thanks,
>
> Marcus
>
>
>
>


--
edubuntu-users mailing list
edubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/edubuntu-users