Increasing trace level is usually useless - there are only a few targeted additional logging messages for things we know about.
You will need to run under the debugger (instructions are in the FAQ) and capture the actual failure-point information. That's the only way. -----Burton _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Leonardos Sent: Thursday, January 24, 2008 1:20 PM To: [EMAIL PROTECTED] Subject: [Ntop-dev] NTOP Seg Fault RHEL4_x64 Hi, I have been fighting with NTOP on a RHEL4 64bit installation. I'm running the lastest subversion source as of today (Jan 24th 2008) no errors during autogen or compile Capturing on eth3 and eth4 ntop starts up fine. The Global Protocol default page works great, I see a list of ports in use and can click on them to few a list of hosts. I can even click on a host from this list and few the details on the host. Network Load works perfectly. However whenever I access Summary->Hosts or All Protocols->Traffic, Throughput, or Activity NTOP returns very quickly a completely blank page. Nothing in the log. If I try to increase the debug trace level instead of just returning a blank page I get a seg fault. Any suggestions on what to try next would be greatly appreciated. Best Regards, -Chris ntop configuration output follows:
_______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
