boot hang at NFS core

[Larry Basford]

I am moving fron a K370 to another K370 different IP and name only. On last reboot from ignite from tape the system hangs here ? will not go to init 3
Start NFS core subsystem ..................................

There was a remote mount to the old system and exports from the ignite tape. I went in single user and removed /etc/exports file contense.

[Shannon Petry]

The exports file only controls file systems shared from the machine it resides on. Your hang at NFS Core is prior to the exportfs occuring anyway.

First, make sure the IP was completely and correctly changed. I.E. Make sure that /etc/hosts is correct and that /etc/rc.config.d/netconf is correct, has proper netmask and broadcast address if assigned, and that no bogus route's are in the file.

It will help to comment out any NFS mounts in /etc/fstab, and also check for the automounter to ensure it's not trying to mount things it can no longer find.

Regards,
Shannon

[Sajid_1]

Well, I would remove NFS services from starting while system boots and when the system comes up normally, I will check and see if I can start the NFS core manually:

# /sbin/init.d/nfs.core start

I could then check the log files and see if there is some error.

[Larry Basford]

When I remove NFS core start
It fails next at
Start NIS client subsystem

If I remove this also what do I do? What logs will I need to look at?

The IP hostname and mask are good. The interface will ping OK

[Christopher McCray_1]

Hello,

If you haven't already thought of this/done so, edit /etc/rc.config.d/nfsconf and set the NFS_SERVER, NFS_CLIENT, AUTOMOUNT and START_MOUNTD all to 0.

Does this help? Hope so.

Chris

[Sajid_1]

Hi again:

There is a configuration file in the directory /etc/rc.config.d called 'nfsconf'. Edit this file and make NFS_SERVER=0 and NFS_CLIENT=0. By doing this will disable NFS services to start automatically while system starts. You may read the file for more descriptions.

Once everything is resolved turn these setting back to ON (set 1 instead of 0). The log file which you may have to look - /etc/rc.log, /etc/rc.log.old, /var/adm/syslog/syslog.log

rgds,

[John Dvorchak]

When you were moving to the new K370 did you use the old K370's ignite tape? If so did you run an Interactive INSTALL session? When you clone a system and change the name the easiest way is to run the recovery/install in interactive and select "Install HPUX" on the first screen then take the "Advanced Install" on the second screen and be sure to change the name, IP address, root password etc. If you didn't follow those steps then I'll bet your /etc/hosts file has the old system's name and IP address and the new system is not listed. Your problem is proabaly caused from the server not being able to resolve it's own name. I like to put the local servers FQDN and alias as the first data line in /etc/hosts. Reboot and bring it up in single user mode and make sure you can resolve your own name. If that is not possible and you are going to try to start nfs manually, the you should see it hang again if the system can't resolve it's own name. Good luck