Interesting - I'll look into this and see if it helps me.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, April 15, 2008 2:14 AM
To: [email protected]
Subject: Re: [Ntop] rrd causing sig11 / segfaults

I'm running ntop with NetFlow and RRDPlugin enabled; no local
traffic; round about 10000 active hosts.
There where permanent ntop segmentation faults:
kernel: ntop[16623]: segfault at 000000010072719f rip
00002adb2c27dd26 rsp 0000000045008050 error 4

Specially at the time when ntop did many DNS operations.

Stopping the dump of domain data in RRDPlugin helped a little
bit.

What really helped was putting the temporary databases into
tmpfs.
/usr/bin/ntop -P /var/lib/ntop -Q /mnt/tmpfs
ntop is now running for days.

Be careful: the netflow RRD-file "throughput.rrd" also lies in
the path specified with -Q
You should save it before reboot.

Stefan



                                                                 
             "Gary Gatten"                                       
             <[EMAIL PROTECTED]                                       
             ell.com>                                         An 
             Gesendet von:           <[email protected]>             
             ntop-bounces@                                 Kopie 
             unipi.it                                            
                                                           Thema 
                                     Re: [Ntop] rrd causing      
             09.04.2008              sig11 / segfaults           
             16:43                                               
                                                                 
                                                                 
                 Bitte                                           
             antworten an                                        
             [email protected]                                       
                                                                 
                                                                 




I'm running the default protocol list and I think that's around
20 or?

I agree with the rrd code base.  Seems it doesn't handle
exceptions well - like if there's a file or directory not found
or a perms error or something.

Gary



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Colin Valentine
Sent: Monday, April 07, 2008 6:56 PM
To: [email protected]
Subject: Re: [Ntop] rrd causing sig11 / segfaults

I have crashes that look like an RRD graphing issue when tracking
large numbers of protocols (~40).  Backing back down to ~20 seems
to delay the issue.

Specifically, NTOP dies while drawing the graphs on the main
page.  Probably not related, but it makes me wonder about the RRD
code base.

Colin
On Mon, Apr 7, 2008 at 5:51 PM, Gary Gatten <[EMAIL PROTECTED]>
wrote:


Hello,





I've been working on this segfault issue for some time.  With rrd
enabled and detail set to "Full" ; "Hosts" and "Interfaces" - it
was crashing very often - sometimes several times / hour.  I
tried several options and am currently on "Full" detail but just
'Interfaces" - NO "Hosts".  It's been running for a week now with
no crashes.





I don't think rrd is the only thing causing my segfaults, but it
is definitely the cause of some.  I did run in the gdb and
captured the failures.  Bunch of stuff but mostly "no such file
or directory" caught my eye.  See the post for gdb attach: "Help
with segfault w 3.2.1 on FreeBSD 6.0 - GDB output attached"





Would like to get Host information back in the rrd tables, so any
help would be great!





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



"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





<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
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to