More information - when I am attempting to restore the sessions in question, I notice that the client seems to "hang" on several ip's. I looked through the logs and session files, and find that these "hanging" ip addresses have the following characteristics:
<session>-index reports the address as having been scanned nessusd.messages reports the scan against the address to be finished <session>-data has NO "HOST-END" statement for the address Could it be that the client awaits "host-end" statements for the addresses, and continues to queue up more addresses to process into a results report, but since the "host-end" statement is never encountered, the input buffer overflows and the client crashes??? At 09:36 PM 5/10/2002 -0500, John McCain wrote: >I ran a detached scan and tried to restore the session to generate a >results report. The client spends some time trying to build the report, >but then crashes without error trying to do so. I figured there may be a >client/server problem, so I copied the session files down locally and >tried to restore them with a local server, but I get the same result. > >I am using nessus 1.14 on RH 7.2.
