From: Philip Craig <philipc@snapgear.com>
To: Frischknecht Peter <peter@empoweringsolutions.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Kernel: NET: messages suppressed (I am sure it has been covered before)
Date: Fri, 24 Oct 2003 13:34:16 +1000 [thread overview]
Message-ID: <3F989DB8.1070507@snapgear.com> (raw)
In-Reply-To: <3F41DBB59549A54482D4FC25AEEDCBE18B9A9F@MAIL-06VS.atlarge.net>
Frischknecht Peter wrote:
> I need to know WHAT MESSAGE WAS SUPPRESSED.
>
> I am getting slammed. My server will display anywhere from a few
> hundred to 50K messages suppressed.
>
> Previous posters have suggested that if I go early enough in my logs,
> that I will find the original suppressed message. NOT TRUE.
You should have one successful log message for every log message
indicating the number of suppressed log messages. Since your
/var/log/messages does not contain the successful log messages,
your syslogd must be configured to send them elsewhere.
Note that the number of suppressed log messages is always logged
at KERN_WARNING, but the actual message could be anything. I
would suspect that the actual log messages are KERN_DEBUG, and
your syslogd is configured to ignore them
--
Philip Craig - philipc@snapgear.com - http://www.SnapGear.com
SnapGear - Custom Embedded Solutions and Security Appliances
next prev parent reply other threads:[~2003-10-24 3:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 15:47 Kernel: NET: messages suppressed (I am sure it has been covered before) Frischknecht Peter
2003-10-23 16:03 ` Antony Stone
2003-10-23 19:06 ` Arnt Karlsen
2003-10-24 3:34 ` Philip Craig [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-28 9:57 Gaby Schilders
2003-10-24 2:35 Frischknecht Peter
2003-10-24 16:46 ` Peteris Krumins
2003-10-23 14:55 Frischknecht Peter
2003-10-23 14:34 Frischknecht Peter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F989DB8.1070507@snapgear.com \
--to=philipc@snapgear.com \
--cc=netfilter@lists.netfilter.org \
--cc=peter@empoweringsolutions.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox