nfs and inet.d not being started at boot up

[Chet Woods]

I have just changed the IP address of my server, (10.20) through SAM and now when I reboot the server is hanging at nfs.client and inetd. Is there something that could have changed in those configurations when I changed the IP's?

[Rick Garland]

You changed the IP. Does the system resolve?
Do the nslookup by name and by IP address. Is it clean?

[Kofi ARTHIABAH]

Yes, get the machine to single user mode and then edit your /etc/hosts file so that your current host has your new IP address... you might also want to confirm that in your /etc/rc.config.d/netconf that your IP addresses and routes are in order... you could break out of the hang state with the ctrl+b rs sequence.

good luck

[CHRIS_ANORUO]

Run ifconfig once the IP address of you is changed and update your /etc/rc.config.d/netconf and /etc/hosts files, before rebooting the server.

[Antoanetta Naghiu]

Check /etc/rc.config.d/netconf file if reflect the modification. (IP-address, in which interface, route, defaultgateway,etc).
more /etc/rc.log and see what error did you get durring the execution of nfs.client and inetd.
Did nfs.core started ok? Are nfs daemons running (nfsd and biod)?
Come back with more details.

[Chet Woods]

I have confirmed in netconf, hosts, and by issuing the ifconfig command that the IP is correct. I am attaching the rc.log for you to look at.

[Rick Garland]

One thing I see is that the NIS is not configured correctly. Are you running the NIS services without defining the master and/or slave server(s)?

[Vikas Khator]

Hi,

Check your /var/yp/secureservers and /var/yp/securenets file.

Regards,
Vikas

[Kofi ARTHIABAH]

It looks like its failing on automount... can you check the config/setup of your /etc/auto_master file. You might also want to check your /etc/nsswitch.conf file; plus, I note that sendmail is complaining about not having a fqdn - fix this by editing your /etc/hosts file and making sure that you have the fqdn in addition to the short name of your server listed in there.

[Antoanetta Naghiu]

NIS messages are ok, since you are not using NIS.
The problem is with automount. Are you using it? Check the automount specific files. There it might be a reference to the old IP.
As said the very first post just run nslookup to check how names got solved. Using DNS, using /etc/hosts? Ensure those reflect the change properly

[Chet Woods]

We are not using DNS, not on our "remote" servers anyway (using hosts - which has been updated). All home office servers use DNS. /etc/auto_master looks correct also. So is there something I need to take out of the startup scripts?

[Antoanetta Naghiu]

If the box used to run before this change and the IP is only one thing that has been changed, should be able to run after.
So, you are solving hosts by /etc/hosts. /etc/hosts is ok, I mean reflects the new ip for the localhost.
Wait a second. Do ls -al /etc/hosts How are the permission on the file (should be read for everyone).
If this is ok, go and check/modify the /etc/hosts on the remote boxes that have nfs exported file systems to this one.
run nslookup to those boxes....

[Rick Garland]

Check the /etc/nsswitch.conf file.
You may want ot remove the not start the NIS services or configure them correctly. DNS, if not being used, don't start it.

The NIS and DNS startups are in the /etc/rc.config.d/namesvrs file.

The automount start is in the /etc/rc.config.d/nfsconf file.

[Chet Woods]

Ok I have verified in the /etc/rc.config.d/nfsconf file that automount=0. It was set at 1. Anything I should be weary of rebooting this server? Remember it is at a remote site. Thanks.

[Rick Garland · Accepted solution]

You indicated earlier that the IP was changed. Do you resolve this system by name and IP? You turned off the automount start, if not using DNS did you turn that off as well? Is the nsswitch.conf file set OK? It would be nice if you had a console so you can see the messages as the system boots up.