Am Mit, 2003-10-08 um 18.26 schrieb Burton M. Strauss III: > I wonder, since it's related to -M, if you are seeing the same host on more > than one interface?? If so, it could be that it's being freed on the 1st > device's pass so that when the 2nd device pass comes along it's already > free... --trace-level 5 will enable the NOISY messages that show the purge > details. That might have a clue too... This are the log entries: [hash:522] IDLE_PURGE: FINISHED selection, 19 [out of 49] hosts selected [hash:552] IDLE_PURGE: Device 0 [eth0]: 19 hosts deleted, elapsed time is 1,921668 seconds (0,101140 per host) [hash:522] IDLE_PURGE: FINISHED selection, 26 [out of 59] hosts selected [hash:552] IDLE_PURGE: Device 1 [eth1]: 26 hosts deleted, elapsed time is 1,554777 seconds (0,059799 per host) [hash:522] IDLE_PURGE: FINISHED selection, 4 [out of 13] hosts selected [hash:552] IDLE_PURGE: Device 2 [eth2]: 4 hosts deleted, elapsed time is 0,647198 seconds (0,161800 per host) [hash:522] IDLE_PURGE: FINISHED selection, 0 [out of 5] hosts selected Okt 9 11:50:29 firedrake ntop[1544]: [hash:559] IDLE_PURGE: Device 3: no hosts deleted [hash:522] IDLE_PURGE: FINISHED selection, 39 [out of 76] hosts selected [hash:552] IDLE_PURGE: Device 0 [eth0]: 39 hosts deleted, elapsed time is 3,604439 seconds (0,092422 per host) [hash:522] IDLE_PURGE: FINISHED selection, 45 [out of 90] hosts selected At this point ntop always segfaulted.
Then I dropped the -m switch with my networks in the configuration, since then it seems to work. > It could also be another manifestation of the memory problem I posted this > weekend - Once the memory chains are corrupted, ANYTHING can happen. > > I wonder, can you run under valgrind or one of the other memory monitoring > tools? Running under Valgrind, I don't seem to get anything other than the > ultimately fatal situation, but there's got to be a root cause back in time > (usually it's a double free). If you can tag that, all kinds of problems > just disappear. > I didn't get valgrind to work right, ntop started but the webserver didn't come up. But vmstat with 1 second intervall didn't show unusual memory usage: procs memory swap io system cpu 0 0 0 4404 852744 39180 62544 0 0 0 50 175 113 0 0 100 0 0 0 4404 852664 39180 62544 0 0 0 0 449 472 0 0 99 0 0 0 4404 852660 39180 62544 0 0 0 0 105 15 0 0 100 0 0 0 4404 852652 39188 62544 0 0 0 20 136 59 0 0 100 0 0 0 4404 852652 39188 62544 0 0 0 0 222 175 1 1 98 0 0 0 4404 852628 39204 62544 0 0 0 14 154 87 0 0 100 0 0 0 4404 852628 39204 62544 0 0 0 0 122 40 0 0 100 0 0 1 4404 852596 39204 62544 0 0 0 0 259 233 0 0 100 0 0 0 4404 852584 39212 62544 0 0 0 6 109 34 27 22 51 <-- i think ntop crashes here 0 0 0 4404 852584 39212 62544 0 0 0 0 255 597 56 44 0 0 0 0 4404 852552 39236 62548 0 0 2 30 387 897 56 44 0 0 0 0 4404 866020 39236 62548 0 0 0 0 204 136 31 24 45 0 0 3 4404 866020 39248 62548 0 0 0 24 482 14 0 0 100 0 0 0 4404 866008 39260 62548 0 0 0 8 171 13 0 0 100 0 0 0 4404 866008 39260 62548 0 0 0 0 163 9 0 0 100 0 0 0 4404 866008 39260 62548 0 0 0 0 426 9 0 0 100 0 0 0 4404 866008 39260 62548 0 0 0 0 123 10 0 0 100 0 0 0 4404 866008 39260 62548 0 0 0 0 117 9 0 0 100 > > -----Burton _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
