I had nessus 2.2.3 running on my CentOS 4 admin workstation. THis week (after a yum update??) I started getting empty reports and Seg faults. I then installed 2.2.4 and now I see the following:
I can start the daemon, then start nessus and log in fine. But when I begin a scan the following error appears:
Connection closed by the server (SIGPIPE caught)


I click OK and then I get...
nessusd returned an empty report

From the nessus.messages log:
[Thu Apr 14 15:52:08 2005][28440] nessusd 2.2.4. started
[Thu Apr 14 15:52:20 2005][28440] connection from 127.0.0.1
[Thu Apr 14 15:52:20 2005][28445] Client requested protocol version 12.
[Thu Apr 14 15:52:20 2005][28445] successful login of micha from 127.0.0.1
[Thu Apr 14 15:52:36 2005][28445] SIGSEGV occured !

THere's nothing new in nessusd.dump

and my compilation options...

[EMAIL PROTECTED] log]# nessusd -d
This is Nessus 2.2.4 for Linux 2.6.9-5.0.3.EL
compiled with gcc version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)
Current setup :
       nasl                           : 2.2.4
       libnessus                      : 2.2.4
       SSL support                    : enabled
       SSL is used for client / server communication
       Running as euid                : 0

Can someone point me to a solution to this?

Thanks,
Micha



_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to