topic Re: Could not connect to host swinstall in Operating System - HP-UX

Could not connect to host swinstall

Michael Kurczewski — Sat, 04 Feb 2006 18:30:31 GMT

I just performed a cold install of hp 11.11i and believe I have the basics setup. I can ping the server, telnet into the server, access the Internet and resolve the hostname in DNS.

I have 5 cd's in the pack. I installed the core cd's (2 of them) and have (3) application cd's. I assume I have to install the applications such as gnome, webmin, apatche and other software packages from those three cd's. When I put the first application cd in and type swinstall I get the 'cannot connect to host' error message. The target host has the correct server name and the root path of /
I have tried to make the root path /tmp and it says cannot connect to host.
I have also read the groups and executed the #/usr/sbin/swagentd -r command to no avail.

Any ideas?

Mike

Re: Could not connect to host swinstall

Michael Kurczewski — Sat, 04 Feb 2006 18:34:33 GMT

I mean the #/usr/sbin/swagentd -r executed properly but did not solve the problem.

Re: Could not connect to host swinstall

Michael Denney — Sat, 04 Feb 2006 20:04:20 GMT

Try looking in the sw log files.

/var/adm/sw/swinstall.log
/var/adm/sw/swagent.log

Post the logs here would help us troubleshoot.

Re: Could not connect to host swinstall

Devender Khatana — Sat, 04 Feb 2006 21:44:48 GMT

Hi,

Try these steps

#mount /dev/dsk/cxtydz /cdrom
(Where /dev/dsk/cxtydz is the device file for CD/DVD-ROM and /cdrom is a created mount-point.)

From bdf output insure that cdrom is mounted. Also try listing contents of /cdrom. Then give

#swinstall -s /cdrom

HTH,
Devender

Re: Could not connect to host swinstall

Michael Kurczewski — Sat, 04 Feb 2006 22:54:13 GMT

Here is the swinstall.log file I have attached it.

Re: Could not connect to host swinstall

Michael Kurczewski — Sat, 04 Feb 2006 23:14:17 GMT

Here is the swagent log.

Re: Could not connect to host swinstall

Michael Denney — Sun, 05 Feb 2006 00:52:51 GMT

Looks like there is a problem with your networking. Your other software was installed using loopback, indicating your primary lan is either down or not configured correctly.

What is the output of:

1. ifconfig
2. lanscan
3. ping brandy

You could also swinstall to loopback instead of brandy. "swinstall @ loopback". (syntax might be wrong, I don't have access to hpux machine at the momment)

Re: Could not connect to host swinstall

Fayez — Sun, 05 Feb 2006 04:06:37 GMT

Hi,

Look at the file /etc/hosts and be sure there is no duplicate entry for brandy host, with one of them associated with disabled Ethernet card....

Re: Could not connect to host swinstall

Darrel Louis — Sun, 05 Feb 2006 05:59:57 GMT

Mike,

Check if your hostname i9s resolved correctly.

Also check the nsswitch.conf file, the host line.

nslookup
nslookup

Darrel

Re: Could not connect to host swinstall

Michael Kurczewski — Sun, 05 Feb 2006 10:00:04 GMT

here is my hosts file it looks ok to me:

198.109.197.23 dns1.amsdevelopers.com dns1
192.168.100.2 brandy
127.0.0.1 localhost loopback

I can't ping brandy but I can ping the ip address.

Here are the results of lanscan:
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
10/12/6 0x001083B9E3ED 0 UP lan0 snap0 1 ETHER Yes 119
10/16/8 0x080009D5C045 1 UP lan1 snap1 2 ETHER Yes 119
#

ifconfig gives the following for lan1 lan0 is not configured.

lan1: flags=843
inet 192.168.100.2 netmask ffffff00 broadcast 192.168.100.255
#

nslookup the ip address gives:

# nslookup 192.168.100.2
Name Server: dns1.amsdevelopers.com
Address: 198.109.197.23

Trying DNS
Trying NIS
looking up FILES
Name: brandy
Address: 192.168.100.2

nslookup brandy gives:

# nslookup brandy
Name Server: dns1.amsdevelopers.com
Address: 198.109.197.23

Trying DNS
Trying NIS
looking up FILES
Name: brandy
Address: 192.168.100.2

Mike

Re: Could not connect to host swinstall

Fayez — Sun, 05 Feb 2006 10:10:48 GMT

Hi ,

Can you attache the file nsswitch???

Re: Could not connect to host swinstall

Fayez — Sun, 05 Feb 2006 10:17:08 GMT

And the file resolv.conf too

Re: Could not connect to host swinstall

Michael Kurczewski — Sun, 05 Feb 2006 11:14:11 GMT

It appears taht I don't have the nsswitch or resolve.conf files. I looked in the /etc directory for them but don't have them.
Mike

Re: Could not connect to host swinstall

Fayez — Mon, 06 Feb 2006 02:33:41 GMT

Hi,
Any way, the resolv.conf file needed for tell the system which domain to look in, and the name server to use in the search
For example your domain is amsdevelopers.com, and then the name server is dns1.amsdevelopers.com.

Example of resolv.conf file:
domain dns1.amsdevelopers.com amsdevelopers.com
nameserver 198.109.197.23

And you you have to qualify your hostname in the hosts file, like:
192.168.100.2 brandy.amsdevelopers.com brandy

And the nsswitch.conf it is important to tell the system where to look for host names and other network services, there will be entry like:

hosts: dns files
If you don't have this file you can copy it from /etc/nsswitch.hp_defaults to /etc/nsswitch.conf

Refer to HP document Installing and Administering Internet Services

Any way, I believe your problem is with the hosts file it self, and the entry for the localhost in the hosts file must be the first entry, and again be sure there is no double entry for host brandy.

Re: Could not connect to host swinstall

Michael Kurczewski — Tue, 07 Feb 2006 15:53:05 GMT

This is a sandbox system I am installing. Would it be easier to simply reinstall the os and enable both network cards? I have a 10/100 and a 10 mb. card in the machine. I did not set up the 10 mb. card. I think that may be causing the problem with the loopback, it may be picking up the other card as that is lan 0 and the 10/100 is lan 1.

Mike

Re: Could not connect to host swinstall

jamesps — Tue, 07 Feb 2006 15:57:55 GMT

Just copy over the /etc/nsswitch.compat to /etc/nsswitch.conf then kill the swagentd and restart it again. This should do the trick. This is typical for a new installation and it did solve it for me every time :) Good luck!