self-LOCKED message is a red herring - read the back traffic.
Again, this sounds like the syslog() not being thread safe problem (common
in kernel/glibc combinations prior to NPTL). SMP exposes it more often
(that's what I was able to find/fix it) and -t 4 also doesn't help.
1. Download the cvs.
2. use utils/linuxrelease to figure out what configureextra file is being
used:
$ utils/linuxrelease --distro
fedora
$ utils/linuxrelease --release
2
Translates to configureextra/LINUXfedora2
or configureextra/LINUXfedora
or configureextra/LINUX
(1st match)
Create a file for your version of Mandrake or edit the one that's already
there. Include the -DFORPRENPTL line from configureextra/LINUXredhat8.0
./configure, make, make install as per usual.
Post the info to ntop-dev for inclusion in the cvs.
-----Burton
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Florin
Sent: Thursday, March 31, 2005 1:15 PM
To: [email protected]
Subject: [Ntop-dev] SMP linux hangs with ntop
I got ntop 3.1 running in daemon mode on a P4 HT 2.8GHz, dual-channel 512MB
DDRAM, 80GB SATA HDD, Mandrake Linux 9.2, kernel 2.4.22mdk, used as a
gigabit router.
When using the SMP kernel, accessing the ntop web server causes system hang
after the message:
"Mar 31 21:56:56 ns2 ntop[3560]: **WARNING** tryLockMutex() called
'queuePacket' with a self-LOCKED mutex [EMAIL PROTECTED]:2219]"
Hard reset is the only way out.
If not running ntop, the system works fine with the SMP kernel.
The problem does not occur when booting the normal (uniprocessor) linux
kernel, even if the message is still there sometimes.
Is this a known problem with ntop?
Florin
_______________________________________________
Ntop-dev mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
_______________________________________________
Ntop-dev mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
