 
| Subject: | |
| From: | |
| Reply To: | Craig M. Lalley |
| Date: | Tue, 12 Mar 2002 08:54:11 -0600 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Everyone,
I am seeing a strange situation, (MPE/iX 6.5 PP2)
:showproc 292;tree
QPRI CPUTIME STATE JOBNUM PIN (PROGRAM) STEP
C152 0:00.807 WAIT S182 292 (VTSERVER.NET.SYS) ķU
If you look at the pin in SOS or GLANCE it has (had) a father process,
pin 598. But if I try to look at the father process the system says
that the father process has died.
The session is still alive (not active) and can be aborted.
The real concern is that these orphaned processes are using in some
cases 700MB of memory. Most of the orphaned process are using only
~100MB.
This seems to happen frequently throughout the day. They do seem to
clean themselves up over time, not sure how long it takes though.
In the system log files I am seeing low level I/O errors corresponding
to virtual terminal devices.
Is this a network issue? Here is a copy of LINKCONTROL
Linkname: ELANLINK Linktype: IEEE8023 Linkstate: CONNECTED
Physical Path: 0/28/20
Current Station Address: 08-00-09-D4-B9-FA
Default Station Address: 08-00-09-D4-B9-FA
Current Receive Filter: broad(1) any(0) k_pckts(1) x_pckts(0)
Current Multicast Addresses:
09-00-09-00-00-01
Transmits no error 29417813 Receives no error 16791479
Transmit byte count 4921617 Receive byte count 2128260209
Transmits error 0 Receives error 0
Transmits deferred 102033 Carrier losses 0
****** Strange to have transmit deferred on a switch port.
Transmits 1 retry 7435 CRC errors 0
****** Why are there reties on a switch port?
Transmits >1 retry 2688 Frame losses 0
Trans 16 collisions 0 Whole byte errors 0
Trans late collision 0 Size range errors 0
802 chip restarts 0 Receives dropped 0
Heartbeat losses 0 Receives broadcast 1452820
Receives multicast 305
Linkname: LNK100A Linktype: 100BT Linkstate: CONNECTED
Physical Path: 2/28/48
Current Station Address: 00-10-83-18-A7-0B
Default Station Address: 00-10-83-18-A7-0B
Current Multicast Addresses:
09-00-09-00-00-01
Transmit bytes 3931823018 Receive bytes 836216676
Transmits 6910740 Receives 4891766
Transmits no error 6910740 Receives broadcast 185560
Transmits dropped 0 Receives multicast 1391
Transmits deferred 0 Receives no error 5808662
Transmits 1 retry 0 CRC or Maxsize error 0
Transmits >1 retry 0 Code or Align error 0
Trans 16 collisions 0 Recv dropped: addr 729945
********** That seems like a lot of packet loss. Any ideas?
Trans late collision 0 Recv dropped: buffer 0
Trans underruns 0 Recv dropped: dma 0
Carrier losses 0 Recv dropped: other 0
Link disconnects 0 Recv deferred 0
Link speed 100 Recv overruns 0
Link duplex Full Link auto sensed No
Link mode 100Base-TX Secs since clear 365005
Has anyone else seen this trick?
Is this a network issue?
Is this an O/S issue being aggravated by a network issue?
Any ideas and thoughts would be appreciated.
Thanks,
Craig M. Lalley
Systems Performance Specialist
Lund Performance Solutions
Phone (541) 812-7600 | Email [log in to unmask]
Fax (425) 920-4995| Web www.lund.com
NOTICE: This communication may contain privileged or other confidential
information. If you are not the intended recipient or believe that you
may have received this communication in error, please reply to the
sender indicating that fact and delete the copy you received. In
addition, you should not print, copy, retransmit, disseminate, or
otherwise use the information. Thank you.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|
