From: Christopher Chan <cchan@outblaze.com>
To: netdev@oss.sgi.com
Cc: Yusuf Goolamabbas <yusufg@outblaze.com>
Subject: High number of concurrent connections causes 2.6.4 to go berserk
Date: Fri, 02 Apr 2004 08:57:05 +0800 [thread overview]
Message-ID: <406CBA60.50103@outblaze.com> (raw)
KERNEL: assertion (flags & MSG_PEEK) failed a[t net/ipv4/tcp.c (1571)
KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags & (MSG_PEEK |
MSG_TRUNC))) failed at net/ipv4/tcp.c (1635)
These are repeated in the logs during kernel berserk period
postfix is running on this box.
It is set to spawn max 750 smtpd processes to handle incoming smtp sessions.
When tcp_max_syn_backlog is set to 4096 and
route.max_size = 131072
route.gc_thresh = 65536
the box goes berserk almost immediately after bootup due to a bounce
flood hitting the box.
The below values seem to workaround whatever problem the kernel has.
tcp_max_syn_backlog = 2048
route.max_size = 1048576
route.gc_thresh = 65536
next reply other threads:[~2004-04-02 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 0:57 Christopher Chan [this message]
2004-04-02 3:28 ` High number of concurrent connections causes 2.6.4 to go berserk Nivedita Singhvi
2004-04-02 4:00 ` Christopher Chan
2004-04-02 16:37 ` Christopher Chan
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=406CBA60.50103@outblaze.com \
--to=cchan@outblaze.com \
--cc=netdev@oss.sgi.com \
--cc=yusufg@outblaze.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;
as well as URLs for NNTP newsgroup(s).