* cat /proc/ip_conntrack produces kernel panic
@ 2004-03-23 8:57 Leopold Aichinger
2004-03-23 17:53 ` Tom Eastep
0 siblings, 1 reply; 3+ messages in thread
From: Leopold Aichinger @ 2004-03-23 8:57 UTC (permalink / raw)
To: netfilter
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: cat /proc/ip_conntrack produces kernel panic
2004-03-23 8:57 cat /proc/ip_conntrack produces kernel panic Leopold Aichinger
@ 2004-03-23 17:53 ` Tom Eastep
2004-03-24 9:00 ` Leopold Aichinger
0 siblings, 1 reply; 3+ messages in thread
From: Tom Eastep @ 2004-03-23 17:53 UTC (permalink / raw)
To: Leopold Aichinger; +Cc: netfilter
Leopold Aichinger wrote:
>
> What I am interested in:
> Is there anybody who had the same problem ?
There have been some reports of similar panics on the Shorewall Users
mailing list. These are reported as panics from "shorewall show
connections" which is a thin wrapper around "cat /proc/net/ip_conntrack".
The most recent reports were using RedHat kernels 2.4.20-28.7 and
2.4.20-30.7
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: cat /proc/ip_conntrack produces kernel panic
2004-03-23 17:53 ` Tom Eastep
@ 2004-03-24 9:00 ` Leopold Aichinger
0 siblings, 0 replies; 3+ messages in thread
From: Leopold Aichinger @ 2004-03-24 9:00 UTC (permalink / raw)
To: teastep; +Cc: netfilter
> There have been some reports of similar panics on the Shorewall Users
> mailing list. These are reported as panics from "shorewall show
> connections" which is a thin wrapper around "cat
> /proc/net/ip_conntrack".
>
THX very much - I will search the shorewall mailing list
A google search brought no results.
My aim is to get a test machine where I can reproduce
this problem for debugging.
thx
leo
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-03-24 9:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-23 8:57 cat /proc/ip_conntrack produces kernel panic Leopold Aichinger
2004-03-23 17:53 ` Tom Eastep
2004-03-24 9:00 ` Leopold Aichinger
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.