topic Re: Hostname and other netconf parms corrupt in Operating System - HP-UX

Hostname and other netconf parms corrupt

Scott McDade — Mon, 30 Jan 2006 18:30:22 GMT

Hello:

I am trying to get a 11.11 system onto a network and I am running into some strange behavior.
I have validated all the network setting are correct (ie. hostname, ip, gw, ..). I have tried using
sam, set_parms and even copying the netconf, hosts and resolv.conf files over from another machine.

The end result is I can't get CDE to load. Trying to see if hostname loaded from the netconf file
I tried the $hostname command and in comes back unknown. I then noticed that the OPERATING_SYSTEM parm
in the netconf file was set to -t. I am not sure how that got changes. So I changed it back to
HP-UX. I then reboot and it gets set back to -t again.

I am not sure what could be causing this but it is preventing me from getting the workstation onto the
network.

I have included the /etc/rc.log file as well.

One other thing I noticed when comparing the HOSTNAME accorss several of my 11.11 systems is some have the hostname parm
in "" and some don't. I am not sure if that makes any differnce.

# IMPORTANT: for 9.x-to-10.0 transition, do not put blank lines between
# the next set of statements

HOSTNAME="mtvhp08"
OPERATING_SYSTEM=-t
LOOPBACK_ADDRESS=127.0.0.1

Any help you can provide I would appreiate.

-Scott

Re: Hostname and other netconf parms corrupt

Steven E. Protter — Mon, 30 Jan 2006 18:38:22 GMT

Shalom Scott,

1) Make sure the root fs is not near or at capacity. If this is teh case it can cause problems with the configuration files.

2) If the files are really corrupt, they probably should be restored from backup or set_parms scripts should be used to re-create them.

3) Note that hostnames can not exceed 8 characters unless you are running 11.23 with a special enhancement installed.

I don't think the quotes make any difference.

SEP

Re: Hostname and other netconf parms corrupt

Scott McDade — Mon, 30 Jan 2006 20:33:15 GMT

SEP:

I have restored them from both backup via set_parms. The problem is once I restore them and reboot something is is overwritting the netconf file. I am not sure if it is kept in memory and overwritten up reboot.

I have even gone in single user mode and replaced the netconf, resolv.conf and hosts files via and then rebooted and the OPERATING_SYSTEM parm still gets changed back to -t.

Has anyone ever seen this happen?

Re: Hostname and other netconf parms corrupt

Scott McDade — Mon, 30 Jan 2006 21:44:11 GMT

Hey all, I have included the rc.log file as well just in case there is something in there that I missed.

-Scott

Re: Hostname and other netconf parms corrupt

RAC_1 — Mon, 30 Jan 2006 21:52:08 GMT

Check if you any multiple files for netconf, such as netconf.bak, netconf.orig etc. The /etc/rc.config.d/ directory shoyld have only the configuration files and nothing else.

Re: Hostname and other netconf parms corrupt

Scott McDade — Mon, 30 Jan 2006 21:57:54 GMT

RAC:

Thanks, I will take a look, I know I have a home.netconf file in the /etc/rc.config.d/ path.

Re: Hostname and other netconf parms corrupt

Scott McDade — Tue, 31 Jan 2006 11:10:00 GMT

Cleaned out /etc/rc.config.d of all reduntant files (ie. .. home.hosts or bkup.netconf).

Made sure that the netconf file setting for OPERATING_SYSTEM=HP-UX and rebooted.

Came up in single user mode and checked it. Everything looked fine,

Init level 1 the OPERATING_SYSTEM parmeter was overwritten to -t in the netconf file.

Can anyone explain this or has anyone seen this? PLEASE?????

Where could it be getting this parm from?

Re: Hostname and other netconf parms corrupt

Sameer_Nirmal — Tue, 31 Jan 2006 13:46:29 GMT

Hi,

Can you check if this command shows HP-UX ?
# uname -s

Also check # uname -a

Re: Hostname and other netconf parms corrupt

Scott McDade — Tue, 31 Jan 2006 14:11:22 GMT

Thanks...for the reply.

When I do the uname -s gives me the -t. And the uname -a returns -t unknown then some lic info...

Atleast it is consistant.

Re: Hostname and other netconf parms corrupt

James R. Ferguson — Tue, 31 Jan 2006 14:50:20 GMT

Scott:

One thing to try is to 'vi' the '/etc/rc.config.d/netconf' file. Make sure that 'vi' doesn't "complain" about the file format in any way.

You can also start with a virgin copy of the file and manually configure your hostname and network:

# cp -p /usr/newconfig/etc/rc.config.d/netconf /etc/rc.config.d/netconf

Having done this copy, either manually edit the file or try running '/sbin/set_parms' again.

Regards!

...JRF...

Re: Hostname and other netconf parms corrupt

Jeff Schussele — Tue, 31 Jan 2006 14:52:42 GMT

Hi Scott,

I've seen this before.
It's not the netconf that's causing this.
It's either another conf file or a startup script.
So do this

grep -l HOSTNAME /sbin/init.d
and
gerp -l HOSTNAME /etc/rc.config.d

Then check all the returned filename.
You'll find your culprit.

HTH,
Jeff

Re: Hostname and other netconf parms corrupt

Jeff Schussele — Tue, 31 Jan 2006 14:55:51 GMT

Of course that should have been....

grep -l HOSTNAME /sbin/init.d/*
and
gerp -l HOSTNAME /etc/rc.config.d/*

Cheers,
Jeff

Re: Hostname and other netconf parms corrupt

James R. Ferguson — Tue, 31 Jan 2006 14:58:26 GMT

Hi Jeff:

"gerp" = dyslexic "grep" ? :-))

Regards!

...JRF...

Re: Hostname and other netconf parms corrupt

Jeff Schussele — Tue, 31 Jan 2006 15:03:28 GMT

Hi JRF,

LOL!!!!
Well at least I was consistent.
Actually, I was lazy.
I copy/pasted from my first post.
Funny thing is that's probably the most frequent typo I make.....

Cheers my friend,
Jeff

Re: Hostname and other netconf parms corrupt

Sameer_Nirmal — Tue, 31 Jan 2006 15:05:21 GMT

Hi,

As per the "uname" output you said, it seems that the hostname is "unknown" besides "-t" for OS name.
Set using
#setuname -s HP-UX -n

Ensure you have OPERATING_SYSTEM=HP-UX in
"netconf" file.

Start the net service using
# /sbin/init.d/net start
If you face problem starting net service, yo may have to reboot the system.

Be aware that only script /sbin/init.d/hostname assigns system names. Ensure you don't have any other script which alters these names.