topic Re: install sdk13_13109_1100.depot in Operating System - HP-UX

install sdk13_13109_1100.depot

piyut_2 — Thu, 10 Feb 2005 22:04:59 GMT

dear,

when i run
swinstall -s /tmp/sdk13_13109_1100.depot
there is an error "oasis:/tmp/sdk13_13109_1100.depot": You do not have the required permissions to perform this operation. Check permissions using the "swacl" command or see your system administrator for assistance. Or,
to manage applications designed and packaged for nonprivileged mode,
see the "run_as_superuser" option in the "sd" man page.

I run with root user.

Re: install sdk13_13109_1100.depot

Florian Heigl (new acc) — Thu, 10 Feb 2005 22:13:56 GMT

Is Your DNS loopback config okay?

On one host I got the same error as You did and searched for a very long time until I figured that with the upstream nameservers I set the resolver to use, a connect to swagentd would come not from my.hostname.net but from the bare ip address which was not allowed to access the daemon.

quick resolution: check Your /etc/hosts for the localhost and host entries and temporarily move away /etc/resolv.conf - unless something depends on it too much to stop it for 5 minuntes.
In that case see the nsswitch.conf man page or look at my settings below - I found them to work without any further tuning.

in nsswitch.conf:
hosts: files dns

in /etc/hosts:
127.0.0.1 localhost loopback
ip_address snowwhite

good luck,
florian

Re: install sdk13_13109_1100.depot

bhavin asokan — Thu, 10 Feb 2005 22:49:10 GMT

hi,

reboot the swagent daemon

/sbin/init.d/swagentd stop
/dbin/init.d/swagentd start

and by id command make sure that your uid is 0 (root) and group is sys

regds,

Re: install sdk13_13109_1100.depot

Yogeeraj_1 — Fri, 11 Feb 2005 02:19:15 GMT

hi,

there must be something wrong with the access control.

in the meanwhile you can try to run swinstall independently

i.e.
swinstall

then specify "/tmp/sdk13_13109_1100.depot" as the "Source Depot Path"

regards
yogeeraj

Re: install sdk13_13109_1100.depot

piyut_2 — Fri, 11 Feb 2005 09:23:43 GMT

thanks for all,

the solution is to reboot the swagent daemon.

best regards,

piyut