Burton, thanks for the replies, they have given me some direction to look. I read through previous posts and can make out only part of what you're saying, as I am not a coder, I do have a little C/C++ knowledge and can make some sense of it, but that's about as far as it goes.
However, I will toss out a few tidbits I learned today. 1. I did find that in 3.2 that if I do not use the -c option, sessions will purge more often and the max number of sessions rides a lot smoother. There is a reason I started using -c about six months ago, but don't need to make this post any longer. 2. The application that I spoke of that does tons of little short sessions must be what is helping to cause the unsavory behavior. I watched Active TCP sessions grow and grow, filling to the brim with the aforementioned traffic. 3. Version 3.0 does indeed startup with --disable-instantsessionpurge set to "no" by default, and 3.2 sets it to "yes" (with either setting). Ultimately, it seems to me that the change of --disable-instantsessionpurge to a new default of 'yes' AND the influx of the new application's behaviour is causing me some difficulties. I have learned to skirt the issue with -c, but that's the way it goes I guess. Nathan Choate -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burton Strauss Sent: Friday, March 31, 2006 12:14 PM To: [email protected] Subject: RE: [Ntop] NTOP fails because of max sessions reached Read back over what I said in the long reply - the small # of currently active sessions could be setting the purge limit per cycle low too keep up. If that's the case, you'll see the # of stored sessions (in the textinfo.html report) grow, while the # of active sessions stays roughly constant... -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, March 31, 2006 9:04 AM To: [email protected] Subject: RE: [Ntop] NTOP fails because of max sessions reached I fired up the 3.0 version to find that the disable-instantsession purge was NO by default. Now you're saying that in 3.2 it's set to YES by default with now way to turn it off? I have looked at the globals-defines.h file you mentioned. Is there any settings I can make there, to set the behaviour back to where it won't run out of max sessions? My network isn't so busy that were running that many session over a 5m span. It definitely grows over a time of several hours until it max's out. Nathan Choate -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burton Strauss Sent: Thursday, March 30, 2006 6:08 PM To: [email protected] Subject: RE: [Ntop] NTOP fails because of max sessions reached --disable-instantsessionpurge should be the default ... It is the correct functionality. We simply didn't want to make a big change like that just before the release. I need to check the ./configure stuff and correct the docs - maybe make the option --enable-instantsessionpurge or some such. -----Burton _______________________________________________ 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
