From: Leopold Aichinger <leai@utanet.at>
To: netfilter@lists.netfilter.org
Subject: cat /proc/ip_conntrack produces kernel panic
Date: Tue, 23 Mar 2004 09:57:23 +0100 [thread overview]
Message-ID: <405FFBF3.9060005@utanet.at> (raw)
Hallo to all netfilter-users
on my Redhat8 box I use the 2.4.25 pristine Kernel with freeswan-2.05
patch included (but the freeswan feature I don't use - this is only for
future plans)
The kernel is monolithic with all netfilter-features included which come
with this kernel version.
If I login as root with ssh and do a
cat /proc/net/ip_conntrack
the machine freeze and I get a kernel panic.
(What's real strange: I cannot reproduce this error - sometime the
kernel panic and sometime not).
What I definitly can say: You must be logged in remotly with ssh and
do a cat ip_conntrack. If I logged in on the machine directly
doing cat /proc/net/ip_conntrack I had never a problem.
When I used kernel 2.4.22-pre10 I had the same problem but I could
always reproduce the panic only by login per ssh and doing the cat
This was the reason why I upgraded to a newer kernel.
What I am interested in:
Is there anybody who had the same problem ?
Which kernel did/does he/she use? (version, modular, monolithic, ...)
Perhaps some useful informations:
ip_conntrack_max = 16384
(but typically I don't have more than 1200-1400 entries, and I think
that the machine never reached more than 2000 entries)
uname -a
Linux fw 2.4.25.#1 SMP Thu Feb 19 15:30:36 CET 2004 i686 i686 i386 GNU/Linux
mem: 1550948 total
there is squid running on the machine.
(its the only mem and cpu comsuming application running beside my
firewall-rules)
iptables -nL | wc -l
412
uptime
9:44am up 2:08, 1 user, load average: 0.10, 0.15, 0.10
thx for every reply
leopold aichinger
next reply other threads:[~2004-03-23 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 8:57 Leopold Aichinger [this message]
2004-03-23 17:53 ` cat /proc/ip_conntrack produces kernel panic Tom Eastep
2004-03-24 9:00 ` Leopold Aichinger
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=405FFBF3.9060005@utanet.at \
--to=leai@utanet.at \
--cc=netfilter@lists.netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox