Paul,
Look at the log record Types

Use sysdiag/logtool/summarize log=n
then list log=n type=111

n=last logfile#

look at the IO errors for the potential offending devices. Could be a sign
of a bad hpib card,
scsi card, lan card, console card, or something *else*!

Mike




-----Original Message-----
From: Paul Courry <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Thursday, May 27, 1999 6:05 AM
Subject: LOG process terminated, no system logging


>Ran into a new one for me, predictive support informed me that system
logging, shown as LOG, process 39, priority BS 50
>stopped on it's own. It showed as an active process with no CPU time being
used, no records being added to the LOG5527 file
>and the file still showed as open under Listf and SOS by Lund.
>
>Since we couldn't reboot (24x7 operation, this HP runs a semiconductor
manufacturing operation, rebooting is *expensive*), HP
>went in with DEBUG and tweaked RAM to reenable logging.
>
>Note the following:
>
>1. No problem with disc space, we have 4.6gb free.
>2. No problem with stale log files being left out there
>3. No known power problems (big 'ol UPS) or other predictive support
problems
>4. No recent changes to SYSGEN or NMMGR
>
>I'm open to thoughts, theories and other ideas starting with T.
>
>Paul Courry
>International Rectifier