Craig please mail me (not to the list) a few DHCP packets I could use to reproduce the problem so I can fix it.
Thanks Luca ---- Luca Deri <[EMAIL PROTECTED]> You must be the change you want to see in the world Mahatma Gandhi On Aug 27, 2008, at 12:43 AM, Craig Orsinger wrote: > This is a followup to my own post. > > Setting the --disable-decoders flag stopped the crashes. The > computer on which Ntop 3.3.7 had invariably been crashing every time > its DHCP lease was renewed is still running Ntop five days later, > through multiple DHCP lease renewals. > > Of course, that's just a workaround, not a fix. But if you're having > the same sort of problem, this is something you may want to try. > > Thanks for the suggestions, BTW. > > > --- On Thu, 8/21/08, Craig Orsinger <[EMAIL PROTECTED]> wrote: > >> From: Craig Orsinger <[EMAIL PROTECTED]> >> Subject: [Ntop] Ntop 3.3.7 Crashes On DHCP Lease Update >> To: [email protected] >> Date: Thursday, August 21, 2008, 4:05 PM >> As I mentioned in a previous e-mail to this list, I've >> built Ntop 3.3.7 on Fedora 9. This was successful, except >> for this problem. >> >> The computer I'm testing this on uses DHCP to obtain >> its IP address. Every time this happens, this new version of >> Ntop crashes. It's happened three times now. Each time, >> this is the output as shown in the syslog: >> >> Aug 19 01:48:15 ge40403 dhclient: DHCPREQUEST on eth0 to >> X.X.X.65 port 67 >> Aug 19 01:48:15 ge40403 kernel: ntop[1255]: segfault at 38 >> ip 00204d63 sp b1e665c4 error 6 in >> libntop-3.3.7.so[1bf000+65000] >> Aug 19 01:48:15 ge40403 dhclient: DHCPACK from X.X.X.65 >> Aug 19 01:48:15 ge40403 kernel: device eth0 left >> promiscuous mode >> Aug 19 01:48:15 ge40403 dhclient: bound to X.X.X.70 -- >> renewal in 41094 seconds. >> >> I've removed the IP network address for privacy >> reasons, but those X's represent the same three numbers >> each time. >> >> This doesn't happen when I run Ntop version 3.3 on the >> same system. I'm running the new Ntop now with the >> --disable-decoders flag set to see if the problem is in the >> decoders. >> >> Has anyone else encountered this problem? If so, is there a >> fix? >> >> >> >> >> >> >> >> _______________________________________________ >> 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
