swinstall problem

[Stephen Keane]

Mateja,

swreg seems happy enough, no errors.

[Greg Vaidman]

can you get a swlist of the depot? ("swlist -d @ /path/to/depot", and post the output for us)

also, from your original message, it looks like you're using a file (as opposed to a directory) depot. since a file depot is just a tar file, can you also post the output of "tar tvf foo.depot"?

[Ermin Borovac]

Stephen, sorry KBRC00016523 is document ID in the HP's technical knowledge base article. If you have support contract with HP go to www.itrc.hp.com, search by 'doc ID', enter KBRC00016523 and you'll find issue very similar to yours. It's only relevant if you have PHCO_32116.

[vinod_25]

hi stephen

The swinstall "rpc exception communication error" most likely indicates a hostname resolution problem.

check the hostname and ip address in
/etc/resolv.conf, /etc/nsswitch.conf or
/etc/hosts

The /usr/sbin/swagentd daemon, which is required when using SD-UX commands like swinstall, keeps hostname resolution information from the time it is initialized. Network or hostname resolution changes can cause the static information used by the swagentd to become outdated and incorrect
and can cause the "rpc exception communication error" exhibited in this case.

issue /usr/sbin/swagentd -r to restart the swagent daemon...

even if that doesnt solve the problem try
- lanscan
- ifconfig (for each network interface card)
- netstat -nr
- nslookup `hostname`
- nslookup IP_ADDR (where IP_ADDR is IP returned by nslookup `hostname`)

you can find additional info from /var/adm/sw.

Regards

Vinod

[Stephen Keane]

vinod,

all the network stuff looks fine. host-ip and ip-host resolution seems OK. The thing is I can install patches, stored locally on the machine, but not a particular depot. Which leads me to believe the depot is faulty.

Greg,

the swlist command produces ...

# Initializing...
# Contacting target "foo"...
Memory fault(coredump)

file core

core: core file from "swlist" - received SIGSEGV

[Stephen Keane]

Ermin,

As far as I know, I don't have PHCO_32116 installed. Unless I've installed a superceding patch.

[Ermin Borovac · Accepted solution]

Can you please try the following?

# mkdir /tmp/foo
# cd /tmp/foo
# tar xvf /depot_dir/foo.depot
# cd catalog
# touch swlock
# swpackage -x media_type=tape -s /tmp/foo @ /depot_dir/foo2.depot

Now see if swlist works on /depot_dir/foo2.depot.

[Stephen Keane]

Ermin,

I wish I had more than 10 points to give you!

That not only allowed swlist to work, it also swinstall'ed.

But how did the depot get into that state?

[Ermin Borovac]

Similar problem is described in the knowledge base article I mentioned earlier. It doesn't give out any further details except to say that depot is not "properly packaged" (in this case it was depot for product called SecurePath). Apparently problem will be fixed with the next SD-UX patch with release date still unknown.

[Stephen Keane]

I'll have to live with it then. I tried looking up the reference you gave me, by DocId, but got no results.

Solution was as suggested by Ermin.