Your message to ntop or ntop-dev has been seen.
However, you have:
* neglected to provide important information
- using the built-in problem report form is STRONGLY suggested.
* appear not to have taken advantage of existing information
or
* haven't taken other steps we ask you to do when posting to the
mailing list
Hence this semi-automated response.
Posting guidelines are in the docs/FAQ file in the source tree, and
(although perhaps not the latest copy) in the "HOWTO ask for help"
item at http://snapshot.ntop.org and at http://www.ntopsupport.com
in the documentation section.
1. ONE and only ONE problem / issue / question per message.
With a meaningful subject.
The goal is that if you're asking a common question, the
subject would have allowed you to find it in the back
traffic for the mailing list.
2. Search the back traffic on these lists. There is a searchable archive
at http://search.gmane.org
3. Read the docs/FAQ file in the source. You should get a recent version,
not one
from some old source .tgz. As a last resort, a HTMLed version is posted
in the
documentation section of http://www.ntopsupport.com.
4. Check snapshot, http://snapshot.ntop.org - this is a community FAQ
collection.
Entries from snapshot are migrated into docs/FAQ fairly routinely, but
the
newest stuff (and some oldies but goodies) are at snapshot.
5. We support only the current versions of ntop. This is either:
* the last release, v2.2.
* the cvs (and tell us the last time you did a checkout)
or
* the latest development version posted at SourceForge
(if there is one posted)
If you use a port/package and the latest version available for your
OS is some release candidate from a year ago, sorry. Contact the
packager and ask them to get current.
6. Post the information about your environment we ask for.
We STRONGLY suggest you use the automatically generated "Problem Report"
form that since it contains much of the necessary information.
7. Make sure you're in a supported environment (./configure --showoses).
If it's an unsupported environment, we're interested in your efforts to
make ntop work, but we don't have the time, resources, knowledge and/or
insterest to do it ourselves.
8. For software 'crashes', please run ntop under the gdb debugger and
capture
the full failure information. Brief instructions on using gdb are in the
docs/FAQ file.
-----Burton
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 3:11 PM
To: [EMAIL PROTECTED]
Subject: [Ntop] NEWBIE: Saving data after crash
Hello all, I'm new to the list, but we've been using Ntop off and on for
about 3 years. Basically, we turned it on and used the stats, nothing else
was done with it. We are now trying to do more with it, we have a flat
campus network of 1,500 devices and we want to use Ntop to monitor the
broadcast from the devices. I don't have Nmap installed and will need to do
so in the days ahead.
We currently have Ntop installed on a Compaq Laptop with a 850MHz CPU, 512MB
memory, Suse Linux 8.1 and Ntop 2.1.2. The server run's fine and had been
for 22 days, then it cored. I got a bunch of errors that said "Index
mismatch (hostTrafficBucket=1016/TheIdx=573)" and then "purgeHostIdx(0,573)
failed [host not found]" which repeated themselves every 10min for about 2
hours, then I got a segmentation fault and it cored. Is there anyway to
restart the server without loosing all the stats? Is this done with the
"-S" option?
Thanks
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop
