

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 10.3K Views
Accepted Solutions


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 10.3K Views
RHEL 4 is End of Support as of March 2017, you really need to look into migrating this system (and apps) to a more current RHEL.
kill -9 is likely the way to go, but realize that sigkill (-9) is not sent to the process, but instead denotes that the kernel should terminate this process. When the kernel terminates a process, it just wipes it off the system. Because of that, files that are open may still be open the next time the OS goes to access them, someone earlier mentioned corrupted data, that's possible, but as long as the disk writes were put into the OS buffer, that'll still be honored. However, any active transactions (to like a database) that were occuring would only be partially done as the process doing them was destroyed in the middle of it's operation. You want to use -9 as infrequently as possible.
-STM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 10.3K Views
Hey, @jeesshnasree,
Please tell us a bit more if you want us to help you.
Provide at least the following:
- what do you want to achieve?
- what did you do?
- what happened?
- what did you expect to happen?
It's kind of difficult to help if one doesn't know at least some of the above.
Cheers,
Grega
[don't forget to kudo a helpful post or mark it as a solution!]


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 10.3K Views
Actually it’s related to java process ID and unable to kill (RHEL OS 4), finally not able to stop JVM .,could you please provide solution . Could you please let me know if more details required


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 10.3K Views
Try:
sudo kill -9 <PID>
Keep in mind that if you forcefully kill a process, it may cause data corruption.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 10.3K Views
I think "sudo kill -9 <PID>" with running non-root user for kill and not sure with "sudo kill -9 PID . if execute kill -9 <PID> ( i think only stop the particular process id related JVM and not sure about corrept data . if I wrong about this message , please correct me


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 10.3K Views
What kind of state is the proces in? You can check the state of the process with the ps command.
ps aux | grep <PID>
You may not be able to kill the process depending on the processes state (zombie (Z) or uninterruptable (D))


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 10.3K Views
RHEL 4 is End of Support as of March 2017, you really need to look into migrating this system (and apps) to a more current RHEL.
kill -9 is likely the way to go, but realize that sigkill (-9) is not sent to the process, but instead denotes that the kernel should terminate this process. When the kernel terminates a process, it just wipes it off the system. Because of that, files that are open may still be open the next time the OS goes to access them, someone earlier mentioned corrupted data, that's possible, but as long as the disk writes were put into the OS buffer, that'll still be honored. However, any active transactions (to like a database) that were occuring would only be partially done as the process doing them was destroyed in the middle of it's operation. You want to use -9 as infrequently as possible.
-STM


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 10.3K Views
thanks Scott