I've taken steps to reduce the spikes in host counts, yet the segfaults after an IDLE_PURGE cycle are still prevalent. Anyone else having this issue? Any idea's how to fix this? I have gdb output and have posted it before. I can attach again if someone will actually do something with it. My skill set in C development/debugging is ever expanding, but they're exhausted for the time being.
TIA for any help! Gary ________________________________ From: Gary Gatten Sent: Friday, June 19, 2009 2:49 PM To: 'ntop@unipi.it' Subject: RE: [Ntop] crash after IDLE_PURGE PS: The only way I found this is the new graphs in 3.3.x that keep info about how many hosts ntop knows about. Whomever decided to add this - good idea! ________________________________ From: Gary Gatten Sent: Friday, June 19, 2009 2:01 PM To: Gary Gatten; 'ntop@unipi.it' Subject: RE: [Ntop] crash after IDLE_PURGE I MAY have found the trigger for this. Our internal A/V / Spyware / whatever scans our entire internal network range causing nTop to "see" about 50,000 hosts. I'm not 100% sure on the correlation, but it appears Ntop Crashes every couple hours when this discovery process runs. Not *every* time - but often enough I'm convinced it play at least some role in these crashes. Any thoughts? My -x and -X values are high enough to not cause any issues... ________________________________ From: Gary Gatten Sent: Thursday, June 18, 2009 11:22 AM To: 'ntop@unipi.it' Subject: RE: [Ntop] crash after IDLE_PURGE FWIW this is the last entry in the log: IDLE_PURGE: Device 1 [NetFlow-device.2]: 719/8486 hosts deleted, elapsed time is 0.494425 seconds (0.000688 per host) ________________________________ From: ntop-boun...@unipi.it [mailto:ntop-boun...@unipi.it] On Behalf Of Gary Gatten Sent: Thursday, June 18, 2009 11:19 AM To: ntop@unipi.it; ntop-...@unipi.it Subject: [Ntop] crash after IDLE_PURGE On 3.3.10 rev 3780 - Solaris 10 x86. Had this same problem on 3.2 on FreeBSD... Anyway, nTop blows up after an IDLE_PURGE cycle. There was no entry in the log this time even though I have -t 5 specified. On FreeBSD it would through a signal 11. "One" of the reasons I updated Is to hopefully solve this problem. I'll run it in gdb again and post anything I find. Anyone else having this issue? I have a lot of hosts "monitored' - like... 12,000 ish at times. Not sure if that's part of the problem or why it's more apparent for me? TIA! Gary "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font>
_______________________________________________ Ntop mailing list Ntop@unipi.it http://listgateway.unipi.it/mailman/listinfo/ntop
