similar to: Bug#355649: logcheck: ntp 'adjusting local clock' only matches positive corrections

Package: logcheck Version: 1.2.47 Severity: wishlist I'm running logcheck with an extended set of regular expressions on a desktop system. The CPU load of this system is normally very low, around 3%-5%. When logcheck starts scanning the logs, the CPU usage increases to 100% for several minutes and working on the system becomes difficult. I would therefore be very happy about if a

Package: logcheck Version: 1.2.43a Severity: normal -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.10 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 Versions of packages logcheck depends on: ii adduser 3.77 Add and remove

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

Package: logcheck Version: 1.2.43a Severity: wishlist The conf file currently says # Should the hostname of the generated mails be fully qualified? FQDN=1 I suggest rewording that to # Should the hostname in the subject of the generated mails be fully qualified? FQDN=1 The current wording led me to believe that the sender, and perhaps recipient (if otherwise unqualified) of the emails generated

Package: logcheck Version: 1.3.4 Severity: normal I am running debian/testing and just upgraded to logcheck 1.3.4 and it started reporting the error: mkdir: cannot create directory `/var/lock/logcheck': Permission denied I created the directory and chown'd it to logcheck and it seems fine now. Looking at the changelog, I see something was purposefully changed, so I imagine I

Package: logcheck-database Version: 1.2.43a Severity: minor Since last weekend's upgrade of logcheck-database from 1.2.42 to 1.2.43a, logcheck stopped ignoring routine SpamAssassin messages of the form Feb 20 21:36:16 tux64 spamd[4665]: spamd: checking message <20060220190721.0E0B41C5207 at llwb563.servidoresdns.net> for amu:7286 Could you please edit the second pattern in

Hello All, I have Asterisk 1.4.5 running on a SuSE 10.3 x86_64 2.6.18.2-34 I upgraded from 1.4.2 to 1.4.5 on sunday the 24 of june and since have been getting: Internal RTCP NTP clock skew detected: lsr=1402479300, now=1402675136, dlsr=196500 (2:998ms), diff=664 I see an entry in Mantis that Russell fixed code so that this will not show when it shouldn't. Would i be correct in

Hi list, I have a problem with this stuff, i read many documents about it but i would like to know if anyone have got to resolve the problem. The point is that my vm has the clock unsynchronize, i tried many things and it seems that its work fine but im not sure. Now im using ntpd to synchronize the time but im not trust on it because it didnt work before. First, i tried the jiffies on

https://bugzilla.samba.org/show_bug.cgi?id=9789 Summary: rsync hangs when NTP update system clock time Product: rsync Version: 2.6.2 Platform: PPC OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: abhinav0487 at gmail.com

Package: logcheck Version: 1.2.54 Followup-For: Bug #330220 root at ns2:/# ls -l /var/lock/ total 4 drwxr-xr-x 2 root root 4096 2007-01-30 15:40 logcheck I think chmod 775 on that file would fix this problem... -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked

OK guys and gals ... can we please stop all the fighting? When technical questions are asked, they should be answered. I lot of people on this list have something that a lot of newbies need ... experience. So answering a question with "RTFM" or "JFGI" is not going to impart any of your experience ... which is one of the things they need and want. Also ... if someone attacks

Package: logcheck-database Version: 1.2.43a Followup-For: Bug #355364 sorry but the previous patch was wrong the rules has to match both nagios: and nagios2: (and NOT nagios[...]:) so the pattern is nagios[2]*: (instead of nagios\[[0-9]+\]:) -- Cyril Chaboisseau

Package: logcheck-database Version: 1.2.43a Severity: normal Tags: patch Hi, Given the following popa3d log messages: popa3d[15636]: 0 messages (0 bytes) loaded popa3d[15993]: 1 message (3837 bytes) loaded popa3d[15856]: 3 messages (18116 bytes) loaded The current logcheck ruleset does not take into account that sometimes there might be multiple message_S_ to be loaded. The following patch

Package: logcheck-database Version: 1.2.43a Severity: wishlist when nagios2 is installed logcheck doesn't catch system messages with the existing (nagios) rules please, change "nagios:" to "nagios\[[0-9]+\]:" for all lines thanks -- Cyril Chaboisseau -------------- next part -------------- --- nagios 2005-10-23 06:13:15.000000000 +0200 +++ nagios.new 2006-03-05

Package: logcheck-database Version: 1.2.43a Severity: wishlist -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I recently switched to syslog-ng. Here are some lines that can be ignored. syslog-ng: Changing permissions on special file /dev/xconsole syslog-ng: STATS: dropped 2 - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'),

Hi, I had the following problem today. Because of a misconfigured network switch one system suddenly didn't have any network. After a reboot (with the network still unavailable) NTPD refused to start. Most likely because the initial ntpdate failed to work. I find this troubling, because when the network was restored, NTPD could have resumed working (like I'd expect from a true

Package: logcheck Version: 1.2.54 Severity: normal In the file ignore.d.paranoid/cron there are the rules ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ CRON\[[0-9]+\]: \(pam_[[:alnum:]]+\) session opened for user [[:alnum:]-]+ by \(uid=[0-9]+\)$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ CRON\[[0-9]+\]: \(pam_[[:alnum:]]+\) session closed for user [[:alnum:]-]+$ to ignore lines like 10:17:01 at 04-03-2007 tooar

Package: logcheck Version: 1.2.35 Severity: minor Current manual reads: EXAMPLES logcheck can be invoked directly thanks to su(8) or sudo(8), which change the user ID: logcheck -o -t Check the logfiles without updating the offset. Print everything to STDOUT I believe this shuold be formatted as: EXAMPLES logcheck can be invoked directly thanks

I'm planning to deploy a personal dovecot IMAP server (i.e. I am the only user) in a FreeBSD jail. At present, I have IMAP deployed on the same host as one of my mail servers, which is running Postfix. I do like Postfix, but it seems to be a bit overkill for this particular situation. All my incoming MX are provided by Google. They handle the incoming mail and forward to my private MX,

Package: logcheck Version: 1.2.51 Severity: normal Logcheck has an implicit assumption that the default locale should be used by grep when processing log files. However, that's not always the case. For example, I use the locale "en_US.UTF-8", and consequently grep assumes that its inputs are encoded as UTF-8. But the log files appear to be encoded as ISO 8859-1, which means that