Heh, that's what I get for using my phone to read email. /red face/
Tim Doty
--- Original Message ---
From:"Doty, Timothy T." <tdoty@umr.edu>
Sent:Thu 2/22/07 6:39 pm
To:"mark.frost@uky.edu" <mark.frost@uky.edu>, "nessus@list.nessus.org"
<nessus@list.nessus.org>
Cc:
Subj:Re: Nessusd Segfaults
You've gone to a lot of effort -- have you sent that to the Tenable folks? It's
well beyond my experience and they /are/ the experts :)
--- Original Message ---
From:"Mark Frost" <mark.frost@uky.edu>
Sent:Thu 2/22/07 6:02 pm
To:"nessus@list.nessus.org" <nessus@list.nessus.org>
Cc:
Subj:Nessusd Segfaults
I had written some scripts to automate my nessus usage, and I began to
notice terrible segfault issues. The warnings began to appear roundabout
the time 3.0.2 came out, but I believe it was happening beforehand, it
just wasnt being verbose about it. I have always noticed Nessus seems to
not always scan some of the hosts I tell it to, and it seems as though
this is related. I am now using Nessus 3.0.5, and the problem persists.
Anyway, the visible output I get looks something like this:
> *** The daemon shut down the communication
> Connection closed by the server (SIGPIPE caught)
> send: Broken pipe
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send: Success
> send : Success
Various things about that seem strange to me. I dont understand why the
first one is a broken pipe, whereas the rest arent, and I DEFINITELY
dont understand why that last send has an extra space before the colon
(this is consistent. Every time this error occurs, the last send message
is formatted in that way.
After a great deal of extra debugging, I eliminated consistency. It
didnt always hap
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
|