[SunRescue] Logging memory errors

[Paul Theodoropoulos]

That's controlled by your /etc/syslog.conf. just specify that you 
want whatever was sent to console (should also be insted in your 
syslog.conf) to go to a specific logfile. I have it go to 
/var/adm/messages.

I've been getting the following in my messages log on one of my 
e4500's for months now -

Dec  4 20:40:31 e4500a unix: CPU0 CE Error: AFSR 
0x00000000.00100000 AFAR 0x00000000.7f755c10 UDBH MemMod Board 0 
J3800
Dec  4 20:40:31 e4500a unix:    Syndrome 0xf8 Size 3 Offset 0 UPA 
MID 0
Dec  4 20:40:31 e4500a unix: Softerror: Persistent ECC Memory Error
Dec  4 20:40:31 e4500a unix:  Corrected MemMod Board 0 J3800
Dec  4 20:40:31 e4500a unix:    ECC Data Bit 11 was corrected

Haven't had time to swap out the module. Just keeps running and 
running, doesn't bat an eyelash.

I refuse to use anything but SPARC running Solaris for core 
infrastructure. Nothing is as reliable.

At 08:58 PM 12/4/00, you wrote:
>I just checked the console of my webserver today, and
>noticed I had parity errors (yet the system has been up for 68 
>days).
>Damn, is Solaris reliable on regular hardware.  Anyways, is there 
>a log where
>I can get this information for my records, or do I have to touch a 
>file to
>get it to start logging?
>
>THanks all,
>
>Paul
>
>P.S.  I should have DSL by the end of the month.
>
>
>_______________________________________________
>Rescue maillist  -  Rescue at sunhelp.org
>http://www.sunhelp.org/mailman/listinfo/rescue

-----------------------------------
Paul Theodoropoulos   paul at atgi.net
Senior Unix Systems Administrator
Advanced Telcom Group, Inc.
Santa Rosa, California
Work: http://www.atgi.net
Play: http://www.anastrophe.com
Downtime is Not an Option