Starting nfsd on HP-UX 11.0

[Manjunath Shastry]

Greetings Gurus,

I am trying to start nfsd on HP-UX 11.0 on a HP C Class Workstation, but the demon doesn 't seem to start. I tried starting NFS Server through SAM, even that doesn 't sem to work.

How do i start NFS Server Services ?

Manjunath.

[Massimo Bianchi]

Hi,
you must check a couple of things:


- file /etc/rc.config.d/nfsconf

the SERVER part must be 1

then, and only then

/sbin/init.d/nfs.server start
if you also want tthe client
/sbin/init.d/nfs.client start

SAM uses the /sbin script, but they start is they are configured.

Massimo

[Con O'Kelly]

Hi

Set the following in /etc/rc.config.d/nfsconf file:
NFS_CLIENT=1
NFS_SERVER=1

Then run the following:
# /sbin/init.d/nfs.core start
# /sbin/init.d/nfs.client start
# /sbin/init.d/nfs.server start

Cheers
Con

[Steven E. Protter]

You need to have some filesystems exported in /etc/exports

You need to start the three daemons

nfs.core
nfs.server
nfs.client

Core must run, you can omit client if you never want to be an nfs client

Better to run it.

All three are in /sbin/init.d/

to: Start

/sbin/init.d/nfs.core start
/sbin/init.d/nfs.server start
/sbin/init.d/nfs.client start

It took a bunch of tried to get this to post. Something is up with itrc

Regards,

SEP

[RAJESH GANGADHARAN]

Hi,
Check the /etc/rc.config.d/nfsconf file for NFS_SERVER=1, if the value is not 1, chnage it to 1.
check the NUM_NFSD, this will tell the number of nfsd process.
then restart the nfs service by
/sbin/init.d/nfs.server start

-Rajesh

[Manjunath Shastry]

Greetings Gurus,


I still have a problem in starting the NFS Server.

The Variables
NFS_CLIENT=1
NFS_SERVER=1
NUM_NFSD=16
NUM_NFSIOD=16
have the assigned values in /etc/rc.config.d/nfsconf

When I start the /sbin/init.d/nfs.server I get the following output

# ./nfs.server start
starting NFS SERVER networking

starting up the rpcbind daemon
rpcbind already started, using pid: 843
exportfs error: /usr/system: No such file or directory
exportfs error: /usr/users/vipul: No such file or directory
Reading in /etc/exports
starting up the mount daemon
rpc.mountd already started, using pid: 1906
starting up the NFS daemons
/usr/sbin/nfsd 16
starting up the Status Monitor daemon
rpc.statd already started, using pid: 921
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 927


./nfs.core start
starting NFS CORE networking

starting up the rpcbind
rpcbind already started, using pid: 843

But still nfsd is not visible in the process and I am unable to utilize NFS Services.


What may be wrong ?, would appreciate your help.


Regards,
Manjunath.

[Massimo Bianchi]

exportfs error: /usr/system: No such file or directory
exportfs error: /usr/users/vipul: No such file or directory

What is the content of
/etc/exports

?

BTW:
proper order to start is

nfs.core
nfs.server
nfs.client

Massimo

[RAC_1]

It clearly says no such file /usr/system and /usr/system/vipul.

Check if they are present and have appropriate permissions.

[Caesar_3]

Hello!

As you can see exportfs has problem of export
the 2 directory, post your /etc/exports

Caesar

[Manjunath Shastry]

Greetings Gurus,

Thank you for further clarification. I did not notice the exportfs error, regret the overlook. There were old entries in /etc/exports file which I have removed. Now looks like my /etc/exports is intact and it looks like this.

/abaqus/abq_exp -root=mesh

Now when I start the NFS Daemons, I get the following Output

./nfs.core start
starting NFS CORE networking

starting up the rpcbind
rpcbind already started, using pid: 843


./nfs.server start
starting NFS SERVER networking

starting up the rpcbind daemon
rpcbind already started, using pid: 843
Reading in /etc/exports
starting up the mount daemon
rpc.mountd already started, using pid: 1906
starting up the NFS daemons
/usr/sbin/nfsd 16
starting up the Status Monitor daemon
rpc.statd already started, using pid: 921
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 927

# ./nfs.client start
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 843
starting up the BIO daemons
biod(s) already started, using pid(s): 898 899 897 900 901 902 903 904 9
05 906 907 908 909 910 911 912
Reading in /etc/exports
starting up the Status Monitor daemon
rpc.statd already started, using pid: 921
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 927
starting up the Automount daemon
automount already started, using pid: 938
mounting remote NFS file systems ...
Permission denied
FAILURE CODE: 1
Mount failed! Possible local filesystem mount.
If local filesystem, then nfs.server will mount it.

This is the output, there seems to be a problem in mounting remote file systems, But I think that should should not be a problem to start NFSD.

I am still not able to start the NFSD Daemon.

I can 't reboot the System atleast for next couple of days. What do I do further ?


Regards,
Manjunath.

[RolandH]

Check your /etc/fstab file if you have there any entries with nfs mounts.

Give us your hole /etc/rc.config.d/nfsconf file. Could be problems with the automounter.

But first I recommend you to stop and start again the nfs startup procedure. Could be something wrong in yours. Because nfs.server and nfs.client was running and formost then you have started nfs.core server an client in the right direction.

So do that.

/etc/rc.config./nfs.client stop
/etc/rc.config./nfs.server stop
/etc/rc.config./nfs.core stop

Are processes really stopped as was said in the stop messages? Check this with ps command. Otherwise kill them. Then do the startup procedure in this sequence.

/etc/rc.config./nfs.core start
/etc/rc.config./nfs.server start
/etc/rc.config./nfs.client start



HTH

Roland

[RolandH]

Have given you the wrong path, sorry.

It is /sbin/init.d/nfs.core stop/start

similar to the others.

NOT
/etc/rc.config./nfs.core


Roland

PS : That is fat finger syndrome

[Kevin Wright]

Are you trying to mount a remote filesystem? If so, try mounting in manually, do a showmount -e to ensure you have correct permissions to mount it.

[Massimo Bianchi]

Hi,
check two things:

- since you are going to reboot, put AUTOFS=1, it works much better than automount. same parameters, no need to have further changes

- check if the remote host is properly exporting towards your hosts.

In aby case, without nfsd, you can try to mount the FS by hand:


mount remote:/export/dir /local/dir

Does this work ?

Massimo

[Tim D Fulford]

Hi

NFS needs to be in the kernel as well.

What is the result of doing the following
# /usr/sbin/kmsystem | egrep -i nfs

There should be 4 items listed here, if not you will need to re-build the kernel with them in. The default is to have them in the kernel, thus if they have been removed from the kernel it was probably done on purpose, so you might want to check this out before re-building the kernel as NFS is sited as a potential security problem (hours of fun discussing NFS & security!!!).

Regards

Tim

[Tim D Fulford]

As a side issue, I saw /abacus/... & infer you are using ABACUS the Finite Element program, IF you are using the NFS to store models or the binaries etc fine. BUT IF you are using it for matrix decompositions, inversions, Gausiean ... blah blah blah... the calculation will be slow & will probably flood the network segment!!

Hope you have some sucess soon (Tim, the Ex-FE guy)

Regards

Tim