In question are a pair of identical nessus servers, running on freebsd 4.5.
They've been running well for a few months, and all scans were executed by
hand/X GUI.
Over the last couple days I've been building a little perl to do an nmap
ping sweep for every net I want to cover, drop out IPs I can't scan (like
our ho jetdirect cards that crash, getting them upgraded) and then feeds
that to a nessus using a custom nessusrc.
Something I did, presumably to the nessusrc file, is causing every kicked
off scan to run till the nmap finishes, and hangs. No difference if I run
the scan from the command line or from the x gui. However, if I kill the
nessus process, or stop the test in the gui the report has the nmap results
in there accurately. So presumably it is finishing and reporting, but the
parent nessus process is not then kicking off the next scan.
So I grabbed a working nesusrc from another machine with an identical nessus
version and I still get the same hang, always after nmap.
Next I deleted and reinstalled nessus. No difference.
I know this HAS to be config related as it worked and then not while in the
meantime there wasn't any change to nessus itself (that I'm aware I did).
A random mistake is a little less likely as I have the same symptom on 2
identical boxes, while I was only testing my perl on one.
Can anyone give me some tips on places to look, things to check, or has this
been seen before?
nessusd -d:
This is Nessus 1.2.4 for FreeBSD 4.5-RELEASE
compiled with gcc version 2.95.3 20010315 (release) [FreeBSD]
Current setup :
Experimental session-saving : enabled
Experimental KB saving : enabled
Thread manager : fork
nasl : 1.2.4
libnessus : 1.2.4
SSL support : enabled
SSL is used for client / server communication
Running as euid : 0
Thanks
Matt
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
