i have deployed logAnalyzer and been using it for about 4 months. things seems to be working find but today i found out that my /var/log/syslog contains this
Aug 27 12:11:37 lion kernel: [ 6.347932] ata1.00: status: { DRDY ERR } Aug 27 12:11:37 lion kernel: [ 6.348008] ata1.00: error: { UNC } Aug 27 12:11:37 lion kernel: [ 6.372478] ata1.00: configured for UDMA/133 Aug 27 12:11:37 lion kernel: [ 6.372487] ata1: EH complete Aug 27 12:11:37 lion kernel: [ 9.059325] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 27 12:11:37 lion kernel: [ 9.059413] ata1.00: BMDMA stat 0x4 Aug 27 12:11:37 lion kernel: [ 9.059514] ata1.00: failed command: READ DMA Aug 27 12:11:37 lion kernel: [ 9.059620] ata1.00: cmd c8/00:08:08:78:1b/00:00:00:00:00/e2 tag 0 dma 4096 in Aug 27 12:11:37 lion kernel: [ 9.059621] res 51/40:00:0a:78:1b/00:00:00:00:00/e2 Emask 0x9 (media error) which is a hardware badsector notification. and i could not see this on log analyzer. however other logs from this server are showed as expected. i am using " *.* @@logserver.test.com " which means everything and this error is very critical , this must have showed in to the remote server. can anyone please help me to make it sending these types of critical error to log server. Thanks, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagwvfmkxnxsk+k2wzjq+5b4f5j6tavs6wcrfmehwfvqcsqh...@mail.gmail.com