Displaying 20 results from an estimated 2000 matches similar to: "Bug#408037: logcheck-database: logcheck doesn't need to remind me my hard drive is dying, kthx"
2007 Jan 29
1
Bug#408037: will not fix
On Sat, Jan 27, 2007 at 02:40:41PM -0800, Steve Langasek wrote:
> On Sat, Jan 27, 2007 at 02:36:00PM +0000, martin f krafft wrote:
> > tags 408037 wontfix
> > thanks
>
> > Steve, I am not happy with filtering this message on the basis that
> > is *is* an uncorrectable sector and thus a problem that should get
> > fixed.
>
> No, smartd already sends its
2006 Apr 28
1
Bug#365121: logcheck: Fails to ignore certain pattern
Package: logcheck
Version: 1.2.43a
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have messages like these in my logs:
Apr 27 10:05:49 localhost smartd[9357]: Device: /dev/hda, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 58 to 57
Apr 27 10:05:49 localhost smartd[9357]: Device: /dev/hda, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 58 to 57
2008 Sep 11
3
Alarming (?) smartd reports
I decided, after the last discussion of smartd and S.M.A.R.T. disks,
to take a look in my /var/log/messages, and I'm seeing fair bit of
this:
Sep 10 20:11:23 mhrichter smartd[3361]: Device: /dev/sda, 4294967295
Offline uncorrectable sectors
Sep 10 20:41:23 mhrichter smartd[3361]: Device: /dev/hdb, 21 Currently
unreadable (pending) sectors
Sep 10 20:41:24 mhrichter smartd[3361]: Device:
2006 Jul 04
0
Processed: setting package to logcheck logcheck-database logtail, tagging 354820, tagging 355085, tagging 356681 ... ... ... ... ... ... ...
Processing commands for control at bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.9.20
> package logcheck logcheck-database logtail
Ignoring bugs not assigned to: logcheck-database logtail logcheck
> tags 354820 + pending
Bug#354820: rules to filter out entries caused by ssh scanners
Tags were: patch
Tags added: pending
> tags 355085 + pending
2013 Mar 25
1
Bug#703936: logcheck-database: SSH Bad Protocol Version Idenitifcation Rule is incomplete
Package: logcheck-database
Version: 1.3.13
Severity: normal
The rule for SSH ignoring "Bad protocol version identification" assumes there are no single quotes
inside the version string ('[^']'). I am however getting mails including those lines:
Mar 25 22:57:04 Debian-60-squeeze-64-minimal sshd[12144]: Bad protocol version identification
2010 May 25
1
Bug#583155: logcheck-database: Please create rules for amavis(d-new)
Package: logcheck-database
Version: 1.3.8
Severity: wishlist
HI,
can you please create a rule/some rules for amavis(d-new).
I get for every mail this mesage:
May 25 19:55:40 data amavis[9603]: (09603-15) Passed CLEAN, [::1] [213.165.64.22] <xxx at yyy.zz> -> \
<aaa at localhost>, Message-ID: <20100525175015.29677page1 at mx002.bbb.ccc>, mail_id: MM7upJv6se1Z, \
Hits:
2011 Jul 02
1
Bug#632471: logcheck-database: spamd child cleanup message broken after upgrade to squeeze
Package: logcheck-database
Version: 1.3.13
Severity: normal
Tags: patch
After upgrading to debian squeeze I get several messages a day in the form of:
Jul 2 15:05:15 hostname spamd[21286]: spamd: handled cleanup of child pid [28609] due to SIGCHLD: exit 0
This is due to an update in spamd, that makes the message more detailed (includes exit code)[1]. Therefore messages including exit code 0
2011 Apr 01
5
question on software raid
dmesg is not reporting any issues.
The /proc/mdstat looks fine.
md0 : active raid1 sdb1[1] sda1[0]
X blocks [2/2] [UU]
however /var/log/messages says:
smartd[3392] Device /dev/sda 20 offline uncorrectable sectors
The machine is running fine.. raid array looks good - what
is up with smartd?
THanks,
Jerry
2005 Sep 15
1
SMART error (OfflineUncorrectableSector) detected on host: SMART error (CurrentPendingSector) detected on host
Hello,
SMART error (OfflineUncorrectableSector) detected on host:
***************************************************************************
The following warning/error was logged by the smartd daemon:
Device: /dev/hdb, 2 Offline uncorrectable sectors
For details see host's SYSLOG (default: /var/log/messages).
You can also use the smartctl utility for further investigation.
No additional
2014 Feb 07
3
Software RAID1 Failure Help
I am running software RAID1 on a somewhat critical server. Today I
noticed one drive is giving errors. Good thing I had RAID. I planned
on upgrading this server in next month or so. Just wandering if there
was an easy way to fix this to avoid rushing the upgrade? Having a
single drive is slowing down reads as well, I think.
Thanks.
Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb
2012 Jun 13
0
Help with smartd
I have a system that is logging:
smartd /dev/sda currently unreadble (pending) sectors
smartd /dev/sda offline uncorrectable sectors
The box continues to run fine.
Doing "smartctl -H /dev/sda" says:
test result: PASSED
I have ran the "smartctl -t offline /dev/sda", after the 300+ seconds I
rebooted
and waited about 30 minutes and again got the above error, and smartctl
-H
2010 May 10
0
tracing the source of a sector error from smartd
I'm not used to using smartd, but have a new set of systems
that don't have any sort of RAID on them, so I enabled
smartd (18 systems 4 SATA drives each).
Running CentOS 5.4 64-bit ..
One of them has emailed me twice(despite it saying it
would only email me once) saying it has
1 Offline uncorrectable sectors
But when I try to find more information, smartctl seems to
think everything is
2007 Jan 16
0
Bug#407087: Logcheck rule update.
Package: logcheck-database
Version: 1.2.52
Severity: Minor
Tags: Patch
I've got a suggested rule update for the kernel file in the
/etc/logcheck/ignore.d.workstation directory.
The file already contains this rule:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: input: Logitech USB Mouse as /class/input/input[[:digit:]]+$
However my system was reporting the following two similar events:
2005 Feb 12
3
Bug#294950: logcheck: ignore.d.server courier imaplogin: DISCONNECTED not matching
Package: logcheck
Version: 1.2.34
Severity: normal
the ignore.d.server pattern for courier 'imaplogin: DISCONNECTED' does
not match the following line:
Feb 12 16:19:47 backup imaplogin: DISCONNECTED,
user=example at example.com, ip=[::ffff:111.111.111.111],
headers=14013, body=0, time=1
This line should be ignored like the other DISCONNECTED messages. Or am
I wrong?
-- System
2004 Oct 21
3
Bug#277636: logcheck-database: support for dnsmasq
Package: logcheck-database
Version: 1.2.28
Severity: wishlist
Could you add support for dnsmasq for the server profile?
This is the standard dnsmasq output.
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dnsmasq\[[[:digit:]]+\]: read /etc/hosts - [[:digit:]]+ addresses$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dnsmasq\[[[:digit:]]+\]: reading /etc/resolv.conf$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
2007 Dec 06
1
smartd.conf get overridden
Yohoo!
I have some issues with the smartd in CentOS5/x64
I edited the /etc/smartd.conf for my needs and restarted the smartd with
"service smartd restart". But the start script is overriding my file. I
checked it and saw the following lines:
---------------/etc/init.d/smartd------------
case "$1" in
start | reload | restart)
GEN_CONF="*SMARTD*AUTOGENERATED*"
[ !
2007 Mar 26
0
smartd on Centos 4.4
Hello,
I'm running CentOS 4.4 and am getting an error from smartd. This machine
has a single ide drive in it /dev/hda and i was getting a bootup error from
smartd, so i uncommented the /dev/hda line in /etc/smartd.conf. The error
persisted when i tried to restart smartd, i got a service restart failed and
the below error. Any suggestions?
On another unrelated subject i'm
2008 Aug 25
2
smartd
last night I checked the log messages on the server Dell PE2950 6xSAS 146G I
found the smartd running , I did not request such daemon
[root at PowerEdge1 pons]# tail -f /var/log/messages
Aug 25 08:27:30 PowerEdge1 smartd[8039]: Home page is
http://smartmontools.sourceforge.net/
Aug 25 08:27:30 PowerEdge1 smartd[8039]: Opened configuration file
/etc/smartd.conf
Aug 25 08:27:30 PowerEdge1
2008 Oct 10
2
smartd and 3ware on centos5
Hi,
I've CentOS5 box with 3ware RAID controller in it. I can't get the
tw_cli command line tool to work, and smartd also barks on me. The
tw_cli simply doesn't see the controller, no errors logged anywhere.
When starting smartd, it is much more verbose. I'm getting a bunch of
messages like this:
Oct 9 22:15:15 toporko kernel: program smartd is using a deprecated
SCSI ioctl,
2009 Jun 04
3
Plot and lm
I want to make a log-log plot with a regression line, but I can't figure
out what I'm doing wrong. What I'm trying is:
plot(mass,area, log="xy", pch=as.numeric(food))
abline(lm(mass~area))
or
plot(mass,area, log="xy", pch=as.numeric(food))
islands$logmass <- log(mass)
islands$logarea <- log(area)
attach(islands)
abline(lm(logmass~logarea))
But that does