It's not an error, it's a warning. Search the back traffic - it's usually harmless.
It's impact is on our ability to use the internal code to figure out what's wrong with threading. That's all. Shouldn't be any data impact. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Innocent Nwakor Sent: Saturday, July 21, 2007 11:12 AM To: [EMAIL PROTECTED] Subject: [Ntop] ERROR WITH NTOP HI, I have been getting these eroor fron Ntop and do not know how to solve it could you help me to get a solution to this Innocent **WARNING** tryLockMutex() called 'queuePacket' with a self-LOCKED mutex [EMAIL PROTECTED]:2219] J **WARNING** tryLockMutex() called 'queuePacket' with a self-LOCKED mutex [ ____________________________________________________________________________ ________ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433 _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
