Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2227
  • Last Modified:

How to kill a process...

Hi,

I have 3 processes that just won't die, even with kill -9. I'm not aware of any other more severe way to kill a process.

This is on HP-UX.

If you can advise, please do!!

Thanks,
Derek.
0
ruamire
Asked:
ruamire
  • 6
  • 3
  • 3
  • +5
10 Solutions
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
which processes? can you show the ps -eaf  for the relevant processes?
0
 
ruamireAuthor Commented:
BTW : I am aware of a more severe way, a reboot, but I'm not that keen on that solution.
0
 
ruamireAuthor Commented:
Here's the output you requested....

  bt21cd 15352     1  0 13:41:19 ?         2:09 /net/burns/export/home2/bt21cd/ac/f3.6/b
  bt21cd 15029     1  0 13:30:41 ?         2:53 /net/burns/export/home2/bt21cd/ac/f3.6/b
  bt21cd 16373     1  0 14:35:32 ?        76:15 /net/burns/export/home2/bt21cd/ac/f3.6/b
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ruamireAuthor Commented:
I've ran kill -9 15352 15029 16373
to no avail...
0
 
ruamireAuthor Commented:
These are not zombie processes, they are holding ports which means I cannot start another instance of my process.
0
 
dnojcdCommented:
have u tried the fuser -f to find  which files or directories within a filesystem are currently in use and to identify the processes and users that are using them
after that you can use fuser -k
0
 
mightyoneCommented:
if they have guis use xkill

or try user logoff and relogin

when they hold ports it might be worse a network restart

rcnetwork restart
0
 
bpeterseCommented:
If you have access to a serial console, try going into Single User mode - that'll kill all user proc's and still avoid going <completely> down.  init S
0
 
ahoffmannCommented:
if kill -9 does not stop the process, then your user have not proper permissions, or the process is disk waiting (seems to be started from NFS), or it's a zombie
0
 
gheistCommented:
It lost the file handle on NFS down below, has pending writes , and will not die. Data has been damaged.
System reboot is 100% working fix. But try single mode first.

To avoid:
Do not mount NFS over firewalls and use TCP instead of UDP for involved mount
0
 
bpeterseCommented:
Hey - if you're using nfs, check for lockd, statd daemons.  They've been known to flake out (at least on Solaris) and restarting those daemons could fix the problem.
0
 
Jeremy_WileyCommented:
On solaris REBOOT
0
 
ruamireAuthor Commented:
Unfortunately none of these options worked. I had to reboot HP-UX.
0
 
gheistCommented:
Did you take measures to avoid problem in future?
0
 
ahoffmannCommented:
> Unfortunately none of these options worked. I had to reboot HP-UX.
could you please explain?

Are you saying that user root cannot kill these processes, they are no zombies, and they are not disk waiting?
unbelievable ...
0
 
gheistCommented:
Asker took Window approach - reboot when in doubt .... No need to solve problem.
0
 
ahoffmannCommented:
Windows approach is reinstall from scratch, isn't it?
SCNR :-))
0
 
ruamireAuthor Commented:
I'm going to close this off, hopefully won't be in this situation again anytime soon.

Points for all cause I can't say any particular solution worked but thanks for the comments.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 6
  • 3
  • 3
  • +5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now