Signal 11 is a seg fault. W/o information there's nothing to diagnose. Run under gdb and capture the true failure point information, instructions are in docs/FAQ at the bottom. Unfortunately that's the only way I know to do it. And, of course, some weirder memory issues go away under gdb!
-----Burton (Please note that I am speaking only as an individual and not as a representative of my employer) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gary Gatten Sent: Tuesday, July 11, 2006 5:24 PM To: [email protected] Subject: [Ntop] ntop 3.2.1 process dying after some period of time - signal11 - FreeBSD 6.0 The only "interesting" record in messages is: kernel: pid 46197 (ntop), uid 65534: exited on signal 11 This was a CVS install. When I run with the -t and -K options, it doesn't seem to die. Without the -t 5 and -K switches it's maybe 2 - 3 weeks. With these switches it's ran for > 4 months. Here's my current config: -o -d -L --skip-version-check -x 16384 -X 65536 -m 10.0.0.0/8,192.168.0.0/16 Netflow plugin is active, NOT actually capturing packets - although I think libpcap is active as NIC is in promiscuous mode. Any ideas? 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." _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
