It's not an ERROR, it's clearly labeled as a WARNING!  And that's what it
is!


Two+ NICs and SMP?  That's the most common case where it's seen. I've traced
100s of hours of ntop execution with a lot of added instrumentation and
caught PRECISELY one instance (adding the extra traceEvents() or printf()s
hides it).  From that trace, it appears that there's a race in the optimized
code when you have multiple processors which goes away if you remove -O2.

Read the code in util.c and think about out-of-order execution of this block
of code

  if(!myGlobals.disableMutexExtraInfo) {
    myPid=getpid();
    if(mutexId->isLocked) {
      if((fileLine == mutexId->lockLine)
         && (strcmp(fileName, mutexId->lockFile) == 0)
         && (myPid == mutexId->lockPid)
         && (pthread_equal(mutexId->lockThread, pthread_self()))) {
        traceEvent(CONST_TRACE_WARNING,
                   "accessMutex() called '%s' with a self-LOCKED mutex
[EMAIL PROTECTED]:%d]",
                   where, (void*)&(mutexId->mutex), fileName, fileLine);
      }
    }

    strcpy(mutexId->lockAttemptFile, fileName);
    mutexId->lockAttemptLine=fileLine;
    mutexId->lockAttemptPid=myPid;
  }

with 2 processors.  That's the ONLY way I can see for the message to
appear...

Also, search the back traffic for this list...

-----Burton


US-based commercial support for ntop:
     http://www.ntopsupport.com
     mailto:[EMAIL PROTECTED]

Search the ntop mailing lists at gmane:
     http://search.gmane.org

HowTo Ask for Help at
     http://snapshot.ntop.org/faq.php#83


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
> Michael Gale
> Sent: Wednesday, January 14, 2004 10:08 AM
> To: [EMAIL PROTECTED]
> Subject: [Ntop] I think this is a simple question - tryLockMutex ?
>
>
> Hello,
>
>       I can swear I remember reading about this message some where, what
> causes it and how to fix the issue. But now I can not find the doc :(
>
> Any ways here is the following error that is printed on the console,
> ntop seems to be running great regardless. May be because I compiled
> with ignoresigpipe ?
>
> **WARNING** tryLockMutex() called 'queuePacket' with a self-LOCKED mutex
> [EMAIL PROTECTED]:2114]
>
> I am running slackware 9.1 with ntop-current (ntop-04-01-12), please let
> me know if you need any other info.
>
> --
> Michael Gale
> Network Administrator
> Utilitran Corporation
> _______________________________________________
> Ntop mailing list
> [EMAIL PROTECTED]
> http://listgateway.unipi.it/mailman/listinfo/ntop
>

_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to