I havent seen it without traffic--i cant replace this running server at 
the moment ! .. but i can tell u one thing--even at off peak hours the 
server handles traffic of atleast 512kbps with a max of 2mbps which is 
comming from the ISP !

Alexey Talikov wrote:
> This messages appear with traffic or not ??
> 
> 31.05.2002 9:14:31, Arindam Haldar <[EMAIL PROTECTED]> wrote:
> 
>>hi to u all again !
>>i posted the below message yestreday... this log message keeps on commng 
>>in the messages file EVERY 1min & hence is filing up the disc space 
>>given for /var/log
>>pls .. i need some direction in knowing what could be the possible 
>>problem !..
>>Thanking u all in advance...
>>this is the message posted earlier.....
>>
>>hi all,
>>i am getting these messages in my /var/log/messages..
>>can someone tell me whats hapenning here..
>>iptables v1.2.7-2--2-423 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
>>May 30 05:10:04 cab1 kernel: ASSERT: ip_nat_core.c:743 
>>&ip_conntrack_lock not readlocked
>>May 30 05:10:04 cab1 kernel: ASSERT ip_conntrack_core.c:973 
>>&ip_conntrack_lock not readlocked
>>May 30 05:10:04 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
>>May 30 05:10:04 cab1 kernel: ASSERT: ip_nat_core.c:743 
>>&ip_conntrack_lock not readlocked
>>May 30 05:10:04 cab1 kernel: ASSERT: ip_nat_core.c:840 
>>&ip_conntrack_lock not readlocked
>>[root@cab1 root]#
>>
>>awaiting reply
>>a.h
>
>  
> -----------------------------------
> mailto:[EMAIL PROTECTED]
> BR
> Alexey Talikov
> FORTEK
> -----------------------------------
>


Reply via email to