I have a router that passes up to 25m/bits of traffic everyday and flow-export to ntop. Ntop will run for about 5-7 minutes and seg fault after the hash size has hit 32768.
I've seen others listing this problem and point to the ntop.h for a possible cure, but I am using the precompiled RPM on RedHat 7.3. (I previously had a NetBSD 1.6 (i386) box, but the pkgsrc for ntop2.1 appears to be faulty for the browser interface.) (Thanks Burton for the assistance last week!) I have also tried flow-exports from just a 2610 that has a T1 and 60 percent circuit load at times with the same result just a longer death.. 20-30 mins before seg fault. If I built from source (ntop-03-01-10.tgz) and before compiling, change ntop.h to 65536 or higher would my hash problem go away?? The box has 320 megs RAM on a P-II 450. - When using the larger router I see my memory consumption for ntop grows rapidly, before ntop dies it burns about 267 megs of RAM. This is true for the other router exports as well, just takes longer.. I have read about a user that has this same problem and uses 512 megs RAM so my memory theory feels weak. What's the formula for flows to memory usage? I can stack the box with a gig of RAM if the chipset supports it and let you guys know if any head scratching starts.. Ashley Gates Director of Network Operations Atlanta Broadband, Inc. http://www.atlantabroadband.net Office: 770.794.0767 _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
