Looks like Luca already did the update - Christian sent it to him separately. This should be in the 17May2002 snapshot.
I did commit the more informative log messages, those will be in 18May2002... Thanks for your help in chasing this down! -----Burton -----Original Message----- From: mbano [mailto:mbano]On Behalf Of Marco Bano Sent: Friday, May 17, 2002 3:24 AM To: Burton M. Strauss III Subject: Re: [Ntop] May 14 ERROR: releaseMutex() call with a NULL mutex [reportUtils.c:749] Ok Burton, good news. I apply your patch to the 14 May distribution and it works fine. I change the line +++ ntop-current/reportUtils.c Thu May 16 13:49:28 2002 to +++ reportUtils.c Thu May 16 13:49:28 2002 and type the command patch -p0 < your-patch-file from the directory ./ntop-current/ntop that is generated untarring the ntop distribution. after I type: make make install now with -n flag ntop is not generating error logs. .. (apart that make it hanging netscape if I want to hightlight the info on a particular host that have lots of informations)... ciao _Marco "Burton M. Strauss III" wrote: > Update: > > Marco helped me pin this one down... it's because of the -n parameter. He's > testing a tiny patch, but this is not the more general case I alluded to > below. > > So, if you have any other releaseMutex NULL call messages, let us know... > > -----Burton > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Burton M. Strauss III > Sent: Wednesday, May 15, 2002 11:17 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: RE: [Ntop] May 14 ERROR: releaseMutex() call with a NULL mutex > [reportUtils.c:749] > > It happens periodically and nobody has ever been able to pin down why... > > The message in util.c is actually probably misleading. If it's happening > repeatable, I'd love you to do some debugging.... > > Given that it's in reportUtils.c, it's related to which pages you are > browsing... that information is critical! > > 1. As a first test, change _releaseMutex, around line 1000 so it looks like > this: > > int _releaseMutex(PthreadMutex *mutexId, > char* fileName, int fileLine) { > int rc; > > if(mutexId == NULL) { > traceEvent(TRACE_ERROR, > "ERROR: releaseMutex() call with a NULL mutex [%s:%d]\n", > fileName, fileLine); > return(-1); > } > if(!mutexId->isInitialized) { > traceEvent(TRACE_ERROR, > "ERROR: releaseMutex() call with a UN-INITIALIZED mutex > [%s:%d]\n", > fileName, fileLine); > return(-1); > } > ... > > That way we'll be able to tell if it's really NULL (really, really bad) or > just un-initialized (probably a more localized problem). > > 2. DRASTIC: in util.c, at the beginning, add > > #define SEMAPHORE_DEBUG 1 > > That will create A LOT of output, but show the pattern of lock/release etc. > > -----Burton > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Marco > Bano > Sent: Tuesday, May 14, 2002 9:49 AM > To: [EMAIL PROTECTED] > Subject: [Ntop] May 14 ERROR: releaseMutex() call with a NULL mutex > [reportUtils.c:749] > > Hallo, > > I am having lots of such messages on the syslog files when I try to > access ntop web page for throughtput (Data recv) . > > ntop snapshot 14.05.2002. linux rh 7.2 > > any help ?--- ideas... > > ciao > > Thanks in advance > > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop > > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
