while swconfig the subsystem we are getting error

[ossrte]

hi guys we are getting the following error while doing the swconfig for the subsystem
* Beginning Selection
ERROR: "pulsar2:/": This target or source is already in use either
within this same session or by another session. A read or
write lock was denied.
what i have to do for resolving this

[Dennis Handly]

Is anyone else doing a swinstall or swconfig, etc. on this system?

You might want to use ps -ef to see if there is any sw command running besides demons.

If not, did you abort a SD command in the past?
If so, you may have to clean up the lock file.
Possible in here? /var/adm/sw/queue

[ossrte]

yes i have aborted the eriler session due to some problem
now i want to configure them
how do i clear this lock

[Dennis Handly]

>how do i clear this lock

You could look in /var/adm/sw/queue/.
Or you may want to look at other threads that stop and start swagentd, that may clean it up:
# /usr/sbin/swagentd -r

[avik]

a. find out the pid that locking the session from /var/adm/swagent/swagentd.log

b. kill that PID. Do a ps -ef | grep to make sure the kill was sucessfull

c. restart the swagent daemon "swagentd -r"

[Steven E. Protter]

Shalom,

Welcome to the forums.

The most common cause of this issue is what you did, killing a running sd-ux session.

Restarting swagentd does reset the lock.
Restarting the entire system does as well.
Deleting the lock file manually normally does reset the lock. Even when the running process is killed, the lock file is often left behind.

SEP