[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nessus
Subject:    linux 2.6 / hangs
From:       Stuart Kendrick <skendric () fhcrc ! org>
Date:       2004-10-24 23:55:21
Message-ID: Pine.LNX.4.58.0410241646440.3801 () vishnu ! fhcrc ! org
[Download RAW message or body]

hi folks,

i've been whining over the last few weeks about how i can't get nessus to 
work ... i've just had a break-thru:

-if i change the 'Log file' parameter to 'syslog', then nessus scans
'hang' ... they get part way thru the port scan and then quit and just sit
there.

-if i leave the 'Log file' parameter at the default, the scan proceeds to 
completion ... finishes the port scan, and then launches the attack ... 
and logs the launch and completion of each nasl to the nessusd.messages 
file.  beautiful!


fairly thrilling to me, really -- this is the first time i've ever seen an
actual nessus scan complete ... prior to this ... i've just been staring
at 'hangs'.

oh, and the nessus 2.0.10a package from SuSE seems to be broken ... per 
Renaud's suggestion, i compiled it from scratch, and it worked fine.


here's a snippet from nessusd.conf:
# Log file (or 'syslog') :
# logfile = syslog
logfile = /opt/vdops/var/nessus/logs/nessusd.messages

if i uncomment the 'logfile = syslog' line and comment-out the 
'nessusd.messages' line, then nessus scans appear to 'hang', per my 
previous posts to this list.

i'm using compiled-from-scratch copies of nessus-2.2.0rc1 plus nmap-3.75
under SuSE 9.1.

if you know of a way to get the 'logfile = syslog' to work, i'd like to
hear about it -- i prefer to dump everything into syslog, rather than
segregating log files.


now, i'm going to go look at this report and see what i can learn about 
vulnerabilities ...

--sk

stuart kendrick
fhcrc


_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
[prev in list] [next in list] [prev in thread] [next in thread]