I forgot to mention the version of the OS I am running is Fedora Core 3. That
being said, I 
read another e-mail that appears to point the finger at the gcc library bundled
with the OS.
Specifically it mentions to modify a setting in the MALLOC_CHECK_ environment
variable. My
next question, is to what file in question do I make this change? Thanks.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kaplan, Andrew H.
Sent: Thursday, April 14, 2005 8:37 AM
To: Nessus (E-mail)
Subject: Problem with Automated and User-Interactive Nessus Scans


I was doing a check of our Nessus server (version 2.2.3) and noticed that this
past night's automated scans did not have any servers listed in its output
files. 
When I ran the automated scan this morning, the following output was observed:

Output from command /usr/local/bin/nessus -x -q 127.0.0.1 1241 <username>
<password> /<path to file>/windows
/usr/local/apache/htdocs/outputfiles/windows.html -T html ..

The daemon shut down the communication
The plugins that have the ability to crash remote services or hosts
have been disabled. You should activate them if you want your security
audit to be complete
Connection closed by the server (SIGPIPE caught)
send: Broken pipe
send: Success
send: Success
send: Success
send: Success
send: Success
repeated numerous times until
send : Success
Communication closed by server
nessus: nessusd abruptly shut the communication down - the test may be
incomplete

I also ran the Nessus GUI from the server and when I did so, I encountered an
error message that said the daemon shut the communication down. 

The nessus-update-plugins script was run last night, as part of a nightly
schedule, and was completed prior to the above mentioned automated scan. There
are two scans
which run nightly, and both generated the same output.

Does anyone have any idea what happened and what I need to do to correct it?
Thanks.




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

Reply via email to