When are Logwatch errors really errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Hi All,

I don't know enough about when errors are *really* errors. So I google a lot to read and learn.

I have a few things in my Logwatch that I want to make sure I understand

1. smartd
**Unmatched Entries**
Problem creating device name scan list 
Device /dev/sda: using '-d sat' for ATA disk behind SAT layer. 
Device /dev/sdb: using '-d sat' for ATA disk behind SAT layer. 
Device: /dev/sdc, NO MEDIUM present; skip device 
Device: /dev/sdd, NO MEDIUM present; skip device 
Device: /dev/sde, NO MEDIUM present; skip device 
Device: /dev/sdf, NO MEDIUM present; skip device 

I googled and since I know the devices I have I can comment out
#DEVICESCAN -H -m root

and replace with:

/dev/sda -a -d sat -m root -M exec /usr/share/smartmontools/smartd-runner
/dev/sdb -a -d sat -m root -M exec /usr/share/smartmontools/smartd-runner

2. kernel

WARNING:  Kernel Errors Present
   amd64_edac: probe of 0000:00:18.2 failed with error -22 ...:  1 Time(s)

I googled this and I only had 5 hits that I could not make sense of. Can anyone shed some light?

3. automount
**Unmatched Entries**
lookup_read_master: lookup(nisplus): couldn't locate nis+ table auto.master: 1 Time(s)

I googled and this seems to be a RHEL bug?

Can anyone confirm and explain?

-Jason
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux