Read the back traffic on this list - it's been discussed oh, 10 or more
times...
It's an artifact of collecting addition information about mutex locks and is
not a problem. It's more likely w/ SMP systems and multiple NICs.
The fix is in the CVS.
There's also a discussion in docs/FAQ, look for this:
Q. What does this log message (and others like it) mean?
**WARNING** releaseMutex() call with an UN-LOCKED mutex [hash.c:559] last
unlock [pid 22176, pbuf.c:2598]
...
-----Burton
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Preston Kutzner
Sent: Thursday, May 26, 2005 8:47 AM
To: Ntop Mailing List
Subject: [Ntop] Strange errors in messages log
Hello list,
I'm seeing some interesting logs in my /var/log/messages log related
to ntop. I'm not sure exactly what the problem is or how to fix it.
Here's what I'm seeing:
May 26 08:42:33 nexus ntop[20100]: **WARNING** tryLockMutex() called
'queuePacket' with a self-LOCKED mutex [EMAIL PROTECTED]:2219]
I get a bunch of these in my log file. I'm running ntop on our firewall,
running TSL 2.2 with Shorewall. I'm running ntop 3.1 MT in SSL mode with
the following command line:
ntop -L -M -W 3001 -i eth0,eth1,eth2 -d -u root
Does anyone have any idea what the problem might be?
--
Preston
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
