I took Nessus 3.0.0-fc4 for a test drive today and had an odd result. The
machine in question is a stock, fully updated FC4 install on a Dell laptop.
Everything went smoothly until I actually launched my first scan. The
nessusd process properly spawned nmap to begin the portscan and then
immediately pegged the CPU. Here's the last few lines of nessusd.messages:
[Mon Jan 2 15:37:00 2006][19339] user nessus : launching
dont_print_on_printers.nasl against 10.50.32.85 [4]
[Mon Jan 2 15:37:00 2006][19339] dont_print_on_printers.nasl (process 4)
finished its job in 0.003 seconds
[Mon Jan 2 15:37:00 2006][19339] user nessus : launching nmap.nasl against
10.50.32.85 [5]
The nessus.dump file is 0 bytes. Load average is 1.31 on a P4/1.8GHz with
512MB. When I run `strace -p 19339` (19339 = nessusd pid) I get lots of
this:
gettimeofday({1136234940, 135137}, NULL) = 0
read(7, 0xbfa54fbc, 8191) = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1136234940, 135313}, NULL) = 0
read(7, 0xbfa54fbc, 8191) = -1 EAGAIN (Resource temporarily
unavailable)gettimeofday({1136234940, 135505}, NULL) = 0
read(7, 0xbfa54fbc, 8191) = -1 EAGAIN (Resource temporarily
unavailable)gettimeofday({1136234940, 135681}, NULL) = 0
read(7, 0xbfa54fbc, 8191) = -1 EAGAIN (Resource temporarily unavailable)
...
While typing this message, nmap completed successfully, at which point
nessusd went back to a normal level of CPU usage and the scan completed
successfully. This is liveable, but I'm wondering if there's a fix or if
this information is useful to the Nessus team.
PaulM
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
