SAM -> To install application with swinstall, HP OpenView is required, why?

[GTI]

Hi, I'm trying to install a depot file with SWInstall, but when I mark the software to install and run Action Menu->Install(analizes), swinstall require to specify a target path, so running Action Menu->Change Target and enter the location of the target, eg. /opt and press OK, a message is shown: "... to attempt this action ... HP OpenView must be installed". What I have to do now? I don't have HP OpenView to install.

Thanks...

Leandro.

ps: I'm using HPUX 10.20

[A. Clay Stephenson]

Hi,

I think the message means just what it says. You seem to be installing a product which has a dependency upon an Openview Product. What are you trying to install?

Clay

[James R. Ferguson]

Hi:

This is a bogus message. Make sure that you have your hostname defined in /etc/hosts. Make sure, too, that you have the 'localhost' declaration for '127.0.0.1'.

'swinstall' and the 'swagentd' daemon are fussy about network issues. Try this to restart before installing:

# swagentd -r

...JRF...

[GTI]

I'm trying to install the GD lib. I checked the /etc/hosts and everything is right. I ran swagentd -r but didn't work.
Recently I have to reinstall the HPUX 10.20 and before this, swinstall worked well.

What I have to do?

Leandro.

[James R. Ferguson]

Hi again:

Try running 'nslookup' using your hostname. See if the correct IPAddress is returned. If it is *not*, then temporarily rename /etc/resolv.conf to something else and restart the 'swagentd' daemon as I indicated above. Once again, 'swinstall' is very fussy about network issues.

...JRF...

[A. Clay Stephenson]

Hi,

Sorry, I didn't read your original posting closely enough. This is definitely a name resolution type error. Since you have done an OS reinstall you may not have applied the any General Release patchsets and there have been quite a few swagentd patches. You probably also need to apply the latest cumulatative swagentd patches (from the command line).

Clay

[GTI]

Hi... I run nslookup and I got the following:

# nslookup strauss
*** Can't find server name for address THE_IP_ADDRESS_OF_MY_DNS_SERVER: Non-existent domain
*** Default servers are not available
Using /etc/hosts on: strauss

looking up FILES
Name: strauss
Address: THE_IP_OF_strauss

but if I ping to the IP_ADDRESS_OF_MY_DNS_SERVER is ok.

and now?

Leandro.

[GTI]

... end the named of MY_DSN_SERVER is running propertly...

Leandro.

[Patrick Wallek]

Check you /etc/resolv.conf file and make sure it is correct. It should look something like:

domain abc.com
nameserver 172.30.0.177
nameserver 172.30.0.176
nameserver 172.30.0.210

Make sure your domain is correct and the nameserver addresses are correct.

Also check the hosts line in your /etc/nsswitch.conf file. It should be similar to:

hosts: dns [ NOTFOUND=continue ] files

If you want, you can switch the 'files' and 'dns' so that it searches files first.

[James R. Ferguson]

Hi Again:

The easy fix is to change your /etc/nsswitch.conf to query hosts ahead of dns, as:

hosts: files [NOTFOUND=continue] dns

This should allow you to do the 'swinstall'. First fix the nsswitch file, and *then* restart the 'swagentd' daemon as I first suggested.

Regards!

...JRF...

[GTI]

I checked the files and everything is right... But nslookup shows the same. Still not working...

Leandro.

[A. Clay Stephenson]

Hi:

Before we go too far let's establish whether this is an install using a local depot or an install from a remote host.

[GTI]

install from local depot...

Leandro.

[Sachin Patel]

Hi GTI,
Do this
1.Stop your named.
2.if your /etc/resolv.conf move it to /etc/resolv.conf.old
3. vi /etc/hosts file and
127.0.0.1 yoursystemname loopback
ip_of_system yoursystemname
save and close

run swinstall. It will work. I do have same problem on my newly installed system c3po.

swinstall is not resolving your system's name and ip.

Sachin

[Bob_Vance]

A couple of things:

1. you should definitely get the latest SD and SAM patches:
PHCO_22268 - Cumulative SAM/ObAM Patch
PHCO_23042 - Software Distributor cumulative


2. The 'nslookup' error arises from the fact that 'nslookup' cannot do a *reverse* lookup of the "nameserver" mentioned in your /etc/resolv.conf file. This is just something that 'nslookup' does -- for no good reason.
This, then, means that either:
a. you have an incorrect "nameserver" statement in /etc/resolv.conf
or
b. your DNS is not set up correctly, at least vis-a-vis the reverse, ".in-addr.arpa" domains.

"b" is not a problem, though, for othe DNS clients besides 'nslookup', 'cause they don't do the reverse lookup :)


3. /etc/hosts should have entries:

your_IP_addr your_host your_host.your_domain
127.0.0.1 localhost loopback


4. /etc/nsswitch hosts entry should look like:

hosts: dns [NOTFOUND=continue TRYAGAIN=continue UNAVAIL=continue] files


5. what does

swlist -s absolute_path_your_local_depot

show?


BV

[Wodisch]

Hello Leandro,

do you actually want to "copy" the contents of a depot,
or do you want to "install" software from a depot?
If you want to copy, then the command is "swcopy" not
"swinstall", if you want to install, the "target" has to be
your local station's root dir, not "/opt"!

HTH,
Wodisch

[Bill Hassell]

The nslookup problem is a very common error:

# nslookup strauss
*** Can't find server name for address

nslookup has located the server OK, but for security reasons, it must verify that the DNS server is really who it says it is and therefore asks the DNS server: What is your name? and the server says: I don't know my own name.

Now this may seem silly but the reality is that named gets all of its information from the named database, and admins often forget to add the server's name to the database. You can verify this by typing:

nslookup IP_addr_of_DNS_server

and it will likely fail. The fix is fairly easy (and all sysadmins should implement this performance and reliability change): change nsswitch.conf to use hosts first. Then add all the commonly used machine names to /etc/hosts. For network backups, this can significantly reduce network and DNS traffic and allows most networking to work even if the DNS server is down.