lock prevents swinstall from working

[Dave Chamberlin]

On trying to install software with swinstall, it fails to allow me to pick / as the target. The swagentd log reports that it cannot lock target / because another command holds a conflicting lock. I assume this is because a previous swinstall session hung and I had to kill it. Can I safely kill the locking process (swagentd ....). What is the best way to terminate swinstall (if it hangs) without leaving a locked situation?

[Rick Garland · Accepted solution]

Do the swagentd -r command. This will reset the daemon.

When you kill, you are not giving a chance to clean and reset itself.

(Check the $PATH for the command)

[Alan Riggs]

I suggest also using ps -ef |grep sw to check for old swinstal, swcopy, swlist, etc. processed. Kill them all (make sur eyou don't kill swapper) and then issue swagentd -r.

If that doesn't work, try moving the /var/adm/sw/products/swlock file.

[Emmanuel Eyer]

Concerning Alan's reply, I'm afraid that removing the lock file might prevent SD-UX to work. The file must be there, but empty, as far as I remember (I removed once this file and ran into bigger troubles).

Cheers, Emmanuel

[Cheryl Griffin]

Removing /var/adm/sw/products/swlock is routine in recovering from SD-UX hangs or for error messages of "source already in use" when it is really not in use.

Once the swinstall/swcopy, etc. processes are stopped/killed, the file should be removed. Stop and restart swagentd and retry the commands.

[Dave Chamberlin]

swagent -r worked fine to restart the daemon. As it turns out, swinstall was hanging until I learned that I could bypass the problem with: swinstall -x rpc_binding_info=ncadg_ip_udp:[2121]. I learned that there is a patch for swinstall, PHCO_20209. Thanks for the help