[Ntop] queuePacket/dequeuePacket errors

[Arn Vollebregt]

Hello,

I am having some troubles with running NTOP on a 100Mbit network with quite 
some traffic to monitor. A short while after starting up the process the 
webinterface becomes sluggisch and unresponsive at times. When I check 
/var/log/messages I am seeing a flood of the errors below repeating

**WARNING** tryLockMutex() called 'queuePacket' with a self-LOCKED mutex 
[0x35a8d1c at pbuf.c:2219]
**WARNING** accessMutex() called 'dequeuePacket' with a self-LOCKED mutex 
[0x35a8d1c at pbuf.c:2399]

NTOP is also spawning multiple processes, at the time of writing I am up to 
9 NTOP processes, running for a small 5 minutes now.

I recon NTOP cannot keep up with the traffic or the amount of hosts and 
their data, are there ways to tweak NTOP? I figure the machine itself is not 
the problem, since it concerns a dual Xeon 2.4Ghz, 1Gig of RAM with a SCSI 
harddisk.

Arn Vollebregt

-- 
"Wisdom lies not in obtaining knowledge, but in using it in the right way"
 - kroesjnov