Nmap Development mailing list archives
Re: NSE errors
From: Christopher Clements <christopher.a.clements () gmail com>
Date: Wed, 10 Apr 2013 19:52:27 -0500
I'll try and reproduce tonight with a debug and see. The only thing unusual about this test was I used a large min-hostgroup (around 400 I believe). Chris On Apr 9, 2013, at 4:41 PM, David Fifield <david () bamsoftware com> wrote:
On Thu, Apr 04, 2013 at 12:56:31AM -0500, Christopher Clements wrote:I recieved the following errors when attempting to conduct an nmap scan of about 1k hosts tonight: NSE: Script scanning 304 hosts. NSE: Starting runlevel 1 (of 2) scan. Initiating NSE at 00:51 NSOCK ERROR [4293.3400s] nsock_make_socket(): Bind to 0.0.0.0 failed (IOD #8316): Address already in use NSE Timing: About 40.12% done; ETC: 00:53 (0:00:46 remaining) NSOCK ERROR [4305.8510s] nsock_make_socket(): Bind to 0.0.0.0 failed (IOD #8501): Address already in use NSOCK ERROR [4306.0770s] nsock_make_socket(): Bind to 0.0.0.0 failed (IOD #8510): Address already in useDo you know what command line caused these messages? It looks like two different NSE scripts are trying to bind to the same local port. David Fifield
_______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- NSE errors Christopher Clements (Apr 04)
- Re: NSE errors David Fifield (Apr 09)
- Re: NSE errors Christopher Clements (Apr 11)
- Re: NSE errors Christopher Clements (Apr 11)
- Re: NSE errors David Fifield (Apr 27)
- Re: NSE errors Christopher Clements (Apr 11)
- Re: NSE errors David Fifield (Apr 09)