From owner-freebsd-ports@FreeBSD.ORG Fri Nov 26 18:47:52 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EBD616A4CE; Fri, 26 Nov 2004 18:47:52 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B83C43D5E; Fri, 26 Nov 2004 18:47:52 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com (localhost [127.0.0.1])with ESMTP id 6423E2955B7; Fri, 26 Nov 2004 13:47:49 -0500 (EST) Received: from 207.219.213.163 (proxying for unknown) (SquirrelMail authenticated user mikej); by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with HTTP; Fri, 26 Nov 2004 13:47:49 -0500 (EST) Message-ID: <25343.207.219.213.163.1101494869.squirrel@207.219.213.163> Date: Fri, 26 Nov 2004 13:47:49 -0500 (EST) From: "Mike Jakubik" To: clement@FreeBSD.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-wettoast-MailScanner-Information: Please contact the ISP for more information X-wettoast-MailScanner: Found to be clean X-MailScanner-From: mikej@rogers.com cc: ports@freebsd.org cc: ntop-dev@listgateway.unipi.it Subject: ntop v3 consumes all cpu on FreeBSD 5.3 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 18:47:52 -0000 Hi, It seems that ntop will start to consume 100% of the cpu after its ran for ~30 min. I have found some old information regarding this issue here: http://listgateway.unipi.it/pipermail/ntop-dev/2004-July/004747.html This article describes using the option --set-pcap-nonblocking as a work around, due to some sort of pthread issues. Indeed this option is specified in the startup script, however ntop's man page does not list any such options. Instead it has something similar called "--pcap_setnonblock", however attempting to start ntop with this option causes it to exit with sig 11: --- Nov 26 12:02:37 sniffer ntop[2956]: CHKVER: Version file is from 'version.ntop.org' Nov 26 12:02:37 sniffer ntop[2956]: CHKVER: as of date is '2004-03-22T04:30:00' Nov 26 12:02:37 sniffer ntop[2956]: CHKVER: This version of ntop is the CURRENT stable version Nov 26 13:43:40 sniffer ntop[2956]: CLEANUP: ntop caught signal 15 Nov 26 13:43:40 sniffer ntop[2956]: CLEANUP: Cleaning up, set FLAG_NTOPSTATE_TERM Nov 26 13:43:40 sniffer ntop[2956]: SIGPIPE: Handled (ignored) 0 errors Nov 26 13:43:40 sniffer ntop[2956]: CLEANUP: Locking purge mutex (may block for a little while) Nov 26 13:43:40 sniffer ntop[2956]: CLEANUP: Locked purge mutex, continuing shutdown Nov 26 13:43:40 sniffer ntop[2956]: FREE_HOST: Start, 1 device(s) Nov 26 13:43:40 sniffer ntop[2956]: FREE_HOST: End, freed 87 Nov 26 13:43:40 sniffer ntop[2956]: PLUGIN_TERM: Unloading plugins (if any) Nov 26 13:43:40 sniffer ntop[2956]: RRD: Locking mutex (may block for a little while) Nov 26 13:43:40 sniffer ntop[2956]: RRD: Locked mutex, continuing shutdown Nov 26 13:43:40 sniffer ntop[2956]: RRD: killThread() succeeded Nov 26 13:43:40 sniffer ntop[2956]: RRD: Thanks for using the rrdPlugin Nov 26 13:43:40 sniffer ntop[2956]: RRD: Done Nov 26 13:43:40 sniffer kernel: pid 2956 (ntop), uid 65534: exited on signal 11 --- I observed the same behaviour on a different machine, running FreeBSD 4.10. Also, every now and then ntop will not respond in the broswer interface when cliking on random links. P.S: Please include me in the replies, as i am not subscribed to the list. Thank you.