- Get Started
Below you can find what we offer you in terms of support.
Note: in order to fill-in bug reports you must first create a new bugzilla account
Community Support: Mailing Lists
Shall you still have a question concerning ntop, please subscribe to the ntop mailing list(s) and the post your message.
Note: in order to reduce spam, users cannot post messages unless they are subscribed to the list.
Currently there are two mailing lists available:
|email@example.com||Bug reports, extensions, etc. related to ntop development||More Info (Un/Subscribe)|
|firstname.lastname@example.org||General questions about ntop (all that’s not suitable for ntop-dev)||More Info (Un/Subscribe)|
|email@example.com||General questions about ntop-related stuff (e.g. nProbe, nBox, PF_RING)||More Info (Un/Subscribe)|
Please send us suggestions, bug reports, enhancements, new packages you’ve built.
Everything is welcome!
Submitting a Code Patch
If you want to submit a patch please mail it (as attachment) to firstname.lastname@example.org.
What To Do In Case Of Crash
In the unlikely case of crash, we need to apply a code patch. In addition to reporting the problem verbally, it is helpful to also try to debug the application so that we can have an idea of where the problem could be. You do not have to be a programmer to do that, as with some simple steps you can help us making debugging easier.
Step 1. Enable Debugging In The Code
By default the GNU toolchain enables debugging symbols in the Makefile. Unfortunately it also enables code optimization that makes debugging difficult. Thus you need to remove optimization doing these simple steps:
cd <ntop or nProbe directory>
plugins/Makefilefiles and remove from it
-Os. Note that depending on your platform it might be that
-Osis no present. Save the
Step 2. Run The Application
The GNU toolchain creates the binary files inside the .libs directory. You need to run the code from such directory and not from the directory where you have compiled ntop or nProbe. Most platforms do not generate core dumps in case of crash thus it’s also necessary to enable core dump generation prior to run the code. This is done in different wait depending on the shell you use.
cd <ntop or nProbe directory>/.libs
ln -s ../plugins .(nProbe with Plugins and ntop)
ln -s ../html .(ntop only)
sudo su(become root)
ulimit -c unlimited(bash) or
limit coredumpsize unlimited(tcsh)
export LD_LIBRARY_PATH=.(Linux) or
export DYLD_LIBRARY_PATH=.(Mac OS X).
- Finally run the application:
./ntop <put your options here>
Step 3. Wait Until The Problem Shows Up
Crashing the application is something that can take some time. Thus you have to be patient, and use the application as usual. When the crash happens a core dump should be generated. Depending on the platform the core is saved into the same directory where you have started the application, or on MacOS X it can be found in the
/cores directory. Usually the core file is named
core, sometimes it has a PID (process ID) appended to it
Step 4. Analyze The Core File
In order to analyze the core file you need to install the
gdb debugger. Done that you can debug the core as follows (we suppose you use the bash shell and that you are still in the
cd <ntop or nProbe directory>/.libs directory).:
- Run the gdb:
gdb ntop core. At this point the debugger will open a shell where you can run commands.
#0 0x00007fff96a6ee42 in __semwait_signal ()
#1 0x00007fff92d55dea in nanosleep ()
#2 0x00000001060d7601 in _ntopSleepMSWhileSameState (file=0x105fa8d82 "main.c", line=678, ulDelay=5000) at util.c:4103
#3 0x00000001060d77e9 in _ntopSleepWhileSameState (file=0x105fa8d82 "main.c", line=678, secs=5) at util.c:4131
#4 0x0000000105f9eb09 in main (argc=6, argv=0x7fff65b99ae0) at main.c:678
- Show threads information
(gdb) info threads
6 0x00007fff96a6faf2 in read ()
5 0x00007fff96a6edf2 in select$DARWIN_EXTSN ()
4 0x00007fff96a6ebca in __psynch_cvwait ()
3 0x00007fff96a6ee42 in __semwait_signal ()
2 0x00007fff96a6ee42 in __semwait_signal ()
* 1 0x00007fff96a6ee42 in __semwait_signal ()