Re: nmap: nsock_event.c:406: msevent_new: Assertion `msiod->state != NSIOD_STATE_DELETED' failed

[Henri Doreau <henri.doreau () gmail com>]

2012/11/12 Abuse 007 <abuse007 () gmail com>:
> Hi,
>
> I'm getting a nmap: nsock_event.c:406: msevent_new: Assertion `msiod->state
> != NSIOD_STATE_DELETED' failed error which is terminating nmap when
> scanning a range of addresses.
>
> The command I'm using is: nmap -Pn -A --script 'safe and not broadcast*'
> -oA nmap-x.x.x.224_27.`dt` x.x.x.224-255
>
> dt is a script to print out the date-time in ISO format (i.e.
> "20121112-153151")
>
> I'm using the nmap from SVN Revision: 29188, on Ubuntu 10.04.2 LTS,
> Linux 2.6.38 SMP i686.
>
> Output: -
>
> Starting Nmap 6.02 ( http://nmap.org ) at 2012-11-09 11:14 EST
> Pre-scan script results:
> |_eap-info: please specify an interface with -e
> | http-icloud-findmyiphone:
> |_  ERROR: No username or password was supplied
> | http-icloud-sendmsg:
> |_  ERROR: No username or password was supplied
> | http-virustotal:
> |_  ERROR: An API key is required in order to use this script (see
> description)
> | targets-asn:
> |_  targets-asn.asn is a mandatory parameter
> nmap: nsock_event.c:406: msevent_new: Assertion `msiod->state !=
> NSIOD_STATE_DELETED' failed.
> Aborted
>
>
> This was happening on an earlier revision, I tried checking out a later
> SVN, recompiling etc. Still hitting the issue.
>
> I search and found this post, http://seclists.org/nmap-dev/2012/q3/56,
> which was fixed.
>
> Is this a regression, or a separate issue?
>
> Can nmap's error handling be buffed up to not abort the whole scan, but log
> an error/warning instead. Also can more details about which session the
> event/assertion is related to be included in the error message so that
> users can skip over hosts or services that are causing the crash.
>
> Any troubleshooting I can do? I'd prefer not to use a debugger, but will if
> it helps. Will have limited time to test this target though.
>
> Thanks,
> Abu

Hello,

Do you know in which scan phase does the crash happen? A way to figure
this out is to increase the debug level.
In case it happens in NSE could you run the same command with
--script-trace and send the output (you can send it off-list and/or
anonimized).

Regards

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