Re: NSE errors

[Christopher Clements <christopher.a.clements () gmail com>]

Was able to reproduce, but I'm afraid I don't know enough about NSE's
innards to understand why:

NSOCK INFO [2586.2190s] nsock_trace_handler_callback(): Callback: WRITE
SUCCESS for EID 50611 [172.16.0.2:500]
NSE: UDP 192.168.0.1:839 > 172.16.0.2:500 | SEND
NSOCK INFO [2586.2710s] nsock_readbytes(): Read request for 1 bytes from
IOD #2251 [172.16.0.2:500] EID 50618
NSOCK INFO [2586.5740s] nsock_trace_handler_callback(): Callback: READ
TIMEOUT for EID 48922 [172.16.0.3:123]
NSE: rpc-grind: isRPC didn't receive response.
NSE: Target port 123 is not a RPC port.
NSE: Finished 'rpc-grind' (thread: 0x5cbcb60) against 172.16.0.3:123.
NSE: UDP 192.168.0.1:237 > 172.16.0.3:123 | CLOSE
NSOCK INFO [2586.5800s] nsi_delete(): nsi_delete (IOD #2181)
NSOCK INFO [2586.6330s] nsi_new2(): nsi_new (IOD #2252)
NSOCK INFO [2586.6340s] nsock_connect_tcp(): TCP connection requested to
172.16.0.1:2002 (IOD #2252) EID 50624
NSOCK ERROR [2586.6340s] nsock_make_socket(): Bind to 0.0.0.0 failed (IOD
#2252): Address already in use
NSOCK INFO [2586.6660s] nsock_trace_handler_callback(): Callback: CONNECT
SUCCESS for EID 50624 [172.16.0.1:2002]
NSE: TCP 192.168.0.1:46337 > 172.16.0.1:2002 | CONNECT
NSE: TCP 192.168.0.1:46337 > 172.16.0.1:2002 | 00000000: 80 00 00 28 41 a2
5e 58 00 00 00 00 00 00 00 02    (A ^X
00000010: 00 01 86 a0 00 00 00 02 00 00 00 00 00 00 00 00
00000020: 00 00 00 00 00 00 00 00 00 00 00 00

this was from a -d3 run.  I have the full run output if it would help.


On Wed, Apr 10, 2013 at 7:52 PM, Christopher Clements <
christopher.a.clements () gmail com> wrote:

> 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 use
> >
> > Do 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/