I moved the box to a very lightly used segment and the problem still happened. But the one production box keeps up with whatever you through at it.
Shane ----- Original Message ----- From: "Aristeu Gil Alves Jr" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, December 17, 2004 1:00 PM Subject: Re: [Ntop] FreeBSD 4.9 and 4.10 > I have one similar problem with FreeBSD 5.x and 4.x. Ntop works fine > one or two days when it suddenly gets a very high CPU usage and the > daemon stops responding. > > I've did some verification with ktrace/kdump in this high CPU > situation, and the results (filtered) where > > #ktrace -p <NTOP PID> > > # kdump -l | grep files > 20703 ntop RET accept -1 errno 24 Too many open files > 20703 ntop RET socket -1 errno 24 Too many open files > 20703 ntop RET socket -1 errno 24 Too many open files > 20703 ntop RET accept -1 errno 24 Too many open files > 20703 ntop RET socket -1 errno 24 Too many open files > 20703 ntop RET socket -1 errno 24 Too many open files > 20703 ntop RET accept -1 errno 24 Too many open files > 20703 ntop RET socket -1 errno 24 Too many open files > 20703 ntop RET socket -1 errno 24 Too many open files > 20703 ntop RET accept -1 errno 24 Too many open files > (...) > > I've did some readjusting on FreeBSD kernel variables (kern.maxfiles, > kern.maxfilesperproc) but the problem still persists. > Even with maxfiles and maxfilesperproc adjusted to 60000, when > kern.openfiles gets ~1024, ntop goes to the scenario described. > Do I need to adjust maxusers too (now its 32, a reasonable number)? > Any tips are welcome. > > Regards, > --Aristeu > > > ----- Original Message ----- > From: "Luca Deri" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, December 17, 2004 12:22 PM > Subject: Re: [Ntop] FreeBSD 4.9 and 4.10 > > > > Shane, > > I spent quite some with with FreeBSD 5.x this week. All I can tell > you > > is that there are major threads problem on your platform (at least > on > > 5.x). I have now fixed (most of/all) the problems and ntop work > smoothly > > unless you use the libc_r that bugged (more than the pthread library > > that's bugged too). Please check the ntop code that's on CVS on 4.x > and > > let us know whether we need to patch the code. > > > > Thanks, Luca > > > > shane mullins wrote: > > > > >Hello all, > > > > > > We have a FreeBSD box running 4.9 and ntop 3.0, 550 Mhz, 640 MB > Ram, > > >Ide hard disk. Runs great and monitors a busy sement. We have > another > > >FreeBSD box running 4.10, 900 Mhz CPU, 1 Gig ram, Raid 5 and ntop > 4.10. > > >ntop runs fine for awhile on this box and then it just stops. > Should, I > > >just give up *BSD on my ntop boxes and run linux on my ntop boxes? > > >Nothing wrong with linux, I just know BSD. Or does FreeBSD support > ntop > > >3.1 better? > > > > > >Thanks, > > > > > >Shane > > > > > > > > >_______________________________________________ > > >Ntop mailing list > > >[EMAIL PROTECTED] > > >http://listgateway.unipi.it/mailman/listinfo/ntop > > > > > > > > > > > > -- > > Luca Deri <[EMAIL PROTECTED]> http://luca.ntop.org/ > > Hacker: someone who loves to program and enjoys being > > clever about it - Richard Stallman > > > > _______________________________________________ > > 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
