Chill out - I frankly don't give a damn what happens when it's closing down. And you shouldn't either.
While it's possible to patch the util.c functions to skip the messages if ntop is shutting down, why waste the effort - a few instructions for each packet vs. a couple of messages... no way Jose! If you do a controlled shutdown, via the web interface, that should be a clean shutdown. But if you control-c the process - all bets are off. Please STOP reporting ANY problems after you control-c -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Markus Rehbach Sent: Sunday, September 07, 2003 1:39 PM To: [EMAIL PROTECTED] Subject: [Ntop-dev] **ERROR** accessMutex() called 'scanIdleLoop' with an UN-INITIALIZED mutex [EMAIL PROTECTED]:487] Hi all, started the newest CVS version with the following script: rm -r /home/markus/ntop/* #ifconfig tap0 up 10.20.30.40 netmask 255.255.255.0 broadcast 10.20.30.255 tcpsic -s rand -d 127.0.0.1 -m 1 >/dev/null 2>&1 & #nprobe -i lo >/dev/null 2>&1 & /usr/local/bin/ntop -n -u markus -P ~markus/ntop -A /usr/local/bin/ntop -n -u markus -P ~markus/ntop -K -t 5 -M -i eth0,lo -b -z The tcpsic is for doing a little noise on the lo interface, not more. After a while I wanted to add another host to eth0 and ssh'ed to it. But the host wasn't added in any view. After my usual Ctrl-C there were the following messages: 07/Sep/2003 20:11:56 [pbuf:1740] THREADMGMT: Packet Processor thread (1026) terminated... 07/Sep/2003 20:11:56 [hash:471] IDLE_PURGE: Device 0 [eth0], up to 8 of 16384 hosts 07/Sep/2003 20:11:56 [util:1113] **ERROR** accessMutex() called 'scanIdleLoop' with an UN-INITIALIZED mutex [EMAIL PROTECTED]:487] 07/Sep/2003 20:11:56 [util:1316] **ERROR** releaseMutex() called with an UN-INITIALIZED mutex [EMAIL PROTECTED]:524] 07/Sep/2003 20:11:56 [util:1113] **ERROR** accessMutex() called 'scanIdleLoop' with an UN-INITIALIZED mutex [EMAIL PROTECTED]:487] 07/Sep/2003 20:11:56 [util:1316] **ERROR** releaseMutex() called with an UN-INITIALIZED mutex [EMAIL PROTECTED]:524] ..................repeated ca. 100 times 07/Sep/2003 20:11:57 [util:1113] **ERROR** accessMutex() called 'scanIdleLoop' with an UN-INITIALIZED mutex [EMAIL PROTECTED]:487] 07/Sep/2003 20:11:57 [util:1316] **ERROR** releaseMutex() called with an UN-INITIALIZED mutex [EMAIL PROTECTED]:524] 07/Sep/2003 20:11:57 [util:1113] **ERROR** accessMutex() called 'scanIdleLoop' with an UN-INITIALIZED mutex [EMAIL PROTECTED]:487] 07/Sep/2003 20:11:57 [ntop:874] CLEANUP: Freeing device eth0 (idx=0) 07/Sep/2003 20:11:57 [ntop:878] STATS: 2,343 packets received by filter on eth0 07/Sep/2003 20:11:57 [ntop:881] STATS: 0 packets dropped by kernel 07/Sep/2003 20:11:57 [ntop:883] STATS: 294 packets dropped by ntop 07/Sep/2003 20:11:57 [ntop:874] CLEANUP: Freeing device lo (idx=1) 07/Sep/2003 20:11:57 [ntop:878] STATS: 298 packets received by filter on lo 07/Sep/2003 20:11:57 [ntop:881] STATS: 0 packets dropped by kernel 07/Sep/2003 20:11:57 [ntop:883] STATS: 0 packets dropped by ntop 07/Sep/2003 20:11:57 [util:1316] **ERROR** releaseMutex() called with an UN-INITIALIZED mutex [EMAIL PROTECTED]:524] 07/Sep/2003 20:11:57 [util:1113] **ERROR** accessMutex() called 'scanIdleLoop' with an UN-INITIALIZED mutex [EMAIL PROTECTED]:487] /sbin/ntstart: line 11: 2041 Segmentation fault /usr/local/bin/ntop -n -u markus -P ~markus/ntop -K -t 5 -M -i eth0,lo -b -z I tried it with and without the -b and the -z-flag, everytime the same messages. Markus _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
