Hello Folks @ 3000-l,

Re: diagmond

------------------------------------------------- Pete Crosby writes--
I believe this can indicate a lot of errors being logged in the
system logs. Use the LOGTOOL command to extract type 111 log records
(I/O errors) and see what you've got.

One occurrence of this in the past pointed to VT connections not
terminating properly. In that case all of the errors in the logs were
of the type:
----------------------------------------------------------------------

As Pete reports, cases have been see of "diagmond" consuming
significant CPU resources when processing type 111 - entries with
MPE XL STATUS: $FFCC0071 (device-offline).

It has been identified that both NS-VT VTSERVER and TELNET code have
a problem where io_ioreq entries are left in an ACTIVE state and can
fill the io_request_table.  These entries are of the type $d terminal
control.

In debug the io_request_table command displays the IO REQUEST TABLE,
the io_ioreq command will display a specific RID, the following
tblinfo command will display the size and current utilization of the
IO REQUEST TABLE:
  tbl_info(symval(kso_pointer(6f),'hlio_sanctum.ioreq_head'))

Details are documented in SR: 8606194879 (telnet), 8606180749 (ns-vt).

I did a search in HP-ITRC "io_request_table" and I was able to find
SR 8606194879 which includes documentation of the debug steps to
verify this problem.

The patches for NS-VT SR 8606180749 are:

6.0 NSSGD20
6.5 NSSGD21
7.0 NSSGD51

The patches for Telnet SR 8606194879 are:

6.0 PTDGD17
6.5 PTDGD18
7.0 tbd

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *