SYSLOG.LOG messages

[David Carruthers]

Our system is not well. If only I knew how to interpret the kajillion messages in our syslog.log...

I've put a copy of our old syslog.log file on-line for anyone who wants to wade into it. Be warned, it's ugly. You can find a copy of it at:

ftp://ftp.interrain.org/seth/david/syslog/

Any thoughts besides getting rid of the system?

Thanks in advance to anyone who dares taking this on.
David.

[Tom Danzig]

I would contact HP support. My GUESS is you most likely have a failing disk based on the "Resetting SCSI bus / lbolt" messages. The ToolTalk errors can be ignored.

[melvyn burnard]

The ttdb error messages can be sorted out by applying the latest CDE patches, and reading document
KBRC00000053 on the ITRC site.

Regarding hte SCSI errors, I agree with Tom, get a hardware call logged.

[John Bolene]

This could be a number of hardware issues, from a cable going bad, controller going bad, disk going bad.

I agree, get your HP hardware dude to look at it before it gets worse.

Hopefully you have a system backup tape.

[Rita C Workman]

The lbolt message gives you alot of info..you just have to translate.
lbolt is generally indicative of hardware failure
the dev: 1f000000 gave you the device to translate
1f is hex for 31 and 31 is /dev/dsk so it's a disk
000000 is the address of the disk now drop the last
two 00 always...the rest gives you the address
c0t0d0
Another ex: 1f0x0a6000
would translate to /dev/dsk/c10t6d0

So your problem is related to a disk going bad. I'd address that first and then make sure everything that needs to be restored is done...then I'd start accessing the rest of the system.

Just my 2cents,
/rcw

[David Carruthers]

Thanks for all your feedback. I'll take a closer look at the SCSI issue and apply the CDE patch. Better yet, I'll let the HP tech look at both of these issues at 4:00 today when he drops by for a visit.

Thanks again for your thoughts.
David.