Hostname disappeared...

[TWBSupport]

OK - I'm back. Now that I can actually access the console after a new i/o board was installed, my server boots with no hostname. If I go into SAM to take a look at the NIC's, I get the following "Your system name is invalid.....A screen will appear to reset the system name" I hit OK & SAM closes. Same thing happens when I try to access hosts via SAM. uname -a gives me hostname of unknown. All my data is there & the drives will mount by using mount -a, but will not mount automatically. Any idea on how to get my server to know who it is again? HELP! Thanks in advance.

[Rick Garland]

Can you run the set_parms command?

/sbin/set_parms hostname <$HOSTNAME>

man set_parms

This will modify the /etc/hosts file. Have you looked in this file to see? Does it still exist?

[Pete Randall]

Run /sbin/set_parms hostname. You may want to also run /sbin/set_parms ip_address just to make sure. After each one it will ask if you want to reboot. Reply no after hostname and yes after ip_address.


Pete

[Mel Burslan]

initial suggestion is to run the utility called

set_parms

it will ask you the information you need to enter interactively, like hostname, timezone, date/time, root password, ip_addresses.

Answer these and let the server reboot. If it recovers, fine. If it does not, let us know the error messages you are getting at the boot time for further help.

[Devender Khatana]

Hi,

Can you see wheather /etc/hosts has correct entries & your /etc/rc.config.d/netconf has hostname set properly. If both are correct you can check /etc/rc.log for errors which causing it to not getting set.

HTH,
Devender

[TWBSupport]

Yes, I checked /etc/hosts as soon as SAM -> hosts would not let me update it. It's fine.

I have run set_parms for hostname & ip address & after each configuration it never asked me to reboot. So I rebooted anyways, uname -a came back with the hostname but SAM still errors out with the same error 'system name invalid'. I was thinking maybe it had something to do with the NIC, lanscan comes back with the NIC up. I then rebooted AGAIN & it lost the hostname config once more. Any other ideas? There are no errors on boot up to give you, no errors are coming up in the syslog.

[Devender Khatana]

Hi,

It could be something that is stopping your names from getting resolved. How does names are resolved ? Check /etc/nsswitch.conf & resolv.conf files to find this out.

Try coping nsswitch.file in /etc to nsswitch.conf if network sources used for resolution are temporarily unavailable.

HTH,
Devender

[TWBSupport]

resolv.conf & nsswitch.conf are both there. I can set_parms hostname & ip_address & if I immediately go into SAM, I can get into NIC Interface, BUT my NIC's no longer show up & SAM tells me that it can not find any NIC's & to install them. If I do a lanscan, all 3 LAN Interfaces show up. Also lanadmin shows this too. If I bounce the server, all the set_parms that I just did do not come back....

rc.log only shows shutdown messages, it's not showing startup messages, so that's not helping me at all. I think tomorrow, I will switch out our NIC & see what happens. Please keep the ideas coming. THank you all for your time.

[Devender Khatana]

Hi,

Post the contents of /etc/nsswitch.conf, /etc/resolv.conf, /etc/rc.config.d/netconf & /etc/hosts files.

Is your server accessible on network when hostname is not set ?

HTH,
Devender

[Rick Garland]

Was SAM in use when system hard crashed?

Look in the SAM log to see if any clues are present.

/var/sam/log/samlog

[Mel Burslan]

can you run this command for all 3 interfaces

ifconfig lanX

where X is changing according to your interface instances. Can you see your ip addresses ?

Actually can you post the output of the commands ?

Also could you please provide the contents of
/etc/rc.config.d/netconf
file ? Looks like you are having some sort of network trouble and you may have lost hardware of an interface.

[TWBSupport]

Because of these issues, the system in not on the network, so I can't copy the files for you all. All the files are properly setup, they are the original files that it was working on from day one.

I did however take a look at the SAMlog & this error is constant on it since the problem started..

rpc_server_use_protseq[_ep] failed with message "Protocol sequence not supported (dce/rpc)" Protocol sequence was ncacn_ip_tcp. Max calls was 20. End point was 2012092968. ALocation:agent.c.222^AError Code: -2007.

I haven't search it yet on here to see if that would lead me anywhere. Mel, I haven't had a chance to run your suggestions, I will post back with that info.

Thanks again to you all

[TWBSupport]

Mel -
when I try to run ifconfig lan0, ifconfig lan1, ifconfig lan2. Each time I get the following error..

ifconfig: socket: operation not supported

[Devesh Pant_1]

Post the output of
ioscan -funC lan
and netstat -in
and lanscan

please check the /etc/rc.config,d/netconf accordingly

thanks
DP

[Jino.P.V]

Hi Belynda,

I think the base problem is with the hostname itself. Could you please edit the /etc/rc.config.d/netconf and set the hostname.
Then you can use setuname -n "hostname"

Then the base problem wil be solved.

Hope this will help a bit..

Jino

[TWBSupport]

Problem fixed just by recreating the netconf file. Startup files were not starting up. Netconf is exactly what was there, but for some reason, just stopped being recognized.... Very odd. Thank you all for your help.