swinstall doesn't work after changing hostname

[Ceesjan van Hattum]

Hi,
I've changed a machine (hpux11.11) its hostname by using set_parms.
Now, a few days (and reboots) later, i'd like
to install some software.
Unfortunately, swinstall cannot contact target.
It complains about RPC (remote procedure call), but it just the localhost...
I already changed the /var/adm/sw/target_hosts
and restarted swagentd... but no luck there..

I shouldn't be difficult, maybe you know the trick?

Regards,
Ceesjan

[Scot Bean · Accepted solution]

swinstall uses network / LAN communication even for one machine. If the network parameters are not configured correctly, this can happen.

I have found that using set_parms to alter a machine that has been up and running does not change everything it should. I believe this command is intended to be used only during initial machine boot/setup, not later on.

Stuff to try:
- "hostname" and "uname â a" output match?
- /etc/hosts file look OK?
- nslookup match nslookup ?
- also examine /etc/rc.config.d/netconf, look OK?

Basically there is a hostname / address conflict on your machine that you need to find & fix for swinstall to work.

[Ceesjan van Hattum]

Thanks,
I had a old and invalid ipadress in my hostfile. Correct resolving my own ipaddress did the trick.

Greetings,
Ceesjan

[Victor Fridyev]

Hi,

I agree with Scott that you have a conflict in the hostname setting. In order to resolve it, check the following:

the hostname setting in /etc/hosts;
network settings in /etc/rc.config.d/netconf;
the order of name resolution in /etc/nsswitch.conf.
I'd recommend the following order in /etc/nsswitch.conf:
hosts: files [NOTFOUND=CONTINUE] dns
commands nslookup hostname and nslookup ipaddress should give correct responce

HTH

[Steven Brown_1]

hostname is embedded in the kernel. Use SAM and make a small change to a kernel parameter and then reboot and rebuild the kernel. Once the box comes up, then swintall will be using the new hostname. It will then work correctly.