ackward system message...

[deCG]

One of our RX system generated syslog message:
''vmunix: Double bit error discovered in kernel memory'',''vmunix: Hardware Error'',''vmunix: I/O hardware error'',''vmunix: memory error'',''vmunix: file system is full'',''vmunix: I/O error'',''vmunix: SCSI*lbolt*'',''vmunix: table is full'',''fatal: vxvm'',''error: vxvm'';''-'';''-''

I looked syslog, resmon, mstm and etc.
But I could not find any of matching message from the system.

Have any of you gurus seen this message?

Thank you in advance.

[Sandman!]

Look under "/var/tombstones" if there is a ts99 file with the latest timestamp (or dated atleast as the syslog message). Sounds like an awful lot of problems going wrong here. Might be best to open a support call and have the experts at HP look at it.

[Bill Hassell]

> ''vmunix: Double bit error discovered in kernel memory'' ...

It is truly remarkable that this error message was recorded in syslog. Normally, a double bit error in kernel memory is uncorrectable and the system would have immediately crashed (no time to write anything). If your system has not recently crashed, look in /etc/shutdownlog to see if there is an unusual reboot message. IS the above a single error message in syslog.log?

[deCG]

Thank you for reply.
I will let you if anything comes up.

[Andrew Merritt_2]

Hi,
Was that all one syslog message, or several separate ones? Can you paste exactly what was in the syslog? Which version of HP-UX?

If it's all one log message, I'd say it was an error in the logging code, and direct you to HP support for further investigation.

Also, which model of rx was this? (With some of the latest systems, such as rx2660, some double bit errors are correctable.)

Andrew

[deCG]

Hi Andrew,

Server spec is RX7620, HPUX 11v2.

We have our own monitoring tools to pickup any message from various alert/warning logs.

Above error message was categorized with [Syslog], but now it is nowhere to be found.

[Andrew Merritt_2]

Hmm. If you have the syslog file from when the message was recorded by your monitoring tools, but the message is not present, I'd be inclined to suspect a problem with the monitoring tools.

If what you quoted was sent as one message, it looks more like something extracting a lot of possible error strings from somewhere than a real error.

Andrew

[deCG]

Monitoring tools uses 'grep' command every 1-2 minutes to find new log message.
There is nothing

I'd better open a case to find exact cause.

Thanks.

[Andrew Merritt_2]

Was there a time and date at the beginning of the message? If not, then it doesn't look like a syslog entry anyway.

Do you know what time your monitoring tools reported the error? Do you have the syslog file covering that time? If the message is not there, then the tools have a problem, messages don't disappear from syslog unless someone is editing it.

Andrew