kernel error?

Hi,

This weird thing happens to my web proxy server every around midnight
when the load is at its peak. I found thousands of messages like these
in /var/log/messages :
Sep 1 00:22:28 sumbawa kernel: printk: 73 messages suppressed.
Sep 1 00:22:36 sumbawa kernel: printk: 23 messages suppressed.
Sep 1 00:22:41 sumbawa kernel: printk: 1 messages suppressed.
Sep 1 00:22:43 sumbawa kernel: printk: 6 messages suppressed.
Sep 1 00:22:48 sumbawa kernel: printk: 89 messages suppressed.
Sep 1 00:22:56 sumbawa kernel: printk: 28 messages suppressed.
Sep 1 00:22:58 sumbawa kernel: printk: 10 messages suppressed.
Sep 1 00:23:04 sumbawa kernel: printk: 48 messages suppressed.
Sep 1 00:23:08 sumbawa kernel: printk: 46 messages suppressed.
Sep 1 00:23:13 sumbawa kernel: printk: 83 messages suppressed.
Sep 1 00:23:18 sumbawa kernel: printk: 24 messages suppressed.

When I checked with top, the load average was very low. But the
server's response was very slow. If the traffic goes down, the server
will be back to normal again. I had this problem once when I turned on
iptables, because the traffic surpassed the max limit for ip_contrack.
But this time, I didn't turn on iptables. I was wondering if Linux has
some kind of max connection hard coded into the kernel? Any idea? Please
help. Thank you very much.

Regards,
Vito

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.networking Vito Corleone <(E-Mail Removed)> suggested:

> This weird thing happens to my web proxy server every around midnight
> when the load is at its peak. I found thousands of messages like these

What is the peak?

> in /var/log/messages :
> Sep 1 00:22:28 sumbawa kernel: printk: 73 messages suppressed.
> Sep 1 00:22:36 sumbawa kernel: printk: 23 messages suppressed.
[..]

> When I checked with top, the load average was very low. But the
> server's response was very slow. If the traffic goes down, the server
> will be back to normal again. I had this problem once when I turned on
[..]

With the nearly zero information you provide it's nearly
impossible to suggest much. I'd run 'sar' from cron and see what
happens during the time you get those messages. What is the
output of 'uname -a'? Random guess, might be a faulty NIC, what
NICs are there ('lspci')?

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBNfwIAkPEju3Se5QRAu5tAJ9J8O7ejd7AEpkYNRZ8sw zGGOj0sgCdEXfZ
LByIeyH5uHNx+/PSWvcdvUQ=
=mwC1
-----END PGP SIGNATURE-----