Hostname trouble

[Steven E. Protter]

Shalom,

A bit out of the box, but perhaps a run at set_parms might clean things up.

Running the command without options will display options. I suggest

set_parms ip_address
set_parms hostname
set_parms addl_network # for the second card if active.

HP-UX does not much like two NIC cards on the same network.


SEP

[Ron Irving]

Well, my netconf looks exactly like suggested by TTYl. I am perplexed beyond belief. Using putty, I attempted to run set_parms, but it just hangs there. Can't telnet in because of the original problem. Yikes!!!

[TTr]

I assume you have putty connecting to the console.

> Still comes up as 'unknown

Is this at the hostname prompt? Did the rc sequence start and completed?

Do some sanity checking. Check /etc/hosts and netconf again so that they are in agreement. Look in rc.log and syslog.

Verify there is no other host with the same IP as this one. (ping the IP from another host.

Check the name resolution for N4000 from within the N4000 and from another host.

[James R. Ferguson]

Hi Ron:

Verify again that your '/etc/rc.config.d' directory only contains appropriate files.

If you look at the script, '/etc/rc.config' you will see that it *is* ok to have backup file copies as long as their names contain [.,~#]. That is, 'netconf.old' is an acceptable backup but 'netconfold' is not.

Verify the contents of this directory by doing:

# for FILE in $(ls /etc/rc.config.d/*)
> do
> ls ${FILE}
> . ${FILE}
> done

This will source (read) every file as if the nomral startup sequence is running. The action will stop if there is any file with syntax errors and the 'ls' will identify the offender.

You can also see from a 'ls -ul' which files are not sourced, because they are regarded as backup copies and are skipped.

Regards!

...JRF...

[Ron Irving]

Well, my window of opp ran out. Looks like I'll have to deal with it tomorrow night. Everything looks good, though, from your advice.

I have to dream about this now...yikes!!

[Dennis Handly]

>JRF: If you look at the script, /etc/rc.config you will see that it *is* ok to have backup file copies as long as their names contain [.,~#].

Why bother with such a complex naming scheme?
Simply create a sub or parallel directory named BACKUP and move the old file there, with their original names.

There is also such a thing as RCS.

[F Verschuren]

to check if yo have anny other files that sets the hostname please use:
grep HOSTNAME /etc/rc.config.d/*
this must only replay your netconf file.
All other this must be (re)moved ore reconfiggured.

[Steven E. Protter]

Shalom,

Thanks to Dennis for pointing out that feature.

I still prefer moving the backups out of /etc/rc.config.d

set_parms hanging is very problematic.

At this point, I'd move netconf out, take the system to run level 2 and run set_parms from the console.

I suspect now a hardware problem is interfering with normal systems operations.

SEP

[Ron Irving]

Good morning!!

Well, the system is up now. The set_parms hung only when attempting it from an ssh console, (putty.) When I get another window, I will attempt your idea Stephen. That is removing netconf, and jumping down to run level 2, and running set_parms again. Right now, I have removed all instances of netconf, and left just the one there. Hopefully I'll get another window of opp soon. You are right...it's affecting the application now.

[Ron Irving]

I am attaching the latest netconf and /etc/hosts file. Is there anything in there I may have missed?

Thanks

first netconf

[Ron Irving]

now /etc/hosts

thanks again!!

[Robert-Jan Goossens]

Ron,

Your netconf and hosts file look fine.

---
I have removed all instances of netconf, and left just the one there
---

Remove (move) all backup files from your /etc/rc.config.d/ to a backup folder, not just the old netconf files.

Best regards,
Robert-Jan