| Title: | "ASK THE WIZARDS" |
| Moderator: | QUARK::LIONEL |
| Created: | Mon Oct 30 1995 |
| Last Modified: | Mon May 12 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1857 |
| Total number of notes: | 3728 |
Return-Path: "VMS001::WWW"@vms001.das-x.dec.com Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX); Tue, 6 May 1997 15:33:11 -0400 Received: from vms001 by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV) id PAA17392; Tue, 6 May 1997 15:28:24 -0400 (EDT) Date: Tue, 6 May 1997 14:32:43 -0400 Message-Id: <[email protected]> From: "VMS001::WWW"@vms001.das-x.dec.com (06-May-1997 1432) To: [email protected], [email protected], [email protected] Subject: Ask the Wizard: 'David_A_Crews @ email.mobil.com' X-VMS-To: [email protected] Remote Host: (null) Browser Type: Mozilla/3.01 (Win16; I) Remote Info: <null> Name: Robert W. Brown/David A. Crews Email Address: David_A_Crews @ email.mobil.com CPU Architecture: VAX Version: V 5.5-2 Questions: How to delete/kill/stop phantom processes? We have a problem similar to the question in wizard/december-95/question_7.html Every once in a while we have a bunch of processes which go into limbo. The processes show up in the RWMBX state and lose name so the Process Name doesnt show up with SHOW SYSTEM or SHOW PROCESS/ID=xxx. In fact with SHOW PROCESS/ID=xxx, the error message is returned: %SYSTEM-F-SUSPENDED, process is suspended Pid Process Name State Pri I/O CPU Page flts Ph.Mem . . . 00018358 RWMBX 6 321666 0 00:04:33.80 2346229 512 ... 000192CA RWMBX 6 797 0 00:01:00.33 6834 475 ... 00001C65 RWMBX 6 1359000 0 00:14:47.81 9968908 503 ... 000033E8 RWMBX 9 1450817 0 00:17:11.33 9498828 497 000163D9 RWMBX 6 343392 0 00:05:02.30 2233192 512 00016D27 RWMBX 6 538996 0 00:06:58.28 3510229 498 00016D22 RWMBX 6 504886 0 00:06:54.34 3695140 512 The processes are frozen as far as I/O and CPU are concerned. The CPU time continues to increment about 1/100th of a second every 5 to 15 minutes. A STOP/ID=xxx can be repeated multiple times with no effect. How do we delete/kill/stop or get rid of these phantom processes (other than rebooting)?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1842.1 | Look At Application Mailbox Processing... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Mon May 12 1997 15:21 | 26 |
RWMBX is a resource wait for mailbox, and I'd guess these processes are waiting for a read from the process termination mailbox during process rundown. (This guess is based on the null process name, which is commonly seen only during process rundown, or when a local application neglected to set a process name when creating the process.) Please take a look at the application that started these processes, giving consideration to the termination mailbox processing that was likely requested, and the associated cleanup. And look at the source of the process itself, to determine what sort of mailbox processing is going on there. Using SDA (ANALYZE/SYSTEM) and the SHOW PROCESS/INDEX command, look for the termination mailbox unit number for the specific MBAu: device. A small program or even a DCL COPY command can likely read the contents of this mailbox, completing the process rundown operation. If this process does not have a termination mailbox (or is not waiting for it), then use the SDA> SHOW PROCESS/CHANNEL command to try to determine which mailbox is full. Once this is determined, one then must look for the reason why this mailbox is full. The STOP/ID command (and the $delrpc system service) are not effective against processes stuck in a resource wait, one must free the problem prior to being able to delete the process. | |||||