HP3000-L Archives

August 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Wed, 16 Aug 2000 15:05:15 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (59 lines)
Re:
> Another thing I've noticed is the System Log file has filled up
> and has switched logs to another one.

Identify the most recently used log file, let's say it's 123, and try:

   :sysdiag
   logtool
   summarize log=123
   exit
   exit

That might provide a clue as to what's happening ... particularly
if it's unusual for a logfile to fill up rapidly.

> The symptoms starting occuring yesterday after a specific user
> using Minisoft's ODBC and consumed over 28% of the CPU.  Yet
> the symptoms persisted long after the user logged off.

How busy is the system?  (Preferably, via the "built-in speedometer",
visible when you press control-B at the console.
(see http://www.allegro.com/papers/dump.html#Speedometer for info on it)

>
> (from a VESoft menu)
> NM SYS   a.00.a9a4a0 dbg_abort_trace+$24
> NM PROG  551.000db6b8 EN_eprint+$11c
>     MAIN.PUB.VESOFT "SECLOGON"
> Program terminated in an error state.  (CIERR 976)
> CPU=6.  Connect=1.  yada yada yada....

On our copy of MAIN.PUB.VESOFT, that (EN_eprint+$11c) is
the return address from a call to QUIT ... which implied that
MAIN.PUB.VESOFT deliberately called the QUIT intrinsic for
some reason.


> (Another from I don't know what the user was in)
> An error (from TABLE MGT) was encountered when trying to obtain a message
> frame
> from the port's message pool. Usually, the error is due to the table (pool)
> being empty.
> Port (IPC) Facility message 170
> WARNING ** Message set 108, Error number 200 was not found in the system
> catalog

That's interesting...it implies that some message pool (structure where
messages for "message ports" are allocated) is out of free entries...
this generally implies that whatever process should be consuming the
messages (and doing something with them) is hung...leading to a
waxy buildup of messages...which in turn can cause other problems.


My guess: something is hung, and that's causing secondary problems.

Prediction: reboot
Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

ATOM RSS1 RSS2