Impossible to kill a process !!

 Sun Enterprise 3000 with 3 processors
 Solaris 2.6

SOMETIMES it´s imposible to kill a procces (perhaps with problems)

I try "kill -9 <id_process>"
 (the UID is correct)

The only way to destroy the process is rebooting. ¿¿??
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Are you root?
What process are these?
elmisterAuthor Commented:
The owner is a current user.
If the user or the root try kill it, it´s imposible SOMETIMES.
This issue has been hashed out here before.

If a process is unkillable, it's because it's in kernel mode waiting for an event that never takes place in a part of the kernel that is not interruptable by the signaling mechanism.  This usually indicates some kind of HW failure like a hung device.

The only way to debug this is to run a system call trace on the process and watch what it's doing right before it hangs.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

When a program forks and the child finishes before the parent, the kernel still keeps some of its information about the child in case the parent might need it. For example, the parent may need to check the child's exit status. To be able to get this information, the parent calls wait(); when this happens, the kernel can discard the information.

In the interval between the child terminating and the parent calling wait(), the child is said to be a `zombie'. (If you do `ps', the child will have a `Z' in its status field to indicate this.) Even
though it's not running, it's still taking up an entry in the process table. (It consumes no other resources, but some utilities may show bogus figures for e.g. CPU usage; this is because some parts
of the process table entry have been overlaid by accounting info to save space.)
True, but it didn't seem like this was the issue from the original description.  Elmister, are they showing up as zombies in ps?
as chris_calabrese said. Most common are processes with some kind of "disk failture", they are marked D (disk waiting) in ps output, a problem known from the very early days of SunOS :(
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.