swacl

[Richard Lindroth]

Hi!

I downloaded some free software from the HP developer resources site and tried instaling it as root using swinstall according to the instructions. I get the following error:

ERROR: "localhost:/": You do not have the required
permissions to select this target. Please check to see that
you have the required permissions using the "swacl" command or
see your system administrator for assistance.
* Target connection failed for "localhost:/".
ERROR: More information may be found in the daemon logfile on this
target (default location is
localhost:/var/adm/sw/swagentd.log).
* Selection had errors.

So I check the logfile which is empty and then run the swacl command. I get this error message:

ERROR: An unexpected error occurred while performing the requested
operation on the "host" ACL at "localhost:/". This
is probably the result of a failed Remote Procedure Call to a
daemon, a failure in the SD ACL manager, or the improper
removal of the ACL. If this problem persists, contact your
system administrator.

If anyone has any idea what the problem is and how to solve it, I'd greatly appreciate it.

/Richard

[Vincenzo Restuccia]

Try http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90154/B2355-90154_top.html&con=/hpux/onlinedocs/B2355-90154/00/00/39-con.html&toc=/hpux/onlinedocs/B2355-90154/00/00/39-toc.html&searchterms=swacl&queryid=20010419-155115

[Mark Fenton]

The error message you're seeing would imply that the ACL doesn't exist?

ERROR: An unexpected error occurred while performing the requested operation on the "host" ACL at "localhost:/". This is probably the result of a failed Remote Procedure Call to a daemon, a failure in the SD ACL manager, or the improper removal of the ACL. If this problem persists, contact your
system administrator.

[Steffi Jones_1 · Accepted solution]

Hi Richard,

I have seen these error messages before andit helped in the past to kill and restart the swagentd.

Make sure that nobody else has an open swinstall session.

Easy steps to do:

1) ps -ef | grep sw
That will pull up swagentd (usually swapper, but has nothing to do with this here and should be left alone)
2) kill -9 PID for swagentd
3) check for other sd ux processes and if so check if they can be killed
4) /usr/sbin/swagentd ... to restart the swagentd

Good luck,

Steffi Jones