cancel
Showing results for 
Search instead for 
Did you mean: 

nfsd and nfsiod

SOLVED
Go to solution
sammysammy
Frequent Advisor

nfsd and nfsiod

Hi,

I am running Tru64 5.1B.
I setup nfsd with export as I did on the another Tru64 5.1B server, but this second Tru64 failed to export the file system.

ps axml | grep nfsd shown:
# ps axml | grep nfs
0 44 0 nfsiod_ I 0:00.00
0 44 0 nfsiod_ I 0:00.00
0 44 0 nfsiod_ I 0:00.00
0 44 0 nfsiod_ I 0:00.00
...
0 44 0 nfs_udp I 0:00.00
0 44 0 nfs_udp I 0:00.00
...
0 95391 1 0 44 0 2.31M 0K socket S ?? 0:00.01 /usr/sbin/nfsd -t4 -u8
0 99728 1 0 44 0 2.27M 104K async_d I ?? 0:00.00 /usr/sbin/nfsiod 7

From this output, there are 33 instances of nfsiod running, but the I only instructed the system to run 7 instances. I tried to restart nfsiod 7 (by kill -9 Proc_id and re-run the commandline), it still shown 33 instances of nfsiod.

Second problem is when I nmap this second Tru64 server's IP address, it doesn't show NFS-or-IIS service on port 1025. If I nmap the first Tru64 server, the result of nmap returned NFS-or-IIS running on port 1025.

The final problem is the goal I want to achieve, is that I want to remotely mount the Tru64 nfs file system from a linux server, but it said
[root@linux log]# /bin/mount -t nfs 10.1.10.2:/u01 /u01
mount to NFS server '10.1.10.2' failed.

The second Tru64 has the /etc/exports written with the following content:
/u01 -rw=linux

and the name of "linux" is reachable in the network.

Can anyone please suggest a way to resolve this error?

Very appreciate for your help.
Thanks
S
11 REPLIES
Ivan Ferreira
Honored Contributor
Solution

Re: nfsd and nfsiod

Use sysman nfssetup to configure NFS.

Check if the nfs servers are registered with pormap:

rpcinfo -p

Check if the server is exporting the file systems

showmount -e
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
sammysammy
Frequent Advisor

Re: nfsd and nfsiod

Thanks very much for the hints.
I found RPC program not registered.

# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100068 2 udp 5195 rpc.cmsd
100068 3 udp 5196 rpc.cmsd
100068 4 udp 5196 rpc.cmsd
100083 1 tcp 2653 rpc.ttdbserverd
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 udp 2049 nfs
100003 3 tcp 2049 nfs
# showmount -e
localhost: RPC: Program not registered
#

What can I do to fix this RPC error?

Thanks
sammysammy
Frequent Advisor

Re: nfsd and nfsiod

Hi,

I also found that executing S19nfs script doesn't start nfsd in the Tru64 server.

Sam
Steven Schweda
Honored Contributor

Re: nfsd and nfsiod

This might be easier if you closed the
duplicate thread.

> I setup nfsd with export as I did on the
> another Tru64 5.1B server, but this second
> Tru64 failed to export the file system.

And if you and I both knew how you did it on
the other system, then we might know
something about this one. But we don't.

> # showmount -e
> localhost: RPC: Program not registered

Probably because mountd is not running. For
example, around here:

urtx# /sbin/init.d/nfs stop

urtx# showmount -e
localhost: RPC: Program not registered

urtx# /sbin/init.d/nfs start
NFS mount daemon started
NFS export service started
NFS IO service started
NFS Locking:
rpc.statd started
rpc.lockd started

urtx# showmount -e
Exports list on localhost:
/var Everyone
/usr Everyone
/ Everyone


Is there anything in your "/etc/exports" file
(other than comments)?

I get confused when you talk about "another
Tru64 5.1B server", "this second Tru64", "the
first Tru64 server", "the Tru64 server", and
so on. Actual names and/or IP addresses
might help.


> I fixed the problem by adding NFSSERVING=1
> to the nfs script.

No, you only confused things more.

The "/sbin/init.d/nfs" script should be
reading "/etc/rc.config", which should be
reading "/etc/rc.config.common", and _that's_
where NFSSERVING should be set. And please
read the comments in "/etc/rc.config.common"
before editing the thing.
sammysammy
Frequent Advisor

Re: nfsd and nfsiod

Thanks for the comment.
Let's call the faulty server as Sender,
the working server is Ranger.

I found that Sender has the following configuration in the rc.config.common file:

JOIND_FLAGS=""
export JOIND_FLAGS
JOIND="no"
export JOIND
AUTOMOUNT_ARGS="-m /net -hosts -nosuid"
export AUTOMOUNT_ARGS
BIND_SERVERTYPE="CLIENT"
export BIND_SERVERTYPE

In Ranger:
#4.0 Merge
LSMSTART="mailonly"
export LSMSTART
SECURITY="ENHANCED"
export SECURITY
NFSSERVING="1"
export NFSSERVING
NONROOTMOUNTS="0"
export NONROOTMOUNTS
NUM_TCPD="4"
export NUM_TCPD
NFSLOCKING="1"
export NFSLOCKING
BIND_SERVERTYPE="CLIENT"
export BIND_SERVERTYPE
BIND_CONF="YES"
export BIND_CONF
BIND_SERVERARGS="NONE"
export BIND_SERVERARGS
JOIND="no"
export JOIND
JOIND_FLAGS=""
export JOIND_FLAGS
AUTOMOUNT_ARGS="-m /net -hosts -nosuid"
export AUTOMOUNT_ARGS

Yes, you are right, I should merge the config from Ranger to Sender, that s all.

Thanks

Steven Schweda
Honored Contributor

Re: nfsd and nfsiod

> [...] I should merge the config from Ranger
> to Sender, that s all.

"[T]hat's all"? You're scaring me again.

"man nfsconfig". Also "man rc.config":

Caution

You should always use rcmgr to make changes to the files. This will
preserve the correct syntax in the files. A lock file, /etc/rcmgr.lock
prevents multiple access to the data files.

Apparently the same stuff is available in
"sysman" under "Networking" > "Additional
Network Services" > "Network File System
(NFS)".
sammysammy
Frequent Advisor

Re: nfsd and nfsiod

do you know how to run sysman without using Xlib?

Steven Schweda
Honored Contributor

Re: nfsd and nfsiod

> do you know how to run sysman without using
> Xlib?

Unset your DISPLAY variable? (How to do that
depends on your shell.)
sammysammy
Frequent Advisor

Re: nfsd and nfsiod

er... no, I meant I want to execute a curses-base sysman.

Thanks
Steven Schweda
Honored Contributor

Re: nfsd and nfsiod

> er... no, I meant I want to execute a
> curses-base sysman.

If that means using a simple terminal or
terminal emulator instead of some X Windows
semi-graphical thing, then that's what I
meant, too.

Did you try unsetting your DISPLAY variable?

urtx# unset DISPLAY
urtx# sysman
Use the following keys when working with SysMan applications on a terminal:

Field Navigation:
Use the Tab key or the arrow keys to move from field to field.
Scrolling:
Use Page Up/Page Down (or Prev/Next) to scroll.
Selection:
Use the space bar to:
- toggle the selection in a list box
- choose an item in a radio box
- enable or disable a check box (toggle button)
[...]
sammysammy
Frequent Advisor

Re: nfsd and nfsiod

Thanks, that works.