NFS need path error

[Marcus]

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