[prev in list] [next in list] [prev in thread] [next in thread]
List: ntop
Subject: Re: [Ntop] ntop dying with SegFault at line 26
From: "Gary Gatten" <Ggatten () waddell ! com>
Date: 2008-06-09 20:09:00
Message-ID: 70C0964126D66F458E688618E1CD008A0525BDE2 () WADPEXV0 ! waddell ! com
[Download RAW message or body]
5Gb / hour? How many hosts are you monitoring? There is also options
to "monitor" local hosts only - check out those options as well. Also
there are MANY options in "globals-define.c" - but of course requires
recompile after changes.
HTH
G
-----Original Message-----
From: ntop-bounces@unipi.it [mailto:ntop-bounces@unipi.it] On Behalf Of
Kevin Freels
Sent: Monday, June 09, 2008 2:50 PM
To: ntop@unipi.it
Subject: Re: [Ntop] ntop dying with SegFault at line 26
Okay, I give up. Where will I find (and set) RRD?
I reduced the ntop logging to "0", but it's still sucking up disk space
at about 5Gb/hour....
Is this configured on the build? I don't remember seeing anything when I
built ntop.
....k
-=-=-=-
> -----Original Message-----
> From: ntop-bounces@unipi.it [mailto:ntop-bounces@unipi.it] On
> Behalf Of Gary Gatten
> Sent: Monday, June 09, 2008 9:30 AM
> To: ntop@unipi.it
> Subject: Re: [Ntop] ntop dying with SegFault at line 26
>
> What are your RRD settings? Ie:, hosts, interfaces, domains,
> and what level of logging? If you have everything enabled
> and set to full - that's a LOT of data.
>
> G
>
>
> -----Original Message-----
> From: ntop-bounces@unipi.it [mailto:ntop-bounces@unipi.it] On
> Behalf Of Kevin Freels
> Sent: Monday, June 09, 2008 11:25 AM
> To: ntop@unipi.it
> Subject: Re: [Ntop] ntop dying with SegFault at line 26
>
> Now I have another issue.
>
> The system has been running fine, no un-anticipated exits or
> seg-faults.
>
>
> Well, not quite true...
>
> Now, the system, with almost 50Gb of free disk space is
> killing ntop because it runs out of disk space. The interface
> dirs under rrd are completely filling up with IP hosts data
> from all the hosts ntop touches. I added the "-x 4096"
> parameter, but that doesn't seem to help.
> We do not have --sticky-hosts set.
>
> So how do I (or can I) limit the amount of disk space ntop uses?
>
> ....k
> -=-=-=-
>
> > -----Original Message-----
> > From: ntop-bounces@unipi.it [mailto:ntop-bounces@unipi.it]
> On Behalf
> > Of Kevin Freels
> > Sent: Monday, June 02, 2008 1:42 PM
> > To: ntop@unipi.it
> > Subject: Re: [Ntop] ntop dying with SegFault at line 26
> >
> > Luca,
> >
> > I have started ntop with the CLI you prescribed. Here is
> the history
> > of the commands I had set up in the init.d script (commented-out
> > configs are ones I tried in succession):
> >
> > NTOPBin=/usr/local/bin/ntop
> > #NTOPCfg=" -w 3001 -i eth0,eth1 -M -c -d -t 5"
> > #NTOPCfg=" -w 3001 -i eth0,eth1 -M -c -t 5"
> > #NTOPCfg=" -w 3001 -i eth0 -c -t 5"
> > #NTOPCfg=" -w 3001 -i eth0 -c -t 5 -x 4096"
> > #NTOPCfg=" -w 3001 -i eth0,eth1 -M -z -t 5 -x 4096"
> > NTOPCfg=" -w 3001 -i eth0,eth1 -M -K -z -t 6 -x 4096"
> >
> > Over this last weekend, I limited the hosts hash and --sticky-hosts
> > with "-x 4096" and dropped the "-c". It ran all weekend
> long until the
> > disk filled up (but not from ntop, another issue). So perhaps the
> > --sticky-hosts and the host hash limits are the trick....? In any
> > event, it seems to be working now.
> >
> > I'll keep an eye on it for the week (or until it crashes).
> If it keeps
> > going, maybe I'll fool around with the host hash limit,
> incrementally
> > raising it. If anything happens to cause it to die, I'll forward on
> > the gruesome details.
> >
> > Thanks for the reply!!!
> >
> > ....k
> > -=-=-=-
> >
> > > -----Original Message-----
> > > From: ntop-bounces@unipi.it [mailto:ntop-bounces@unipi.it]
> > On Behalf
> > > Of Luca Deri
> > > Sent: Sunday, June 01, 2008 12:30 AM
> > > To: ntop@unipi.it
> > > Subject: Re: [Ntop] ntop dying with SegFault at line 26
> > >
> > > Kevin
> > > in what setup are you running ntop? WAN perhaps? What is
> > the exact CLI
> > > command you're using? Can you please start it from shell
> > and add -K -t
> > > 6 and send the log.
> > >
> > > Thanks Luca
> > _______________________________________________
> > Ntop mailing list
> > Ntop@unipi.it
> > http://listgateway.unipi.it/mailman/listinfo/ntop
> >
> _______________________________________________
> Ntop mailing list
> Ntop@unipi.it
> http://listgateway.unipi.it/mailman/listinfo/ntop
>
>
>
>
>
> <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
>
_______________________________________________
Ntop mailing list
Ntop@unipi.it
http://listgateway.unipi.it/mailman/listinfo/ntop
<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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic