cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Is samx safe to kill?

 
SOLVED
Go to solution
New Member

Is samx safe to kill?

No one is running sam on my host but top tells me this:

CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
16 ? 22878 root 241 20 17696K 4388K run 7583:00 97.77 97.60 samx

Plus this output shows no other sam processes:

/root)# ps -ef | grep sam
root 10179 1 0 Apr 13 ? 1:23 /usr/sam/lbin/samd
root 22878 1 255 Apr 21 ? 7580:25 samx -K 22874 /usr/sam/lib/%L/fal.ui

Why is samx bottling up one of my CPUs?

Can I safely kill this even though the parent PID is 1?
7 REPLIES 7
Honored Contributor

Re: Is samx safe to kill?

Jim

Looks like a lost session as there is no tty associated with it.

Do you have TUSC installed if so:-

tusc 22878 and see what it is doing.

Also have a look at PID 22874 and see what that is.

Paula

If you can spell SysAdmin then you is one - anon
Honored Contributor

Re: Is samx safe to kill?

Ad far as I know - you can kill it.

Sounds like SAM didn't exit correctly - make sure you have recent patches applied....


Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Honored Contributor

Re: Is samx safe to kill?

Geoff

My worry is PID 22874 ---- What is it?

Paula
If you can spell SysAdmin then you is one - anon
New Member

Re: Is samx safe to kill?

There is no PID 22874 active on the system.

According to the tusc output it looks as if PID 22878(samx) is in an error loop:

tusc 22878 | more
( Attached to process 22878 ("samx -K 22874 /usr/sam/lib/%L/fal.ui") [32-bit] )
read(-1, 0x7aea0c08, 256) ............................................................................ [running]
read(-1, 0x7aea0c08, 256) ............................................................................ ERR#9 EBADF
read(-1, 0x7aea0c08, 256) ............................................................................ ERR#9 EBADF
read(-1, 0x7aea0c08, 256) ............................................................................ ERR#9 EBADF
read(-1, 0x7aea0c08, 256) ............................................................................ ERR#9 EBADF
read(-1, 0x7aea0c08, 256) ............................................................................ ERR#9 EBADF
etc.....

It looks like a definate kill candidate.
Honored Contributor
Solution

Re: Is samx safe to kill?

Jim

Try a straight kill 22878 first.
If that dosent work then kill -15.

As a last resort kill -9.

Also as Geoff said check you patch level.

Paula
If you can spell SysAdmin then you is one - anon
New Member

Re: Is samx safe to kill?

Straight kill did it.

Great advice on using tusc.

Will do on the patch checks.

Points assigned.

Thanks again.
Honored Contributor

Re: Is samx safe to kill?

Welcome to the forum Jim.

Working late?

It is 02:40 here in London (UK)

Paula
If you can spell SysAdmin then you is one - anon