nfs.core and nfs.server dump core

[Ramassh]

Unable to mount NFS files, and got error on the NFS server (HP-UX 11.11):

# /sbin/init.d/nfs.core start
starting NFS CORE networking

starting up the rpcbind
rpcbind already started, using pid: 877
/sbin/init.d/nfs.core[242]: 4283 Bad system call(coredump)
Error: NFS nfskd NOT started

# /sbin/init.d/nfs.server start
starting NFS SERVER networking

starting up the rpcbind daemon
rpcbind already started, using pid: 877
/sbin/init.d/nfs.server[146]: 4305 Bad system call(coredump)
FAILURE CODE: 140
starting up the mount daemon
rpc.mountd already started, using pid: 2156
starting up the NFS daemons
nfsd(s) already started, using pid(s): 2175
starting up the Status Monitor daemon
rpc.statd already started, using pid: 908
starting up the Lock Manager daemon
rpc.lockd already started, using pid: 914


The second core dump is attached. Unable to mount shared file systems on the clients. Please help.

# grep -v "^#" /etc/rc.config.d/nfsconf

NFS_CLIENT=1
NFS_SERVER=1
NUM_NFSD=4
NUM_NFSIOD=4
PCNFS_SERVER=0

LOCKD_OPTIONS=""
STATD_OPTIONS=""
MOUNTD_OPTIONS=""
AUTOMOUNT=1
AUTO_MASTER="/etc/auto_master"
AUTO_OPTIONS="-f $AUTO_MASTER"
START_MOUNTD=1


Used to work fine before applying required patches for Oracle 9.2 & OVOU 8.0. Is there any patch missing?

[TIMOTHY J. REGAN II]

Ramassh,

Stop the client, server then the core. Start the core, server then the client.

If still a problem reboot the server. If it fails after that then I would suggest you take a look at all of the patches you just installed and make sure you are not missing any dependencies. Dependencies can be identified in the patch text file or easily on the web at he ITRC.

Let us know how it goes....

[Dave Olker]

Hi Ramassh,

> Used to work fine before applying required
> patches for Oracle 9.2 & OVOU 8.0.

Exactly which patches did you install?

> Is there any patch missing?

Hard to tell without an swlist output. Can you provide "swlist -l product" output so we can see which patches you have installed?

Thanks,

Dave

[Ramassh]

This problem occurs even during reboot. There are similar errors in the rc.log:

Start NFS core subsystem
Output from "/sbin/rc2.d/S400nfs.core start":
----------------------------
starting NFS CORE networking

starting up the rpcbind
/usr/sbin/rpcbind
/sbin/rc2.d/S400nfs.core[242]: 834 Bad system call(coredump)
Error: NFS nfskd NOT started
"/sbin/rc2.d/S400nfs.core start" FAILED

.
.
.

Start NFS client subsystem
Output from "/sbin/rc2.d/S430nfs.client start":
----------------------------
starting NFS CLIENT networking

starting up the rpcbind
rpcbind already started, using pid: 830
starting up the BIO daemons
/usr/sbin/biod 4
/sbin/rc2.d/S430nfs.client[173]: 855 Bad system call(coredump)
FAILURE CODE: 140
starting up the Status Monitor daemon
/usr/sbin/rpc.statd
starting up the Lock Manager daemon
/usr/sbin/rpc.lockd
starting up the Automount daemon
/usr/sbin/automount -f /etc/auto_master
mounting remote NFS file systems ...
mounting CacheFS file systems ...
"/sbin/rc2.d/S430nfs.client start" FAILED

# ps -ef | grep rpc
root 861 1 0 08:20:13 ? 0:00 /usr/sbin/rpc.statd
root 867 1 0 08:20:13 ? 0:00 /usr/sbin/rpc.lockd
root 1260 1 0 08:20:23 ? 0:00 /opt/dce/sbin/rpcd
root 2112 1 0 08:21:09 ? 0:00 /usr/sbin/rpc.mountd
root 2584 1 0 08:23:08 ? 0:00 /usr/sbin/rpcbind
root 4541 2504 1 08:46:49 ttyp1 0:00 grep rpc


There were a lot of patches applied to bring the system up-to-date to get Oracle & OVOU installation going. I downloaded all the patches from the HP patch site. I can't see any OS patch missing when I run the patch assessment (only NNM patches, PHSS_34870 & PHSS_36385). I have attached the 'swlist -l product' output.

I noticed a similar error in the title of a document when I did a search on ITRC, which I am unable to read, because it is only available for customers with support agreement:
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c01022075-1
We are software developer partners (DSPP) and have no support agreement. Does that doc have the magic answer?

Thanks

[Dan Copeland · Accepted solution]

check if you have have nfs_server in
/stand/system. Solve the problem by rebuilding the kernel with nfs_server.

#grep -i nfs /stand/system
nfs_client
nfs_core
nfs_server
nfsm

[Ramassh]

Dan you are the man. Thanks a lot.

Here are the commands I used to fix this problem:

# grep -i nfs /stand/system <----- note nfs_server is missing
nfs_client
nfs_core
nfsm
remote_nfs_swap 1
# cd /stand
# cp vmunix vmunix.old
# cp system system.old
# cd build
# /usr/lbin/sysadm/system_prep -s system
# vi system <------ included nfs_server between nfs_core and nfsm
# mk_kernel -s system
# cp vmunix_test /stand/vmunix
# cp system /stand
# grep -i nfs /stand/system
nfs_client
nfs_core
nfs_server
nfsm
remote_nfs_swap 1
# reboot -q