Hello all, the problem continues. Yesterday ntop crashed again. The logs are the same and also appears:
kernel: SKB BUG: Invalid truesize (812) len=649, sizeof(sk_buff)=172 repeated many times until ntop crashes. I have read about a kernel bug but I don´t know the solution. I hope, other be luckyer than me with Ntop. I´ll continue researching into a solution. Best Regards, Miguel Velasco -------- Mensaje original -------- Date: Tue, 02 Dec 2008 10:03:27 +0100 From: Miguel A. Velasco <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: [email protected] Subject: Re: [Ntop] warning: can't get client address: Bad file descriptor Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hello all, about this problem I think I´ve found a temporally solution at http://olympus.het.brown.edu/cgi-bin/dwww?type=file&location=/usr/share/doc/ntop/KNOWN_BUGS.gz I say temporally because I´ve disabled ssl support option at /etc/ntop.conf: --https-server 3203 .... and now it looks working fine. Ntop has been working properly for 2 days and before it just worked for some minutes. I hope I will be able to use ssl on ntop config at the future but at the moment I have a solution. I hope it could help someone with the same problem... Best regards, Miguel Velasco ------------------------------------------ Date: Mon, 24 Nov 2008 16:03:11 +0100 From: Miguel A. Velasco <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: [email protected] Subject: Re: [Ntop] warning: can't get client address: Bad file descriptor (Miguel A. Velasco) References: <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hello all, Radu, thanks very much for your help bun I´ve started ntop as you comment and the problem continues ... I have started ntop as follows: $ntop -w 3200 -W 3203 -i eth0,eth1,tun0 -d -L -a /var/log/ntop.log -u root -Q /dev/shm and the log in /var/log/messages when I start Ntop is the same: Nov 24 15:44:41 s-proxy ntop[32462]: THREADMGMT[t2915040144]: RRD: Throughput data collection: Thread starting [p32462] Nov 24 15:44:41 s-proxy ntop[32462]: THREADMGMT[t2915040144]: RRD: Throughput data collection: Thread running [p32462] Nov 24 15:46:21 s-proxy ntop[32462]: warning: can't get client address: Bad file descriptor Nov 24 15:46:34 s-proxy last message repeated 97 times After some minutes Ntop crash again .... I´ve been looking for an answer to this problem on internet for a long time but I´ve found the same question with no answers. Please, if someone has a solution for this problem, let me know. Thanks very much for your time. Miguel A.Velasco Radu Constantinescu escribió: > Try to run NTOP like: > ntop -u ntop --use-syslog=daemon --no-promiscuous --no-fc -Q /dev/shm -M -i > "eth1,eth2,eth0" & > (adapt to your needs) > where the interesting part is >>> -Q /dev/shm > See if that will help. It did fixed my problems on fedora like a charm. > > Radu > > -------- > > Message: 1 > Date: Tue, 18 Nov 2008 09:05:11 +0100 > From: "Miguel A. Velasco" <[EMAIL PROTECTED]> > Subject: Re: [Ntop] warning: can't get client address: Bad file > descriptor > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello all, I have the same problem with ntop in two different servers. I > have ntop-3.3.8-1.el5 in a Centos 5.2 release. > Ntop looks work succesfully but after some minutes it crashes. In > /var/log/messages I have something like this: > > Nov 18 08:59:15 s-analyzer ntop[14534]: warning: can't get client > address: Bad file descriptor > > It repeats n times until ntop crashes.... > I have been trying with different kernel versions but not succesfully. > I have the following /etc/ntop.conf: > > --user root > --db-file-path /var/ntop > --interface eth0,eth1,tun0 > --use-syslog=local1 > --http-server 3200 > --https-server 3203 > --daemon > > I am running at these servers a shorewall firewall, and openvpn service > in a tun0 interface. > > Please, let me know any solution. > Thanks vey much for your time. > > Miguel Velasco. > > > King, Morgan escribi?: >> >> >> I am running Ntop 3.2 on Centos 5.0. I have installed Ntop using yum >> and have also tried compiling it from source. Either way in my >> /var/log/messages I am getting the error saying >> >> >> >> Ntop[6946]: warning: can't get client address: Bad file descriptor. >> >> Last message repeated 49 times >> >> >> >> Sometimes Ntop Crashes after running for just a short time. Other times >> it runs for longer periods of time, the error remains. >> >> >> >> Thank you >> >> >> >> > > > >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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
