On Fri, 7 Jan 2011, peer482 wrote:
Although ulimit -a shows core file size unlimited, I dont't get any corefile. Do I need to complie with any special parameters?
It's possible that ntop is running in a directory to which it cannot write as the current user when the process dies. I was having issues generating core files with ntop for this exact reason (it seemed ntop was changing to a different directory by itself after starting). You can check the current working directory while it is running by looking in /proc, or by using something like lsof, and then change the permissions as necessary. Alternately, if the version of Linux you're using supports it you can alter the value in /proc/sys/kernel/core_pattern to have the core file be generated someplace else (like /tmp). The core(5) man page has full details on that.
Running with export MALLOC_CHECK_=0; ntop didnt change anything. It crashed quickly again. Another standard start of ntop ended after 20 hours. I don't understand why it was running longer time since I didnt change anything.
I was having a similar issue at one point. The backtrace seemed to indicate the problem was related to DNS resolving issues, and the workaround for it was to start ntop with the -n 0 option to turn off DNS lookups. Probably not the best solution, but it did work. I haven't had time to go through the code in greater depth to see if I can patch the actual problem.
_______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
