All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martijn Klingens <mklingens@ism.nl>
To: lartc@vger.kernel.org
Subject: [LARTC] Strange log messages with CBQ?
Date: Wed, 13 Nov 2002 10:17:05 +0000	[thread overview]
Message-ID: <marc-lartc-103718271922293@msgid-missing> (raw)

Yesterday I started using CBQ in production on our firewall over an IMQ 
device, but since then I get a lot of messages in my syslog like below:

On Wednesday 13 November 2002 09:07, root@ism.nl wrote:
> Nov 13 08:01:36 firewall kernel: NET: 1 messages suppressed. 
> Nov 13 08:12:36 firewall kernel: NET: 1 messages suppressed. 
> Nov 13 08:18:36 firewall kernel: NET: 1 messages suppressed. 
> Nov 13 08:19:36 firewall kernel: NET: 1 messages suppressed. 
> Nov 13 08:20:36 firewall kernel: NET: 1 messages suppressed. 
> Nov 13 08:25:36 firewall kernel: NET: 1 messages suppressed. 
> Nov 13 08:30:55 firewall kernel: NET: 1 messages suppressed. 
> Nov 13 08:39:06 firewall kernel: NET: 1 messages suppressed. 
> Nov 13 08:41:25 firewall kernel: NET: 1 messages suppressed. 
> Nov 13 08:44:36 firewall kernel: NET: 1 messages suppressed. 

Any idea what may cause this? It really seems CBQ is causing this. I am 
running IMQ for a few days now, but without doing actual shaping, and I the 
syslog remains calm. But from the moment I added CBQ I get lots of these. 
Doesn't look like coincidence to me :)

Thanks in advance for any help.
-- 
Martijn

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-11-13 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 10:17 Martijn Klingens [this message]
2002-11-13 11:06 ` [LARTC] Strange log messages with CBQ? Martijn Klingens
2002-11-13 13:55 ` bert hubert
2002-11-14 16:36 ` Martijn Klingens

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=marc-lartc-103718271922293@msgid-missing \
    --to=mklingens@ism.nl \
    --cc=lartc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.