How to start the NFS server on HP-UX 11.31 at start up (boot up) automatically

[senthil_kumar_2]

Whom question i have to answer to?

[James R. Ferguson]

Hi:

> Whom question i have to answer to?

Since Dave is _the_ _expert_ and since Dave asked the last set of questions of you, in my opinion you need to respond to his queries!

Regards!

...JRF...

[Sunny123_1]

Hi

Reply on Dave Olker's post.


Regards
Sunny

[Steven Schweda]

> I am having the same [...]

> Dec 21, 2009 19:12:14 GMT 8 pts


> Whom question i have to answer to?

Uh, LOOK FOR THAT DATE AND TIME?

LOOK FOR THIS CHARACTER: "?"?

Rent a brain somewhere?

[Steven E. Protter]

Shalom,

Why JRF's queries are important.

Configuration files backed up in /etc/rc.config.d with the wrong name get read twice, making the configuration impopssible to work.

Consider turning on logging in the startup scripts to see why they fail.

set -x

a few echo statements to try and diagnose the problem.

Cuplicates in rc.config.d is a very common issue for failure to start up. Your symptoms point to this as a possible cause.

SEP

[senthil_kumar_2]

Hi All,

I have done all the steps suggested by Dave.


1) My first question is what version of ONCplus are you running? Issuing the command:

# swlist ONCplus
# Initializing...
# Contacting target "emdlaghpvm05"...
#
# Target: emdlaghpvm05:/
#

# ONCplus B.11.31.06.01 ONC+ 2.3
ONCplus.NFS B.11.31.06.01 ONC/NFS; Network-File System,Information Services,Utilities



2)Once you're running a version of ONCplus that includes debug KLM logging (we added that feature in ONCplus B.11.31.01), I'd recommend you enable debug KLM logging via the command:


# kctune klm_log_level=9
==> Update the automatic 'backup' configuration first? yes
* The automatic 'backup' configuration has been updated.
* Future operations will update the backup without prompting.
* The requested changes have been applied to the currently
running configuration.
Tunable Value Expression Changes
klm_log_level (before) 0 Default Immed
(now) 9 9


3)Once you've enabled debug logging, try the following:

# /sbin/init.d/lockmgr stop
# /sbin/init.d/lockmgr start


Now core files have been created.


I am able to find below shown log error in /var/adm/syslog/syslog.log

Jan 4 13:33:19 emdlaghpvm05 /usr/sbin/rpc.lockd[14442]: Cannot get address for transport udp host \1 service lockd
Jan 4 13:33:19 emdlaghpvm05 /usr/sbin/rpc.lockd[14442]: Cannot establish NLM service over /dev/udp: transport setup problem.
Jan 4 13:33:19 emdlaghpvm05 /usr/sbin/rpc.lockd[14442]: Cannot get address for transport tcp host \1 service lockd
Jan 4 13:33:19 emdlaghpvm05 /usr/sbin/rpc.lockd[14442]: Cannot establish NLM service over /dev/tcp: transport setup problem.
Jan 4 13:33:19 emdlaghpvm05 /usr/sbin/rpc.lockd[14442]: Could not start NLM service for any protocol. Exiting.

[Steven Schweda]

> I have done all the steps suggested by Dave.

This must be some new meaning for "all".

Can you see the difference between these?:

> Dec 19, 2009 23:17:30 GMT 9 pts

> Dec 21, 2009 19:12:14 GMT 8 pts


> Now core files have been created.

Were you expecting someone else to run a
"file" command to see what made them?


I give up.

[senthil_kumar_2]

Hi All,

I have solved this issue.

As is appears to be a typo in the /etc/nsswitch.conf file, more specifically, the services line, I am closing this thread. the rpc.lockd daemon started up as soon as I corrected that line.


Ex:

# vi /etc/nsswitch.conf


services: nis [NOTFOUND=return] files ---> old entry

services: files ---> new entry



Now "rpc.lockd" is starting automatically while starting lockmgr.

[senthil_kumar_2]

I am closing this thread