NFS mount point issue

[bin_smr]

Hello Experts ,

    Whenever any user login to the workstation which is HP-UX 11.11 OS(model-c3700) and tries to access the mount point which has already migrated from old mount point,the application which is CATIA itself getting keep on restarting by throwing the below error

CATRACE FILE : /home/<user_id>/catraceka00075925665.log

                         ********************************
                         * ERROR NUMBER : S0010         *
                         ********************************

and also i checked the log files but its not  giving any error.

But when i am keeping same .model file from new mount point in different locaion like /home/<user_id> or /tmp or anywhere else, its working fine means CATIA application working perfectly without throwing any error . I have doubt could it be system issue or mount point issue ?

NOTE :- Previously mount point was on AIX server and it was working fine but after migration now the mount is having on Solaris server and its working fine except this perticular old workstation.

Can any body suggest me regarding above issue ?

[Dennis Handly]

>tries to access the mount point

What is the new mount point and is this writable by the user?

[bin_smr]

I hope it will be helpful to you . Please find the below output :

1. This is the Solaris server NFS config output where's mount point located :

bash-3.00# more /etc/default/nfs
NFSD_LISTEN_BACKLOG=32
NFSD_PROTOCOL=ALL
NFSD_SERVERS=16
LOCKD_LISTEN_BACKLOG=32
LOCKD_SERVERS=20
LOCKD_RETRANSMIT_TIMEOUT=5
GRACE_PERIOD=90
NFS_SERVER_VERSMIN=3
NFS_SERVER_VERSMAX=3
NFS_CLIENT_VERSMIN=3
NFS_CLIENT_VERSMAX=3

2. This is the HP-UX  NFS Config & mount point output :

bash-2.04# more /etc/rc.config.d/nfsconf
#**********************  NFSCONF  ******************************

# NFS configuration.  See nfsd(1m), mount(1m), pcnfsd(1m)
#
# @(#)B.11.11_LR
#
# NFS_CLIENT:   1 if this node is an NFS client, 0 if not
# NFS_SERVER:   1 if this node is an NFS server, 0 if not
#               Note: it is possible for one host to be a client, a server,
#               both or neither!  This system is an NFS client if you will
#               be NFS mounting remote file systems; this system is a server
#               if you will be exporting file systems to remote hosts.
#               See Also:  nfsd(1M), mount(1M).
# NUM_NFSD:     Number of NFS deamons (nfsd) to start on an NFS server.  Four
#               has been chosen as optimal.
# NUM_NFSIOD:   Number of NFS BIO daemons (biod) to start on an NFS client.
#               Four has been chosen as optimal.
# PCNFS_SERVER: 1 if this node is a server for PC-NFS requests.  This
#               variable controls the startup of the pcnfsd(1M) server.
#               See Also:  pcnfsd(1M).
#
NFS_CLIENT=1
NFS_SERVER=1
NUM_NFSD=30
NUM_NFSIOD=16
PCNFS_SERVER=0
# export feature does not work in this file since files are being
# sourced into another file rc.config and this file is being sourced
# into the startup scripts.
...skipping...
#**********************  NFSCONF  ******************************

# NFS configuration.  See nfsd(1m), mount(1m), pcnfsd(1m)
#
# @(#)B.11.11_LR
#
# NFS_CLIENT:   1 if this node is an NFS client, 0 if not
# NFS_SERVER:   1 if this node is an NFS server, 0 if not
#               Note: it is possible for one host to be a client, a server,
#               both or neither!  This system is an NFS client if you will
#               be NFS mounting remote file systems; this system is a server
#               if you will be exporting file systems to remote hosts.
#               See Also:  nfsd(1M), mount(1M).
# NUM_NFSD:     Number of NFS deamons (nfsd) to start on an NFS server.  Four
#               has been chosen as optimal.
# NUM_NFSIOD:   Number of NFS BIO daemons (biod) to start on an NFS client.
#               Four has been chosen as optimal.
# PCNFS_SERVER: 1 if this node is a server for PC-NFS requests.  This
#               variable controls the startup of the pcnfsd(1M) server.
#               See Also:  pcnfsd(1M).
#
NFS_CLIENT=1
NFS_SERVER=1
NUM_NFSD=30
NUM_NFSIOD=16
PCNFS_SERVER=0
# export feature does not work in this file since files are being
# sourced into another file rc.config and this file is being sourced
# into the startup scripts.

#
# DAEMON OPTIONS
#
# LOCKD_OPTIONS:   options to be passed to rpc.lockd  when it is started.
# STATD_OPTIONS:   options to be passed to rpc.statd  when it is started.
# MOUNTD_OPTIONS:  options to be passed to rpc.mountd when it is started.
#
LOCKD_OPTIONS=""
STATD_OPTIONS=""
MOUNTD_OPTIONS=""
#
# automount configuration
#
# AUTOMOUNT = 0 Do not start automount
# AUTOMOUNT = 1 Start Automount.
# AUTO_MASTER = filename of the master file passed to automount
# AUTO_OPTIONS = options passed to automount
#
AUTOMOUNT=1
AUTO_MASTER="/etc/auto_master"
AUTO_OPTIONS="-f $AUTO_MASTER"
#
# rpc.mountd configuration.  See mountd(1m)
#
# START_MOUNTD: 1 if rpc.mountd should be started by a system startup script.
#               0 if /etc/inetd.conf has an entry for mountd.
#       Note: rpc.mountd should be started from a system startup script,
#       however, it can be started from either nfs.server or inetd, and
#       MUST only be configured in one place.
#
START_MOUNTD=1
#
#autofs configuration.  See autofs(1m)
#
#For the 11.0 Release line both AUTOFS and the old Automount
#are delivered.  In order to invoke the AUTOFS instead of
#you must set the AUTOFS flag to 1.
#
#/usr/sbin/automount is now a script that sources in this file
#Depending on the variable AUTOFS, either AUTOFS or the old
#automount process will execute.  The nfs.client start script
#will also use this variable to start the appropriate process
#during the boot sequence.
#AUTOFS=  0 - use the old automount process.
#         1 - use the new AutoFS.
#AUTOMOUNT_OPTIONS=  - options to the AutoFS automount command
#AUTOMOUNTD_OPTIONS= - options to the AutoFS automountd daemon
#
#The AUTOMOUNT flag still needs to be set for either the old
#automount or new AutoFS to be started by the nfs.client script.
#
AUTOFS=1
AUTOMOUNT_OPTIONS=""
AUTOMOUNTD_OPTIONS=""

and below is the new mount point and for this user access has been given:

10.243.0.54:/projects
                   1882687624 1292630240 590057384   69% /projects

[Matti_Kurkela]

On the Solaris host, please run this command and show the output:

grep /projects /etc/dfs/dfstab

On the HP-UX host, please run these commands and show the output:

ls -ld /projects
grep /projects /etc/fstab

[bin_smr]

Hello Matti ,

Thanks for your response , Please find the below cmd output :

On Solaris host :- 

bash-3.00# grep /projects /etc/dfs/dfstab
bash-3.00#
But didn't get any output from above cmd, So i am providing below these cmd output which might be helpful to you.

bash-3.00# more /etc/dfs/dfstab
# Do not modify this file directly.
# Use the sharemgr(1m) command for all share management
# This file is reconstructed and only maintained for backward
# compatibility. Configuration lines could be lost.
#
#       Place share(1M) commands here for automatic execution
#       on entering init state 3.
#
#       Issue the command 'svcadm enable network/nfs/server' to
#       run the NFS daemon processes and the share commands, after adding
#       the very first entry to this file.
#
#       share [-F fstype] [ -o options] [-d "<text>"] <pathname> [resource]
#       .e.g,
#       share  -F nfs  -o rw=engineering  -d "home dirs"  /export/home2

bash-3.00# df -h
projects               1.8T   1.2T   561G    69%    /projects

On HP-UX host :-

bash-2.04# ls -ld /projects/
drwxr-xr-x  81 root       root            90 Oct  2 09:41 /projects/

bash-2.04# grep /projects /etc/fstab
10.243.0.54:/projects /projects nfs rw,suid 0 0

one more thing i want to share with this mount point every where with C8000 & C3700 model its working perfectly problem is only with this system.

[Dave Olker]

On the HP-UX NFS client, issue the command: showmount -e <NFS server hostname>.  This will confirm the NFS client can send RPC requests to the NFS server and show the list of shared/exported filesystems.  It should also show if the NFS client is in the access lists on the server, assuming there is one.

Dave

[bin_smr]

Hello Dave,

Just check the below one...
bash-2.04# showmount -e zeus
export list for zeus:
/impdata/caedata (everyone)
/projects/cadds5-mockups (everyone)
/projects (everyone)
/u1 (everyone)
bash-2.04#

[Dave Olker]

So the server (Solaris) is sharing /projects, the NFS client (HP-UX) is mounting /projects.  What specifically is not working?  Is the problem that users on the client cannot read or write files in /projects?  Is the problem that users cannot lock files in /projects?  Can you be very specific about what the exact problem is and are you able to reproduce the problem outside of your application?

[bin_smr]

Yes server (Solaris) is sharing /projects, the NFS client (HP-UX) is mounting /projects & also users on the client can read or write files in /projects.Problem also i'm not getting specifically.Because for every other system that .model file (inside /projects)working perfectly for catia application but only in this system at the time of using catia application when mounting to that particular project and using the .model file it is getting restarted by showing some s10 or s11 error .Before migration we've installed some NIS patches in all HPUX systems.

So for that particular system do i need to install some more patches so that it'll work.Can you help me on that.

[Dave Olker]

> Because for every other system that .model file (inside /projects)working perfectly

> for catia application but only in this system at the time of using catia application

> when mounting to that particular project and using the .model file it is getting restarted

> by showing some s10 or s11 error .

I'm not familiar enough with the Catia application to know what an S10 or S11 error is or what it means.  Have you checked with Catia to learn what these errors indicate?  This is why I recommended you try to reproduce the *symptom* outside of Catia.  Aside from the application errors, what is the actual symptom you experience?  Does the application hang?  Does it end? 

The last time I dealt with a Catia problem the issue turned out to be a file locking problem.  That might explain your situation, where users can read/write in /projects but Catia throws errors.

If you can explain exactly what the symptom is, and check with Catia to learn what an s10/s11 error means, it would help us narrow down the underlying cause of the problem.

Dave