Re: 4.85BETA2 posted to Nmap download page - please test

[David Fifield <david () bamsoftware com>]

On Tue, Feb 03, 2009 at 12:25:41AM +0000, Brandon Enright wrote:
> Okay so I *still* haven't been able to get the memory issue to come
> up again.  However, I just run into (for the first time) a infinite
> loop(?) issue with NSE.  Basically what happened is the Nmap process
> started using 100% of the CPU, NSE stopped making an progress reporting:
>
> SCRIPT ENGINE Timing: About 78.91% done; ETC: 00:13 (0:01:04 remaining)
> SCRIPT ENGINE Timing: About 78.91% done; ETC: 00:13 (0:01:12 remaining)
> ...snip...
> SCRIPT ENGINE Timing: About 78.91% done; ETC: 00:15 (0:01:36 remaining)
> SCRIPT ENGINE Timing: About 78.91% done; ETC: 00:16 (0:01:44 remaining)
>
> Then, a host would timeout:
>
> SCRIPT ENGINE (1293.934s): Stopped ./scripts/pop3-brute.nse against a.b.1.47:10101 because of host timeout.
> SCRIPT ENGINE (1293.934s): Stopped ./scripts/pop3-capabilities.nse against a.b.1.47:10101 because of host timeout.
> ...snip...
> SCRIPT ENGINE (1293.934s): Stopped ./scripts/banner.nse against a.b.1.47:25 because of host timeout.
> SCRIPT ENGINE (1293.934s): Stopped ./scripts/smtp-open-relay.nse against a.b.1.47:25 because of host timeout.
>
> Then more zero-progress would be made:
>
> SCRIPT ENGINE Timing: About 83.67% done; ETC: 00:16 (0:01:21 remaining)
> SCRIPT ENGINE Timing: About 83.67% done; ETC: 00:17 (0:01:27 remaining)
>
> Then another host would timeout, and so on until all hosts timed out.
>
> Once the Nmap process hit 100% it stayed there for about 10 minutes,
> not a single script finished other than the ones that were timed out.
> That says to me that no script was really running and that something in
> the engine was eating all the cycles and preventing scripts from making
> progress.
>
> I could try sending a sig ABRT to make the process coredump if anyone
> though a coredump would help to analyze the state Nmap is in the next
> time something like this happens.

Are you still hitting this problem? A core dump might be useful. Patrick
is right that it won't help much if the problem is in a Lua thread, but
it might be in a C++ part of the engine. Does it happen with the nse-lua
branch?

David Fifield

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org