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
-----Original Message----- From: S-M Sent: Friday, January 07, 2011 11:26 To: CentOS mailing list Subject: [CentOS] When are Logwatch errors really errors
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
- 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
- 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?
- automount
**Unmatched Entries** lookup_read_master: lookup(nisplus): couldn't locate nis+ table auto.master: 1 Time(s)
This seems to be a new issue in 5 but not 4. Our nis domain controller is running centos 4, which does not include that in the map.
On side note, we noticed this issue while trying to get samba %N to work.
I googled and this seems to be a RHEL bug?
Can anyone confirm and explain?
-Jason _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
Jason Pyeron wrote:
From: S-M Sent: Friday, January 07, 2011 11:26
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
<snip>
- automount
**Unmatched Entries** lookup_read_master: lookup(nisplus): couldn't locate nis+ table auto.master: 1 Time(s)
This seems to be a new issue in 5 but not 4. Our nis domain controller is running centos 4, which does not include that in the map.
<snip> ObQuestion: why are you running something so insecure as NIS?
mark
-----Original Message----- From: m.roth Sent: Friday, January 07, 2011 12:45 To: CentOS mailing list Subject: Re: [CentOS] When are Logwatch errors really errors
Jason Pyeron wrote:
From: S-M Sent: Friday, January 07, 2011 11:26
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
<snip> >> 3. automount >> **Unmatched Entries** >> lookup_read_master: lookup(nisplus): couldn't locate nis+ table >> auto.master: 1 Time(s) > > This seems to be a new issue in 5 but not 4. Our nis domain controller > is running centos 4, which does not include that in the map. <snip> ObQuestion: why are you running something so insecure as NIS?
Legacy systems...
-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
At Fri, 7 Jan 2011 08:25:41 -0800 CentOS mailing list centos@centos.org wrote:
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
- 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
This will bite you if/when you install another disk drive.
You are better off with the 'DEVICESCAN -H -m root' option in place.
- 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?
- 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@centos.org http://lists.centos.org/mailman/listinfo/centos
Robert Heller wrote:
/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
This will bite you if/when you install another disk drive.
You are better off with the 'DEVICESCAN -H -m root' option in place.
Could you be more precise, please. Where exactly would you put this phrase?
/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
This will bite you if/when you install another disk drive.
You are better off with the 'DEVICESCAN -H -m root' option in place.
Could you be more precise, please. Where exactly would you put this phrase?
/etc/smartd.conf is where this is specified.
-Jason
At Fri, 07 Jan 2011 23:49:34 +0100 CentOS mailing list centos@centos.org wrote:
Robert Heller wrote:
/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
This will bite you if/when you install another disk drive.
You are better off with the 'DEVICESCAN -H -m root' option in place.
Could you be more precise, please. Where exactly would you put this phrase?
Right where it is in the default configuration for smartd (/etc/smartd.conf), where the OP commented it out.