All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arindam Haldar <arindamhaldar@inbox.lv>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@lists.samba.org
Subject: Re: ip_net_ftp  message !
Date: Mon, 03 Jun 2002 17:49:28 +0530	[thread overview]
Message-ID: <3CFB5ED0.1020204@inbox.lv> (raw)
In-Reply-To: Pine.LNX.4.33.0206031349460.4790-100000@blackhole.kfki.hu

hi,

yes..:)... sorry for being a little cryptic ;)... but u guessed it right 
!..so i will summarize my 2 Question in this listing-->
1)i am getting these messages in my /var/log/messages..

  iptables v1.2.7-20020423 with  kernel 2.4.18 & patched htb3.3-020512 & 
imq-2.4.18...
May 30 05:09:58 cab1 kernel: ASSERT: ip_nat_core.c:840 
&ip_conntrack_lock not readlocked
May 30 05:10:04 cab1 kernel: ASSERT ip_nat_core.c:739
&ip_conntrack_lock_R71150de5 readlocked
May 30 05:10:04 cab1 kernel: ASSERT ip_conntrack_core.c:91
&ip_conntrack_lock_R71150de5 readlocked

this pattern message is being received every minute. !.. this system is 
on RH-7.2 with 512mb ram & has been running for a month now but the 
mesages started coming since may 30 !...

2) while insmod ip_nat_ftp(after ip_conntrack_ftp) & i got this message 
on RH-7.3(using RH-7.3 for 1st time !).. the kernel was downloaded from 
ftp.kernel.org & iptables v1.2.7-2002528 -->
ASSERT ip_conntrack_core.c:541 & ip_conntrack_lock not read locked !

i have similar configuration done on different pc(with rh7.2) with 
various iptables veriosn but didnt get any of the errors mentioned above !

ur help is my guidance...
regards
A.H



  reply	other threads:[~2002-06-03 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03 11:47 ip_net_ftp message ! Arindam Haldar
2002-06-03 11:52 ` Jozsef Kadlecsik
2002-06-03 12:19   ` Arindam Haldar [this message]
2002-06-03 12:39     ` Jozsef Kadlecsik
2002-06-04  4:08     ` Help NEEDED--sos !! Arindam Haldar
2002-06-04  8:10       ` Jozsef Kadlecsik
2002-06-05  4:47         ` Arindam Haldar
2002-06-05 10:58           ` George Georgalis

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=3CFB5ED0.1020204@inbox.lv \
    --to=arindamhaldar@inbox.lv \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter@lists.samba.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.