HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- multiplying defunct processes
Operating System - HP-UX
1832790
Members
2979
Online
110045
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
Forums
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
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
10-28-2005 02:55 AM
10-28-2005 02:55 AM
multiplying defunct processes
We patched the system (HPUX B.11.00 U 9000/800) last weekend (after several years) and the process we have always used to kill users still logged in is suddenly causing rapidly multiplying defunct processes.
The shell script that runs nightly basically does this:
1. Find all â kshâ processes and kill the ppid and pid (kill â 9 ppid pid)
2. Find any remaining processes locally attached to the Oracle db and kill the ppid and pid.
3. Find any remaining processes non-locally attached to the Oracle db and kill the ppid and pid.
In June, we stopped executing the first step, and only looked for processes actually attached to the db and killed them. No problems. After hitting this problem this week, the first step was reinstated, and then altered to only kill the ppid (not the pid) of the â kshâ process, but that did not help. Here is a summary of what happens (word doc also attached, for better formatting):
â Normalâ user session:
root 4095 955 0 08:59:28 pts/tad 0:00 telnetd
upmay 4096 4095 0 08:59:30 pts/tad 0:05 -ksh
upmay 17366 4096 0 12:08:27 pts/tad 0:07 quick subdict=search auto=/uk_home/jervis/v63yoln/MENUGO.qkg
upmay 17382 17366 0 12:08:29 ? 0:00 oracleUK (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
Now the kill script kicks in:
upmay 4096 1 1 08:59:30 ? 0:05 -ksh
upmay 1918 1 0 19:01:44 ? 0:00
upmay 2362 4096 0 19:01:45 ? 0:00 -ksh
And 10 seconds later:
upmay 4096 1 1 08:59:30 ? 0:05 -ksh
upmay 7649 1 0 19:02:06 ? 0:00
And about 20 seconds later:
upmay 4096 1 0 08:59:30 ? 0:05 -ksh
upmay 7651 1 1 19:02:06 ? 0:00
upmay 7649 1 0 19:02:06 ? 0:00
upmay 9016 4096 0 19:02:11 ? 0:00
upmay 9493 1 0 19:02:13 ? 0:00
upmay 9492 1 0 19:02:13 ? 0:00
upmay 11412 1 1 19:02:21 ? 0:00
upmay 11411 1 0 19:02:21 ? 0:00
upmay 13228 1 1 19:02:28 ? 0:00
upmay 16543 1 0 19:02:41 ? 0:00
upmay 13156 1 0 19:02:27 ? 0:00
upmay 13624 1 2 19:02:29 ? 0:00
upmay 13623 1 0 19:02:29 ? 0:00
upmay 17020 1 1 19:02:42 ? 0:00
upmay 15600 1 2 19:02:37 ? 0:00
upmay 17935 1 1 19:02:46 ? 0:00
upmay 15527 1 1 19:02:37 ? 0:00
upmay 16946 1 0 19:02:42 ? 0:00
upmay 18311 1 0 19:02:47 ? 0:00
upmay 18415 1 3 19:02:48 ? 0:00
upmay 16616 1 0 19:02:41 ? 0:00
upmay 20387 1 0 19:02:55 ? 0:00
upmay 20472 1 1 19:02:56 ? 0:00
upmay 23532 1 0 19:03:07 ? 0:00
upmay 23531 1 1 19:03:07 ? 0:00
These processes continue to multiply until the process table is filled. This seems to happen only when the kill script is run at 7:00pm each night. I can kill a user session from the unix prompt in exactly the same manner and cannot seem to reproduce this problem. Any ideas, anyone ????
The shell script that runs nightly basically does this:
1. Find all â kshâ processes and kill the ppid and pid (kill â 9 ppid pid)
2. Find any remaining processes locally attached to the Oracle db and kill the ppid and pid.
3. Find any remaining processes non-locally attached to the Oracle db and kill the ppid and pid.
In June, we stopped executing the first step, and only looked for processes actually attached to the db and killed them. No problems. After hitting this problem this week, the first step was reinstated, and then altered to only kill the ppid (not the pid) of the â kshâ process, but that did not help. Here is a summary of what happens (word doc also attached, for better formatting):
â Normalâ user session:
root 4095 955 0 08:59:28 pts/tad 0:00 telnetd
upmay 4096 4095 0 08:59:30 pts/tad 0:05 -ksh
upmay 17366 4096 0 12:08:27 pts/tad 0:07 quick subdict=search auto=/uk_home/jervis/v63yoln/MENUGO.qkg
upmay 17382 17366 0 12:08:29 ? 0:00 oracleUK (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
Now the kill script kicks in:
upmay 4096 1 1 08:59:30 ? 0:05 -ksh
upmay 1918 1 0 19:01:44 ? 0:00
upmay 2362 4096 0 19:01:45 ? 0:00 -ksh
And 10 seconds later:
upmay 4096 1 1 08:59:30 ? 0:05 -ksh
upmay 7649 1 0 19:02:06 ? 0:00
And about 20 seconds later:
upmay 4096 1 0 08:59:30 ? 0:05 -ksh
upmay 7651 1 1 19:02:06 ? 0:00
upmay 7649 1 0 19:02:06 ? 0:00
upmay 9016 4096 0 19:02:11 ? 0:00
upmay 9493 1 0 19:02:13 ? 0:00
upmay 9492 1 0 19:02:13 ? 0:00
upmay 11412 1 1 19:02:21 ? 0:00
upmay 11411 1 0 19:02:21 ? 0:00
upmay 13228 1 1 19:02:28 ? 0:00
upmay 16543 1 0 19:02:41 ? 0:00
upmay 13156 1 0 19:02:27 ? 0:00
upmay 13624 1 2 19:02:29 ? 0:00
upmay 13623 1 0 19:02:29 ? 0:00
upmay 17020 1 1 19:02:42 ? 0:00
upmay 15600 1 2 19:02:37 ? 0:00
upmay 17935 1 1 19:02:46 ? 0:00
upmay 15527 1 1 19:02:37 ? 0:00
upmay 16946 1 0 19:02:42 ? 0:00
upmay 18311 1 0 19:02:47 ? 0:00
upmay 18415 1 3 19:02:48 ? 0:00
upmay 16616 1 0 19:02:41 ? 0:00
upmay 20387 1 0 19:02:55 ? 0:00
upmay 20472 1 1 19:02:56 ? 0:00
upmay 23532 1 0 19:03:07 ? 0:00
upmay 23531 1 1 19:03:07 ? 0:00
These processes continue to multiply until the process table is filled. This seems to happen only when the kill script is run at 7:00pm each night. I can kill a user session from the unix prompt in exactly the same manner and cannot seem to reproduce this problem. Any ideas, anyone ????
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2005 03:51 AM
10-28-2005 03:51 AM
Re: multiplying defunct processes
Re-posted under Sys. Admin.
Closing this one.
Closing this one.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP