mailing list archives
Re: crash report
From: David Fifield <david () bamsoftware com>
Date: Sun, 25 Aug 2013 11:24:02 -0700
On Sun, Aug 25, 2013 at 01:24:30AM -0500, ITS wrote:
The scan was retried with nothing else running and after a fresh boot.
RAM use never went above 6G on a 32G system. Attached is the
screenshot of the crash.
I can breack the 172.16.0.0/12 scan into 4 parts of /14 each, however
when it comes time to do the 10.0.0.0/8 scan breaking into units of
/14 will take forever in terms of human monitoring and intervention.
Let me know if I can enable any debugging or logging features to
assist in resolving this. I am happy to help any way I can..
You will be better off, in this case, using the command-line Nmap rather
than Zenmap for these big scans. Zenmaps keeps information about the
whole scan at once in memory, while Nmap uses only enough memory for a
few thousand hosts at a time. You can save the results to an XML file
(-oX option, http://nmap.org/book/output-formats-xml-output.html) and
open the XML in Zenmap later, after the scan is finished.
Sent through the dev mailing list
Archived at http://seclists.org/nmap-dev/