I'm having this same problem. I kicked off a scan of a /24 subnet yesterday
evening, and all but two were finished by 10:41 last night (according to the
log). However, two servers were still being scanned as of 9:00am this
morning, both were running find_service.nes, and both were hung. I killed
the PID for both find_service.nes process, and the scan quickly finished.
Anyone know what's causing this? Thanks.
--
Jared
on 2/21/2005 5:43 AM Matthew Romanek said the following:
> Hey all..
>
> I've been digging for this in the archives, but I can't find anything
> current and relevent. Feel free to point me at the answer if this has
> come up before..
>
> I'm scanning multiple /24s, and every now and then, on fairly
> populated networks, nessus will hang on one or more hosts. WHICH hosts
> seem to change, and I haven't gotten it to happen on the same host
> twice, even though I've reproduced the problem several times by
> scanning dense networks.
>
> Each time it happens, a ps shows two processes for one or more hosts,
> several hours after all the other hosts are apparently done. One is
> always find_service.nes, and the second one varies. Through
> experimentation, I've learned that I can kill -9 the process for
> find_service.nes and that host will take off, run through the other
> plugins, and finish happily as if nothing happened.
>
> I don't see anything in the dump or message files that would indicate
> a problem. I tried changing the timeout for the plugin, which didn't
> help, nor did reducing the scans to 10 tests and 15 hosts at a time.
>
> For a short-term fix, I've disabled that plugin, but if I could figure
> out why it's hanging in the first place, I'd feel better about it.
>
> Any ideas would be welcomed.
>
> Thanks!
> _______________________________________________
> Nessus mailing list
> Nessus@list.nessus.org
> http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
