Problem With Trace ASM Sip Filter Session Hung

[Johnny3937]

I accidentally exited a Trace ASM session and it won't let me run another one because the other is still active. Can any Linux person help me to kill that session? I don't know the commands. Thanks!

 

[redphone]

In a pinch, you could run this command: traceSM -m


-m Allows to run multiple instances of traceSM. Do not use
this option in a production system as it may cause
performance issues.

You will need to be root or sroot to kill the active session:

[root@sm63 craft]# killall traceSM

 

[Johnny3937]

This is a production system, but I couldn't get back in and I needed to. Can I use the killall traceSM on my production box?

 

[redphone]

I forgot, you could force logoff the user without being root. In the following example the first craft login has an active traceSM session.

[craft@sm63 ~]$ who
craft    pts/1        2013-05-24 09:00 (10.80.150.50)
craft    pts/2        2013-05-29 12:17 (10.80.150.50)

[craft@sm63 ~]$ ps -ef | grep craft
root      2175  1517  0 May24 ?        00:00:00 sshd: craft [priv]
craft     2189  2175  0 May24 ?        00:02:33 sshd: craft@pts/1
craft     2191  2189  0 May24 pts/1    00:00:00 -bash
root      6759  1517  0 12:17 ?        00:00:00 sshd: craft [priv]
craft     6769  6759  0 12:17 ?        00:00:00 sshd: craft@pts/2
craft     6770  6769  0 12:17 pts/2    00:00:00 -bash
craft    11753  6770  0 12:28 pts/2    00:00:00 ps -ef
craft    11754  6770  0 12:28 pts/2    00:00:00 grep craft
[craft@sm63 ~]$ kill -9 2189

 

[Johnny3937]

Ok, that mostly makes sense to me. But how do you know that 2189 is the TraceSM session?

 

[redphone]

2189 is the "bash" for pts/1. pts/2 just ran "ps -ef" and "grep craft" (6770), so you know that is the current login. You want to kill the bash of the rogue login, so "kill -9 2189" will do that. When you logoff the other user, the instance of traceSM should terminate with it. Or if you have root access, you can run "killall traceSM" on a production system without a problem.

 

[pabxdude]

i think an easier way is:

ps -ef | grep traceSM

this will give you the PID of the locked up session, then just do a kill -9 PID to clear it.

 

[redphone]

ps -ef | grep traceSM" will work if logged in as root. In that case, "killall traceSM" would accomplish this in one step. I was showing how to kill traceSM without the root login.