nakbijak895
asked on
AIX nfs subsystem unable to run
hi i'm running AIX 5.1 ML 4
The problem is ...
i tried to activate nfs
To start the nfs group, i type
# startsrc -g nfs
nfsd, biod,rpc.statd,rpc.lockd showing ALL STARTED WITH PROCESS ID.
but then when i type to check status #lssrc -g nfs
showing that only nfsd,biod that are running ...
but subsystems below are failed to run (inoperative status)
rpc.statd inoperative
rpc.lockd inoperative
rpc.mountd inoperative
There is no error message coming out. so i have no idea why the subsystems were stopped.
Any guru can tell what's the problem and how to make rpc.statd,rpc.lockd,rpc.mo untd able to be running.
Thank you very much.
The problem is ...
i tried to activate nfs
To start the nfs group, i type
# startsrc -g nfs
nfsd, biod,rpc.statd,rpc.lockd showing ALL STARTED WITH PROCESS ID.
but then when i type to check status #lssrc -g nfs
showing that only nfsd,biod that are running ...
but subsystems below are failed to run (inoperative status)
rpc.statd inoperative
rpc.lockd inoperative
rpc.mountd inoperative
There is no error message coming out. so i have no idea why the subsystems were stopped.
Any guru can tell what's the problem and how to make rpc.statd,rpc.lockd,rpc.mo
Thank you very much.
Those activate when you export some directory.
ASKER
Here what i have gotten :-
LOCDEV(root)/> mount loc2:/perl /test
mount: 1831-010 server loc2 not responding: RPC: 1832-019 Program not registered
mount: retrying
loc2:/perl
LOCDEV(root)/> lssrc -g nfs
Subsystem Group PID Status
biod nfs 417898 active
nfsd nfs 426096 active
rpc.statd nfs inoperative
rpc.lockd nfs inoperative
rpc.mountd nfs inoperative
LABEL: SRC_TRYX
IDENTIFIER: 1BA7DF4E
Date/Time: Fri Jun 13 22:12:14 2008
Sequence Number: 129113
Machine Id: 005A7D8D4C00
Node Id: LOCDEV
Class: S
Type: PERM
Resource Name: SRC
Description
SOFTWARE PROGRAM ERROR
Probable Causes
APPLICATION PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
DETERMINE WHY SUBSYSTEM CANNOT RESTART
Detail Data
SYMPTOM CODE
256
SOFTWARE ERROR CODE
-9020
ERROR CODE
0
DETECTING MODULE
'srchevn.c'@line:'327'
FAILING MODULE
rpc.statd
-------------------------- ---------- ---------- ---------- ---------- ---------
LABEL: SRC_TRYX
IDENTIFIER: 1BA7DF4E
Date/Time: Fri Jun 13 22:12:11 2008
Sequence Number: 129110
Machine Id: 005A7D8D4C00
Node Id: LOCDEV
Class: S
Type: PERM
Resource Name: SRC
Description
SOFTWARE PROGRAM ERROR
Probable Causes
APPLICATION PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
DETERMINE WHY SUBSYSTEM CANNOT RESTART
Detail Data
SYMPTOM CODE
256
SOFTWARE ERROR CODE
-9020
ERROR CODE
0
DETECTING MODULE
'srchevn.c'@line:'327'
FAILING MODULE
rpc.mountd
LOCDEV(root)/> errpt -a -j 1BA7DF4E |pg
-------------------------- ---------- ---------- ---------- ---------- ---------
LABEL: SRC_TRYX
IDENTIFIER: 1BA7DF4E
Date/Time: Sat Jun 14 00:23:22 2008
Sequence Number: 129150
Machine Id: 005A7D8D4C00
Node Id: LOCDEV
Class: S
Type: PERM
Resource Name: SRC
Description
SOFTWARE PROGRAM ERROR
Probable Causes
APPLICATION PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
DETERMINE WHY SUBSYSTEM CANNOT RESTART
Detail Data
SYMPTOM CODE
256
SOFTWARE ERROR CODE
-9020
ERROR CODE
0
DETECTING MODULE
'srchevn.c'@line:'327'
FAILING MODULE
rpc.lockd
LOCDEV(root)/> mount loc2:/perl /test
mount: 1831-010 server loc2 not responding: RPC: 1832-019 Program not registered
mount: retrying
loc2:/perl
LOCDEV(root)/> lssrc -g nfs
Subsystem Group PID Status
biod nfs 417898 active
nfsd nfs 426096 active
rpc.statd nfs inoperative
rpc.lockd nfs inoperative
rpc.mountd nfs inoperative
LABEL: SRC_TRYX
IDENTIFIER: 1BA7DF4E
Date/Time: Fri Jun 13 22:12:14 2008
Sequence Number: 129113
Machine Id: 005A7D8D4C00
Node Id: LOCDEV
Class: S
Type: PERM
Resource Name: SRC
Description
SOFTWARE PROGRAM ERROR
Probable Causes
APPLICATION PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
DETERMINE WHY SUBSYSTEM CANNOT RESTART
Detail Data
SYMPTOM CODE
256
SOFTWARE ERROR CODE
-9020
ERROR CODE
0
DETECTING MODULE
'srchevn.c'@line:'327'
FAILING MODULE
rpc.statd
--------------------------
LABEL: SRC_TRYX
IDENTIFIER: 1BA7DF4E
Date/Time: Fri Jun 13 22:12:11 2008
Sequence Number: 129110
Machine Id: 005A7D8D4C00
Node Id: LOCDEV
Class: S
Type: PERM
Resource Name: SRC
Description
SOFTWARE PROGRAM ERROR
Probable Causes
APPLICATION PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
DETERMINE WHY SUBSYSTEM CANNOT RESTART
Detail Data
SYMPTOM CODE
256
SOFTWARE ERROR CODE
-9020
ERROR CODE
0
DETECTING MODULE
'srchevn.c'@line:'327'
FAILING MODULE
rpc.mountd
LOCDEV(root)/> errpt -a -j 1BA7DF4E |pg
--------------------------
LABEL: SRC_TRYX
IDENTIFIER: 1BA7DF4E
Date/Time: Sat Jun 14 00:23:22 2008
Sequence Number: 129150
Machine Id: 005A7D8D4C00
Node Id: LOCDEV
Class: S
Type: PERM
Resource Name: SRC
Description
SOFTWARE PROGRAM ERROR
Probable Causes
APPLICATION PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
DETERMINE WHY SUBSYSTEM CANNOT RESTART
Detail Data
SYMPTOM CODE
256
SOFTWARE ERROR CODE
-9020
ERROR CODE
0
DETECTING MODULE
'srchevn.c'@line:'327'
FAILING MODULE
rpc.lockd
Is portmap running? Use "lssrc -s portmap" to see.
ASKER
yes .. portmap is running ...
What else other possible ?
What else other possible ?
Type rpcinfo -p
if you get nfsd and mountd running your NFS is functional. Try mount from some other system.
if you get nfsd and mountd running your NFS is functional. Try mount from some other system.
ASKER
loc1 = master server
loc2 = client server
loc2(root)/> rpcinfo -p loc1
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100068 2 udp 42769 cmsd
100068 3 udp 42769 cmsd
100068 4 udp 42769 cmsd
100068 5 udp 42769 cmsd
100083 1 tcp 42769 ttdbserver
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
200006 1 udp 2049
200006 1 tcp 2049
100005 1 udp 42780 mountd
100005 2 udp 42780 mountd
100005 3 udp 42780 mountd
100005 1 tcp 42773 mountd
100005 2 tcp 42773 mountd
100005 3 tcp 42773 mountd
100024 1 tcp 42775 status
100024 1 udp 42793 status
100133 1 tcp 42775
100133 1 udp 42793
200001 1 tcp 42775
200001 1 udp 42793
200001 2 tcp 42775
200001 2 udp 42793
100021 1 udp 42818 nlockmgr
100021 2 udp 42818 nlockmgr
100021 3 udp 42818 nlockmgr
100021 4 udp 42818 nlockmgr
100021 1 tcp 42777 nlockmgr
100021 2 tcp 42777 nlockmgr
100021 3 tcp 42777 nlockmgr
100021 4 tcp 42777 nlockmgr
loc1(root)/> rpcinfo -p loc2
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100068 2 udp 42768 cmsd
100068 3 udp 42768 cmsd
100068 4 udp 42768 cmsd
100068 5 udp 42768 cmsd
100083 1 tcp 42768 ttdbserver
loc2 = client server
loc2(root)/> rpcinfo -p loc1
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100068 2 udp 42769 cmsd
100068 3 udp 42769 cmsd
100068 4 udp 42769 cmsd
100068 5 udp 42769 cmsd
100083 1 tcp 42769 ttdbserver
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
200006 1 udp 2049
200006 1 tcp 2049
100005 1 udp 42780 mountd
100005 2 udp 42780 mountd
100005 3 udp 42780 mountd
100005 1 tcp 42773 mountd
100005 2 tcp 42773 mountd
100005 3 tcp 42773 mountd
100024 1 tcp 42775 status
100024 1 udp 42793 status
100133 1 tcp 42775
100133 1 udp 42793
200001 1 tcp 42775
200001 1 udp 42793
200001 2 tcp 42775
200001 2 udp 42793
100021 1 udp 42818 nlockmgr
100021 2 udp 42818 nlockmgr
100021 3 udp 42818 nlockmgr
100021 4 udp 42818 nlockmgr
100021 1 tcp 42777 nlockmgr
100021 2 tcp 42777 nlockmgr
100021 3 tcp 42777 nlockmgr
100021 4 tcp 42777 nlockmgr
loc1(root)/> rpcinfo -p loc2
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100068 2 udp 42768 cmsd
100068 3 udp 42768 cmsd
100068 4 udp 42768 cmsd
100068 5 udp 42768 cmsd
100083 1 tcp 42768 ttdbserver
Server says they are up and running.
ASKER
yes but still the subsystem below failed to run.
rpc.statd inoperative
rpc.lockd inoperative
rpc.mountd inoperative
rpc.statd inoperative
rpc.lockd inoperative
rpc.mountd inoperative
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
I get them inoperative and mounting on 64bit AIX.
i.e "inoperative" AIX server allows Linux, 32/64 AIX clients, FreeBSD clients and wvwn SFU clients.
Those are on-demand started by inetd. "inoperable" display is because inetd was not restarted. Then again one installs 2-bit system rebooting 10 times and says it is completely different.
lockd/statd do not cause problems unless multiple users co-edit same files or you have weak network links.
lockd/statd do not cause problems unless multiple users co-edit same files or you have weak network links.