I have a bit of a quirk with my nessus scanner.
First of all, I'm using the following version:
scanner$ /usr/local/sbin/nessusd -v
nessusd (Nessus) 2.2.2 for OpenBSD
(C) 1998 - 2004 Renaud Deraison <deraison@nessus.org>
When I start a scan (either using the command-line batch mode from localhost
(172.19.141.198) or over the network using scan lite), the user can login,
but then there is approximately a 30-120 second delay for the scan to start.
Observe the following...
scanner$ tail -f nessusd.messages
[Wed Sep 21 11:30:27 2005][19143] Caught HUP signal - reconfiguring nessusd
[Wed Sep 21 11:31:19 2005][3334] nessusd 2.2.2. started
[Wed Sep 21 11:31:49 2005][3334] connection from 172.19.141.198
[Wed Sep 21 11:31:49 2005][26664] Client requested protocol version 12.
[Wed Sep 21 11:31:49 2005][26664] successful login of scanuser from
172.19.141.198
[Wed Sep 21 11:33:06 2005][26664] Redirecting debugging output to
/data/scans/nessus/logs/nessusd.dump
[Wed Sep 21 11:33:49 2005][26664] user scanuser starts a new scan. Target(s)
: 172.19.141.197, with max_hosts = 20 and max_checks = 4
[Wed Sep 21 11:33:49 2005][26664] user scanuser : testing 172.19.141.197
(172.19.141.197) [9738]
Notice that the user logs in at 11:31:49, but scans don't start till
11:33:49!
The length of time that the user is idle before scanning varies, but it
never seems to drop below 30 seconds.
Has anyone else run into this problem? There are no other scans going on at
the time, and the machine (a dual P4 with 4GB of RAM) is completely idle.
Thanks for any assistance. I've tried moving to 2.2.4 as well, but the issue
persists.
- Eric
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
