Red Hat Bugzilla – Bug 825177
ntop 3.3.9-7.el5 crashes with glibc double free errors
Last modified: 2014-05-26 17:01:21 EDT
Description of problem:
The EPEL 5 version of ntop is 3.3.9 and crashes within minutes of startup with glibc double free errors.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install ntop-3.3.9-7.el5.x86_64.rpm from EPEL 5
2. Use `service ntop start` once configured with admin password
May 24 16:23:50 vfr1 kernel: ntop: segfault at 00000000aa80b4e5 rip 000000329540481c rsp 00000000433dcd90 error 4
Continues to run and does not crash
ntop was last updated in EPEL in 2009 and the upstream release is now 4.1.0
Have downloaded the EPEL 3.3.9-7 SRPM and rebuilt it using the 4.1.0 source tarball and this version runs fine so far (~1 hour so far and counting where it never managed more than 5 minutes before). Suggest that it might be time to rebuild the EPEL version against a newer upstream version...
Bug 493133 says that newer than 3.3.9 cannot be built for el5 because libevent is 1.1 and not 1.4 but it would appear that el5 5.8 now contains libevent 1.4 which would remove this roadblock.
Seems I spoke too soon, ntop 4.1.0 also crashes but lasts more like an hour than 5 minutes :-(
But ntop-5.0.2 works OK and has been running for several weeks without issue. Any chance of updating the EPEL version to use the latest svn code?
Would you like EPEL5 to get updated to 5.x as it resolves this bug? Does ntop currently work at all or is this an isolated issue?
Bug 325 on https://www.ntop.org/bugzilla3/show_bug.cgi is the bug report for this that fixed the problem for me. I have my own RPM built for this so the lack of a working copy in EPEL5 is not a problem for me now. Since 3.3.9 does not stay up for longer than 5 minutes for me, I'd guess the current EPEL5 copy is fairly useless though it may just not like our traffic pattern (several terabytes of SIP packets a month)
(In reply to comment #4)
> Bug 325 on https://www.ntop.org/bugzilla3/show_bug.cgi is the bug report for
> this that fixed the problem for me.
I cannot find this bug. Ntop bugzilla tells me that Bug #325 does not exist.
@Jonathan - I'd suggest not updating el5 to the latest ntop - it seems like a too invasive change for this late in the el5 cycle. Depending on what is in the ntop bugzilla entry we might be able to fix this bug with a patch to 3.3?
We are unable to get the updated ntop into EPEL5. EPEL6 has 5.x.