Nessus Digest, Vol 24, Issue 1

[Renaud Deraison]

On Oct 1, 2005, at 22:16, Hellman, Matthew wrote:

>>> I had nessus 2.2.5 running on my RedHat Enterprise 2.1 Server. THis
>>> morning (after a yum update) I started getting empty reports and Seg
>>> faults. 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've got the same problem.  This all started Friday. I was running  
> 2.2.4 and ran a scan and it worked fine.  Ran nessus-update-plugins  
> right after and then rescanned...and then started getting the empty  
> report errors.  Been meaning to update Nessus anyway, so installed  
> 2.2.5 and ran nessus-update-plugins.  Same problem.

Run nessus-update-plugins and try again -- does the problem persists ?