aMule Forum
English => en_Linux => Topic started by: s0undt3ch on April 16, 2005, 05:59:21 PM
-
Hi ppl!
Got a big problem, for the second time, my kernel panic'ed.
I saw something about ???_contrac and amule
Now the real problem is that I can't find that message on the log.
I'm using gentoo and I am new to it, and I problably haven't set up my logger correctly, infact, I just emerged it, didn't do any configuration, all I have is messages.
What the kernel complained was not sincyng
Can anyone help? On at least make my logger log the kernel, so I can tell you the error I'm getting?
It will panic again in less that 24H....
-
Well, which logger did you emerge? sysklogd? You should activate the logger on boot time, just enter (as root) 'rc-update add boot' to start it from now on at boottime, then enter '/etc/init.d/ start' for the current session...
sysklogd should give you a /var/log/kern.log with the default configuration, no idea about syslog-ng or metalog as i never used them...
-
I emerged syslog-ng and it is started at boot time.
When I cmplained that it only had messages was becasue on mdk and fc3 logs we're separated, messages, security, boot, etc, and now on gentoo I only have messages, which I think log all together, but that kernel panic happened twice and didn't got cought by the logger, that's when I thought that it might be misconfigured...
-
aMule and indeed any userprogram should not be able to cause kernel-panics, so the fault lies with the kernel you are using. I'd suggest that you head over to the Gentoo forums and ask there instead, you'll probably get much better help there. ;)
Remember to specify which kernel-ebuild and which version you are using.
-
contrack? Maybe the message was: ip_conntrack table full: Dropping package.
This means only, that you have more connections than your PC can handle.
Just compre the output of `cat /proc/sys/net/ipv4/ip_conntrack_max` with the output of wc -l /proc/net/ip_contrack.
If the second value is the bigger one, you get this messages.
-
...But that still shouldn't trigger kernel panics ;)
-
I said: This means only. No word of kernel-panic. The problem is, that many users don't know how they can stop these messages, and if the loglevel isn't set, these messages go to the active console, which renders this ine unuseable.
-
Then how do I set the loglevel?
I'll get back on this question If I get the same panic, c'os there's a new kernel release for gentoo and I'm compiling it, also I've added/removed some option to the kernel. Let's see how it goes.
Anyway that loglevel setup would do wonders to me, and to a possible failure.
-
Amule is working for some time now, I just forgot to come here.
Aparently the kernel panics we due to a bad kernel configuration/compilation.
Since I recompiled it, have no probs.
Thanks,