The CSV file is generated on the fly and therefore cannot be found on the local machine between executions.

The script counts down each host as the nmap process begins to scan that host, not when the scanning is completed. Execution of nmap-audit will stop once all nmap processes have finished scanning.

Check the processlist to make sure there are nmap processes currently executing.

If the messages are of the form "Unrecognized line: .*" then nmap is generating messages that have not yet been seen by the nmap-audit script. Perhaps you are using a newer version of nmap? If this problem persists after obtaining the latest version of nmap-audit, please send a note to the nmap-audit script maintainer with the nmap version and this will be addressed.

If one of the unrecognized lines is of the form "Interesting ports on.." this may have a significant impact on the operation of nmap-audit. If this line cannot be parsed then nmap-audit will not know what host is being scanned.

The other possability is that the messages you are seeing are errors generated by nmap rather then common messages. Since these errors may contain information to help you troubleshoot why a scan is not performing as expected they are not blocked by the nmap-audit script.

The most common messages generated are those relating to timeouts during a UDP port scan.

When this message occurs this means nmap-audit is unable to parse the output from nmap, specifically the line that notes what hostname and IP were just scanned. Without this information no report will be generated.

From reports I've gathered that this error seems to be happening mostly with users who've got a precompiled version of Perl that came with their Red Hat distribution. For these users recompiling Perl seems to fix this problem. Does anywho know why a regular expression would fail for some compilations (though same version) of Perl?

If you're using the most recent version of nmap-audit, please get in touch with. As much of the following information as possible is helpful to help me troubleshoot and correct this problem:

• The version of nmap-audit you're using (execute 'nmap-audit --version').
• The version of nmap you're using (execute 'nmap --version).
• The exact text of all "Unrecognized line:..." lines.
• A copy of the .nmap file located in 'dir-name' as defined in your nmap-audit.rc file (you can anonymize it, just don't chnage the format of the lines).