swinstall error messages

[Donald Thaler]

Why would i get the following error's after running a swinstall, when I looked at the swagent.log and the swagentd.log everything looks ok. These are the error messages that are returned at the console :
swinstall /u02/hpux_patches/cde_patch/depot

======= 09/15/05 16:16:26 EDT BEGIN swinstall SESSION
(non-interactive) (jobid=phoenix-0141)

* Session started for user "root@phoenix".

* Beginning Selection
* Target connection succeeded for "phoenix:/".
ERROR: There is currently no depot software on host "phoenix" at
location "/var/spool/sw". Make sure that an absolute pathname
is specified for location (beginning with "/").
* Source connection failed for "phoenix:/var/spool/sw".
WARNING: More information may be found in the daemon logfile on this
target (default location is phoenix:/var/adm/sw/swagentd.log).
* Selection had errors.



======= 09/15/05 16:16:31 EDT END swinstall SESSION (non-interactive)
(jobid=phoenix-0141)

[Mel Burslan]

I have never asked this question before and I am not sure about the certainity of my answer but I think when swinstall gets launched, it checks the /var/spool/sw as the default depot container.

if you happen to run

swlist -l depot

command on this server, you will more than likely see /var/spool/sw listed as a source.

if you unregister it, using command

swreg -u -l depot /var/spool/sw

it will not come up again when you launch swinstall session to the best of my knowledge

[James R. Ferguson]

Hi Donald:

It appears that you didn't specify the depot locatino. The default is /var/spool/sw. Perhaps you wanted:

# swinstall -x autoreboot=true -x patch_match_target=true -s /u02/hpux_patches/cde_patch/depot

Regards!

...JRF...

[Sameer_Nirmal]

It seems that you didn't provide the source directory of the depot file. By default swinstall will look into /var/spool/sw for any depot file. If nothing there , it will flash that error.

You need to give the command as
#swinstall -s

With this, the depot file would be sourced to swinstall and it will start an interactive SAM session as well to continue the installation of the depot software.

[Andrew Rutter]

hi donald,

It just looks like you havent given the full/correct path to the patch depot.

swinstall is looking here :/var/spool/sw for the patch and you have it here /u02/hpux_patches/cde_patch/depot


run swinstall again adding the correct path or just run the interactive swinstall
#swinstall
and then when the TUI opens point it to the correct path and install from here.

Andy

[Arunvijai_4]

Hi Donald,

It looks like you haven't given the full path to the depot. Try this,

# swinstall -s /u02/hpux_patches/cde_patch/.depot

-Arun

[VEL_1]

You can use sam also to install the software.

Thanks

[Donald Thaler]

I thought I gave it the path, the command was
'swinstall /u02/hpux_patches/cde_patch/depot'.

And in fact the .log file that was created did show the patches as available (Available PHKL_30398.CORE2-KRN,r=1.0) and verified (Verified PHKL_30398.CORE2-KRN,r=1.0) . Should there be additional entries in the .log file indicating the patch was actually applied?

Is the -s parameter required, and would I compromise anything if i reran the swinstall again with the -s parameter?

[Arunvijai_4 · Accepted solution]

-s is required with swinstall. It specifies the source depot.

-Arun

[Pete Randall]

Yes, "swinstall -s /u02/hpux_patches/cde_patch/depot" should do the trick.


Pete

[James R. Ferguson]

Hi Donald:

The '-s' option signals that what follows is the software source, in this case, your depot. You need to specify it as shown in my first post.

There is no problem rerunning the session. 'swinstall' has options to control reinstallation. The default, unless you have rest it in your sessions file, is *not* to reinstall. At commandline you would add '-x reinstall=true' and/or '-s reinstall_files=true' but that is only done infrequently.

Regards!

...JRF...