topic Re: Ongoing depot problem in Operating System - HP-UX

Ongoing depot problem

John B Goode — Thu, 04 Dec 2003 11:11:16 GMT

I still am unable to install ANYTHING I download.
HPUX11.00
HP712 workstation
swinstall sees the depot, analizes it and states ready so it's not a command problem.
Downloaded from Netscape ftp = suspended
Downloaded from HP software= suspended
downloaded to win 2000, ftp'd to unix in BINARY
= suspended
here is an entry at swagent: as you can see it can't read the files in the depot. Any suggestions?

BEGIN install AGENT SESSION (pid=1496)
(jobid=Warlock-0133)

* Agent session started for user "root@Warlock". (pid=1496)

* Beginning Analysis Phase.
* Source:
Warlock:/home/depot/B8342AA_B.11.00.48.01_HP-UX_B.11.00_32+64.depot

* Target: Warlock:/
* Target logfile: Warlock:/var/adm/sw/swagent.log
* Reading source for product information.
* Reading source for file information.
* Executing preDSA command.
NOTE: The used disk space on filesystem "/opt" is estimated to
increase by 27462 Kbytes.
This will leave 91802 Kbytes of available user disk space
after the installation.
NOTE: The used disk space on filesystem "/var" is estimated to
increase by 28 Kbytes.
This will leave 128311 Kbytes of available user disk space
after the installation.
NOTE: The bundle "B8342AA,r=B.11.11.48.01" is already installed. If
you wish to reinstall this bundle, change the "reinstall"
option to "true".

* Summary of Analysis Phase:
* 1 of 1 filesets had no Errors or Warnings.
* The Analysis Phase succeeded.

* Beginning the Install Execution Phase.
* Filesets: 1
* Files: 202
* Kbytes: 27264
* Installing fileset
"NS-communicate.NETSCAPE-RUN,r=B.11.00.48.01" (1 of 1).
ERROR: Could not access remote file "/opt/netscape/LICENSE" in
software item
"NS-communicate.NETSCAPE-RUN,r=B.11.00.48.01,a=HP-UX_B.11.00_32/64,v=HP,fr=4.8,fa=HP-UX_B.11.00_32/64:/opt/netscape"
due to an internal error on the remote system.
ERROR: Failed installing fileset
"NS-communicate.NETSCAPE-RUN,r=B.11.00.48.01". Check the
above output for details.
* Retry number 1 of 1 for loading files for fileset
"NS-communicate.NETSCAPE-RUN,r=B.11.00.48.01".
* Installing fileset
"NS-communicate.NETSCAPE-RUN,r=B.11.00.48.01" (1 of 1).
ERROR: Could not access remote file "/opt/netscape/LICENSE" in
software item
"NS-communicate.NETSCAPE-RUN,r=B.11.00.48.01,a=HP-UX_B.11.00_32/64,v=HP,fr=4.8,fa=HP-UX_B.11.00_32/64:/opt/netscape"
due to an internal error on the remote system.
ERROR: Failed installing fileset
"NS-communicate.NETSCAPE-RUN,r=B.11.00.48.01". Check the
above output for details.
NOTE: The Install Phase has suspended. Check the above output for
reasons.

* Aborting the Install Phase.

======= 12/03/03 17:00:42 MST END install AGENT SESSION (Aborted)
(pid=1496) (jobid=Warlock-0133)

Re: Ongoing depot problem

Umapathy S — Thu, 04 Dec 2003 11:18:57 GMT

The first one says that B8342AA is already installed.

Are you trying to pull the software from a remote machine. It says couldnot access the file. Check the permissions on the remote file. Did you register the depot?

HTH,
Umapathy

Re: Ongoing depot problem

John B Goode — Thu, 04 Dec 2003 11:27:56 GMT

Ok that was a bad example. here's another:
Also, since I can get this far with swinstall what does registering a depot do for me at this point?

BEGIN install AGENT SESSION (pid=1910)
(jobid=Warlock-0123)

* Agent session started for user "root@Warlock". (pid=1910)

* Beginning Analysis Phase.
* Source:
Warlock:/home/depot/bison-1.875-sd-11.00.depot
* Target: Warlock:/
* Target logfile: Warlock:/var/adm/sw/swagent.log
* Reading source for product information.
* Reading source for file information.
* Executing preDSA command.
NOTE: The used disk space on filesystem "/usr" is estimated to
increase by 1163 Kbytes.
This will leave 49020 Kbytes of available user disk space
after the installation.
NOTE: The used disk space on filesystem "/var" is estimated to
increase by 5 Kbytes.
This will leave 128265 Kbytes of available user disk space
after the installation.

* Summary of Analysis Phase:
* 1 of 1 filesets had no Errors or Warnings.
* The Analysis Phase succeeded.

* Beginning the Install Execution Phase.
* Filesets: 1
* Files: 26
* Kbytes: 1137
* Installing fileset "bison.bison-RUN,r=1.875" (1 of 1).
ERROR: Could not access remote file "/usr/local/bin/bison" in
software item
"bison.bison-RUN,r=1.875,a=HP-UX_B.11.00_700/800,v=:/usr/local"
due to an internal error on the remote system.
ERROR: Failed installing fileset "bison.bison-RUN,r=1.875". Check
the above output for details.
* Retry number 1 of 1 for loading files for fileset
"bison.bison-RUN,r=1.875".
* Installing fileset "bison.bison-RUN,r=1.875" (1 of 1).
ERROR: Could not access remote file "/usr/local/bin/bison" in
software item
"bison.bison-RUN,r=1.875,a=HP-UX_B.11.00_700/800,v=:/usr/local"
due to an internal error on the remote system.
ERROR: Failed installing fileset "bison.bison-RUN,r=1.875". Check
the above output for details.
NOTE: The Install Phase has suspended. Check the above output for
reasons.

* Continuing the Install Phase.
* Installing fileset "bison.bison-RUN,r=1.875" (1 of 1).
ERROR: Could not access remote file "/usr/local/bin/bison" in
software item
"bison.bison-RUN,r=1.875,a=HP-UX_B.11.00_700/800,v=:/usr/local"
due to an internal error on the remote system.
ERROR: Failed installing fileset "bison.bison-RUN,r=1.875". Check
the above output for details.
* Retry number 1 of 1 for loading files for fileset
"bison.bison-RUN,r=1.875".
* Installing fileset "bison.bison-RUN,r=1.875" (1 of 1).
ERROR: Could not access remote file "/usr/local/bin/bison" in
software item
"bison.bison-RUN,r=1.875,a=HP-UX_B.11.00_700/800,v=:/usr/local"
due to an internal error on the remote system.
ERROR: Failed installing fileset "bison.bison-RUN,r=1.875". Check
the above output for details.
NOTE: The Install Phase has suspended. Check the above output for
reasons.

* Continuing the Install Phase.
* Installing fileset "bison.bison-RUN,r=1.875" (1 of 1).
ERROR: Could not access remote file "/usr/local/bin/bison" in
software item
"bison.bison-RUN,r=1.875,a=HP-UX_B.11.00_700/800,v=:/usr/local"
due to an internal error on the remote system.
ERROR: Failed installing fileset "bison.bison-RUN,r=1.875". Check
the above output for details.
* Retry number 1 of 1 for loading files for fileset
"bison.bison-RUN,r=1.875".
* Installing fileset "bison.bison-RUN,r=1.875" (1 of 1).
ERROR: Could not access remote file "/usr/local/bin/bison" in
software item
"bison.bison-RUN,r=1.875,a=HP-UX_B.11.00_700/800,v=:/usr/local"
due to an internal error on the remote system.
ERROR: Failed installing fileset "bison.bison-RUN,r=1.875". Check
the above output for details.
NOTE: The Install Phase has suspended. Check the above output for
reasons.

* Continuing the Install Phase.
* Installing fileset "bison.bison-RUN,r=1.875" (1 of 1).
ERROR: Could not access remote file "/usr/local/bin/bison" in
software item
"bison.bison-RUN,r=1.875,a=HP-UX_B.11.00_700/800,v=:/usr/local"
due to an internal error on the remote system.
ERROR: Failed installing fileset "bison.bison-RUN,r=1.875". Check
the above output for details.
* Retry number 1 of 1 for loading files for fileset
"bison.bison-RUN,r=1.875".
* Installing fileset "bison.bison-RUN,r=1.875" (1 of 1).
ERROR: Could not access remote file "/usr/local/bin/bison" in
software item
"bison.bison-RUN,r=1.875,a=HP-UX_B.11.00_700/800,v=:/usr/local"
due to an internal error on the remote system.
ERROR: Failed installing fileset "bison.bison-RUN,r=1.875". Check
the above output for details.
NOTE: The Install Phase has suspended. Check the above output for
reasons.

* Aborting the Install Phase.

======= 12/03/03 15:07:51 MST END install AGENT SESSION (Aborted)
(pid=1910) (jobid=Warlock-0123)

======= 12/03/03 15:07:53 MST BEGIN install AGENT SESSION (pid=1985)
(jobid=Warlock-0123)

* Agent session started for user "root@Warlock". (pid=1985)

======= 12/03/03 15:08:09 MST END install AGENT SESSION (Cancelled)

Re: Ongoing depot problem

John B Goode — Thu, 04 Dec 2003 11:28:36 GMT

Also, all this is being done on one unix machine.

Re: Ongoing depot problem

Robert-Jan Goossens — Thu, 04 Dec 2003 11:33:23 GMT

John,

Could you check your /etc/hosts file.

127.0.0.1 localhost loopback
145.x.x.48 dbxx1 dbxx1.xxx.nl # the HOSTNAME

Robert-Jan

Re: Ongoing depot problem

melvyn burnard — Thu, 04 Dec 2003 11:35:09 GMT

what is the command line you are running?
are you doing this using the GUI?
This looks like it may need an option change to allow the source to be local .

Re: Ongoing depot problem

Todd McDaniel_1 — Thu, 04 Dec 2003 11:38:58 GMT

This may be a too simple answer, but it seems to me a permissions problem.

ERROR: Could not access remote file "/usr/local/bin/bison" in
software item
"bison.bison-RUN,r=1.875,a=HP-UX_B.11.00_700/800,v=:/usr/local"
due to an internal error on the remote system.

somehow the depot is seen, but you can't access the files. OR the file is missing.

Can you verify what exists in the depot on the remote host?

Re: Ongoing depot problem

John B Goode — Thu, 04 Dec 2003 11:43:56 GMT

I type swinstall and the SD Install window opens in CDE. The source host is there i.e. Warlock bur the source depot path is /ver/spool/sw. I cange this to /home/depot/blahblah.depot
Source depot type is local directory.
the depot then shows up in the SD install software selection on warlock (the window in CDE) and I mark for install and then install. it analysizes it gives me a status as ready and I click "ok". It runs for a few seconds then suspends. Everytime on every depot I've downloaded.

Re: Ongoing depot problem

John B Goode — Thu, 04 Dec 2003 11:46:11 GMT

The deopt is on my unix box. I'm trying to install it on my unix box. also, would a bad entry in the etc/hosts file allow me to get this far with an install? like being able to analyize the depot?

Re: Ongoing depot problem

Robert-Jan Goossens — Thu, 04 Dec 2003 11:48:37 GMT

John,

I think there is something wrong with your hostname that is why swinstall things you are using a remote server. check your /etc/hosts file.

Could not access remote file

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000068802395

Robert-Jan

Re: Ongoing depot problem

Umapathy S — Thu, 04 Dec 2003 11:56:23 GMT

One of the standard solutions is to restart swagentd.
Did you see anything in /var/adm/sw/swagentd.log. What about /var/adm/syslog/syslog.log.

Basically it is trying to get from remote system. But the analysis has succeeded in the local system. Some problem with the hostname settings. /etc/hosts or dns.

does $HOSTNAME is set properly. Run hostname and check. Is loopback in /etc/hosts

HTH,
Umapathy

Re: Ongoing depot problem

Darren Prior — Thu, 04 Dec 2003 12:05:22 GMT

John,

Even though this is all happening on one machine it is vital that your networking is configured correctly.

Please ensure that you have the loopback entry in /etc/hosts as below:

127.0.0.1 localhost loopback

and also the fully qualified name in the format shown below (obviously using your values!)

15.13.12.1 blob blob.wibble.hp.com

regards,

Darren.

Re: Ongoing depot problem

John Ramsay_1 — Thu, 04 Dec 2003 12:14:58 GMT

My localhost loopback is there...
Should my hostname be:
192.168.2.16 Warlock
or
127.0.0.1 Warlock

Also I have my dns resolv to look at etc/hosts first then the outside DNS on my ISP Cox.net. I had to do this to get the xserver to run and allow hostname resolution with the existing netscape 3.01 browser. I noticed the original hostname hp4you was given a IP of 127.0.0.1 and the localhost was 127.0.0.1. My unix box got 192.168.2.16 from my router/cablemodem.
I think you all are on to something. It's funny how all my problems go back to that hostname DNS stuff.

Re: Ongoing depot problem

Umapathy S — Thu, 04 Dec 2003 12:20:21 GMT

The basic entries should be like. It should have both the entries.

192.168.2.16 Warlock
127.0.0.1 localhost loopback

I think the dns is fine.

HTH,
Umapathy

Re: Ongoing depot problem

John Ramsay_1 — Thu, 04 Dec 2003 12:20:33 GMT

what about one of the following:
127.0.0.1 Warlock.cox.net
or
192.168.2.16 Warlock.cox.net

Re: Ongoing depot problem

Darren Prior — Thu, 04 Dec 2003 12:25:33 GMT

You will need to use:

192.168.2.16 warlock warlock.cox.net

PS: You will need to log into the forums with the same id as the question author as otherwise it will confuse people and you won't be able to assign points to those that have helped you ;-)

regards,

Darren.

Re: Ongoing depot problem

John Ramsay_1 — Thu, 04 Dec 2003 12:31:32 GMT

My old account stopped working and I had to register...sorry

Re: Ongoing depot problem

John Ramsay_1 — Thu, 04 Dec 2003 12:43:43 GMT

That was the problem...Thanks so much for all the help. I wanted to assign points but my old account is toast. If I get it working I will.