| View previous topic :: View next topic |
| Author |
Message |
outspoken
Guru
Joined: 14 Feb 2004
Posts: 464
Location: orlando, fl
|
 Posted: Sun Feb 20, 2005 4:47 am Post subject: NFS stops working during connect. |
 |
|
Well, I've setup everything I can think of and this is where I am stuck at. The services are all running and there are no iptables to block anything. The odd thing is that it works for al ittle bit then just stops. It gets dhcp fine, it authenticates on nfs and grabs the kernel but then just stops and gives a message on the client side (shown below).
/var/log/messages (from server):
| Code: |
Feb 19 23:29:56 Gray dhcpd: DHCPREQUEST for 192.168.1.4 from 00:e0:7d:a1:c3:3e via eth0: unknown lease 192.168.1.4.
Feb 19 23:30:03 Gray /usr/sbin/cron[17425]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Feb 19 23:35:03 Gray eth0: Promiscuous mode enabled.
Feb 19 23:35:03 Gray device eth0 entered promiscuous mode
Feb 19 23:36:47 Gray device eth0 left promiscuous mode
Feb 19 23:38:11 Gray dhcpd: BOOTREQUEST from 00:e0:18:a8:52:46 via eth0
Feb 19 23:38:11 Gray dhcpd: BOOTREPLY for 192.168.1.5 to mediabox (00:e0:18:a8:52:46) via eth0
Feb 19 23:38:12 Gray xinetd[15098]: START: tftp pid=17466 from=192.168.1.5
Feb 19 23:38:18 Gray dhcpd: DHCPDISCOVER from 00:e0:18:a8:52:46 via eth0
Feb 19 23:38:18 Gray dhcpd: DHCPOFFER on 192.168.1.5 to 00:e0:18:a8:52:46 via eth0
Feb 19 23:38:18 Gray dhcpd: DHCPREQUEST for 192.168.1.5 (192.168.1.4) from 00:e0:18:a8:52:46 via eth0
Feb 19 23:38:18 Gray dhcpd: DHCPACK on 192.168.1.5 to 00:e0:18:a8:52:46 via eth0
Feb 19 23:38:18 Gray rpc.mountd: authenticated mount request from mediabox:657 for /opt/ltsp-4.1/i386 (/opt/ltsp-4.1/i386)
|
Here is what the client says when attaching:
| Code: |
nfs: server 192.168.1.4 not responding, still trying
|
The tftp/dhcp/nfs server is 192.168.1.4 and the attaching thin client is 192.168.1.5
Here is my /etc/exports:
| Code: |
# /etc/exports: NFS file systems being exported. See exports(5).
/tftpboot 192.168.1.5(rw,no_root_squash,async)
/opt/ltsp-4.1/i386 192.168.1.5(ro,no_root_squash,async)
/var/opt/ltsp/swapfiles 192.168.1.5(rw,no_root_squash,async
|
/etc/dhcp/dhcpd.conf:
| Code: |
## Some general options
default-lease-time 21600;
max-lease-time 21600;
use-host-decl-names on;
ddns-update-style ad-hoc;
## Bootp options
allow booting;
allow bootp;
## Network Options
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.254;
option domain-name-servers 192.168.1.254;
option log-servers 192.168.1.254;
option domain-name "ashitaka.net";
## LTSP Path Options
option root-path "192.168.1.4:/opt/ltsp-4.1/i386";
filename "/lts/vmlinuz-2.4.26-ltsp-2";
## If your workstations have ISA NICs uncomment the following
## lines and alter the driver and IO
#option option-128 code 128 = string;
#option option-129 code 129 = text;
#option option-128 e4:45:74:68:00:00;
#option option-129 "NIC=ne IO=0x300";
shared-network WORKSTATIONS {
subnet 192.168.1.0 netmask 255.255.255.0 {
## Distribute dynamic IPs to the workstations
# range dynamic-bootp 192.168.1.2 192.168.1.16;
## Workstation specific configuration for PXE booting
host mediabox {
hardware ethernet 00:E0:18:A8:52:46;
fixed-address 192.168.1.5;
}
}
}
|
|
|
| Back to top |
|
 |
angoraspruce
Apprentice
Joined: 08 Jan 2005
Posts: 193
Location: Minnesota, USA
|
| Posted: Sun Feb 20, 2005 5:26 am Post subject: |
|
|
Hello outspoken,
Have you checked that 'rpc.portmap' is running on the client as well? If not, NFS can take several minutes to mount the remote directory, or fail altogether. I'm asking because of where the server hangs when the remote computer tried mounting the NFS. <shrug> A possibility.
Best regards  |
|
| Back to top |
|
|
outspoken
Guru
Joined: 14 Feb 2004
Posts: 464
Location: orlando, fl
|
| Posted: Sun Feb 20, 2005 6:03 am Post subject: |
|
|
hi angoraspruce. yes, i have checked to make sure that portmap is running, here is the output of a couple commands:
| Code: |
Gray lts # /etc/init.d/portmap status
* status: started
Gray lts # rpcinfo -p localhost
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 4000 status
100024 1 tcp 4000 status
100005 1 udp 4002 mountd
100005 1 tcp 4002 mountd
100005 2 udp 4002 mountd
100005 2 tcp 4002 mountd
100005 3 udp 4002 mountd
100005 3 tcp 4002 mountd
|
|
|
| Back to top |
|
|
outspoken
Guru
Joined: 14 Feb 2004
Posts: 464
Location: orlando, fl
|
| Posted: Sun Feb 20, 2005 6:07 am Post subject: |
|
|
also, here is my /etc/conf.d/nfs:
| Code: |
# Config file for /etc/init.d/nfs
# If you wish to set the port numbers for lockd,
# please see /etc/sysctl.conf
# Number of servers to be started up by default
RPCNFSDCOUNT=8
# Options to pass to rpc.mountd
# ex. RPCMOUNTDOPTS="-p 32767
RPCMOUNTDOPTS="-p 4002"
# Options to pass to rpc.statd
# ex. RPCSTATDOPTS="-p 32765 -o 32766"
RPCSTATDOPTS="-p 4000"
# Timeout (in seconds) for exportfs
EXPORTFSTIMEOUT=30
|
|
|
| Back to top |
|
|
saltine
n00b
Joined: 25 Mar 2005
Posts: 24
Location: Winnipeg, Canada
|
| Posted: Sun Apr 17, 2005 9:49 pm Post subject: |
|
|
Try connecting a client direct to the server with a cross over. I suspect a network issue.
_________________
Recipe for Network Booting |
|
| Back to top |
|
|
angrycoder
n00b
Joined: 29 Dec 2004
Posts: 17
|
| Posted: Sun Apr 17, 2005 9:57 pm Post subject: |
|
|
maybe this sounds stupid, but is nfsd running? your rpcinfo should report nfs also and it's versions, so it should look something like this:
| Code: |
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 32774 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 32770 nlockmgr
100021 3 udp 32770 nlockmgr
100021 4 udp 32770 nlockmgr
100005 1 udp 892 mountd
100005 1 tcp 895 mountd
100005 2 udp 892 mountd
100005 2 tcp 895 mountd
100005 3 udp 892 mountd
100005 3 tcp 895 mountd
|
try /etc/init.d/nfs restart
also maybe try adding the keyword "insecure" to your exports directories you have listed, and maybe try changing async to sync |
|
| Back to top |
|
|
|
Networking & Security
