- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Run-away process
Operating System - HP-UX
1748051
Members
5180
Online
108757
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2004 08:29 AM
05-11-2004 08:29 AM
Run-away process
All,
Here is the alarmdef I have for identifying run-away procs in the system.
==============================================
proctime=3600
PROCESS LOOP
{
if (PROC_USER_NAME != "root") then
{
if ((PROC_RUN_TIME > proctime) and (PROC_CPU_TOTAL_TIME_CUM >= (PROC_RUN_TIME * 0.75))) and
((PROC_DISK_PHYS_IO_RATE_CUM < 10) or (PROC_DISK_LOGL_IO_RATE_CUM <
10)) then
{
exec "/usr/local/bin/somescript PROC_PROC_ID"
}
}
} ==============================================
The above definition identifies the run away processes using the following criteria
1) the process owner is not root and
2) the total elapsed time of the process is more than 3600 secs with the total CPU time by the process
exceeding more than 75% of the elapsed time and
3) the process is not effectively doing any physical or logical IO.
So any process sitting idle for more than 1 hr (doing no physical/logical IO) and consuming CPU time will be considered a run-away process.
I would like some feedback/suggestion from you forum folks.
TIA
Sundar.
Here is the alarmdef I have for identifying run-away procs in the system.
==============================================
proctime=3600
PROCESS LOOP
{
if (PROC_USER_NAME != "root") then
{
if ((PROC_RUN_TIME > proctime) and (PROC_CPU_TOTAL_TIME_CUM >= (PROC_RUN_TIME * 0.75))) and
((PROC_DISK_PHYS_IO_RATE_CUM < 10) or (PROC_DISK_LOGL_IO_RATE_CUM <
10)) then
{
exec "/usr/local/bin/somescript PROC_PROC_ID"
}
}
} ==============================================
The above definition identifies the run away processes using the following criteria
1) the process owner is not root and
2) the total elapsed time of the process is more than 3600 secs with the total CPU time by the process
exceeding more than 75% of the elapsed time and
3) the process is not effectively doing any physical or logical IO.
So any process sitting idle for more than 1 hr (doing no physical/logical IO) and consuming CPU time will be considered a run-away process.
I would like some feedback/suggestion from you forum folks.
TIA
Sundar.
Learn What to do ,How to do and more importantly When to do ?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2004 08:46 AM
05-11-2004 08:46 AM
Re: Run-away process
This sort of thing is very difficult to define --- and will very much depend upon your environment. For example, a number-crunching application like computational fluid dynamics or finite element analysis would perfectly fit your criteria. These programs can run for days and only do i/o at the beginning and end. Typically, you also need to filter on process names as well.
If it ain't broke, I can fix that.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP