Nessus Digest, Vol 24, Issue 1

[Hellman, Matthew]

>>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.

Matt


-----Message Disclaimer-----

This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect at principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.

Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.