I recently upgraded from 2.0.something to 2.2.3. Now, whenever I do a scan, the
whole scan just seems to stop near the beginning of the test. The portscans
finish, and the "check" progress bar gets maybe 2% of the way through, and it
just stays there. I started a scan yesterday evening, and when I came in this
morning, that's where it was. I stopped that test altogether and started a new
one later today (on a different network), and it stopped in the same place.
A tcpdump shows no network activity to or from the scanner. The system load was
far lower than it is when a scan is really going on. Looking at the process
list, most of the nessus processes were doing check_services.nes, but a few
were doing other tests. All of those processes were about 3 hours old, and
hadn't gotten anywhere during that time. Doing a kill -9 on them would get the
scan going again for that target (a regular kill had no effect), so after
killing them all the scan keeps going. I haven't let it finish after that
point yet, because as I understand it lots of tests rely on the output of
check_services, so if that didn't successfully finish then I'm probably not
doing all the tests I should be.
Shouldn't Nessus be automatically killing any test that takes too long anyway?
I did a complete wipe of the old 2.0.x install, and I didn't change any of the
default settings after the 2.2.3 install, except for changing the scan type to
a SYN scan, so all my settings should be the defaults.
Any ideas what might be going on?
Thanks,
Frank
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
