On Wed, Jun 05, 2002 at 02:25:33PM -0700, Mike Batchelor wrote:
> Scans give no results. None. Zip. Nada. There is plenty of network
> activity, and /var/log/nessus/nessusd.messages fills rapidly claiming
> boatloads of activity is going on.. I first tried to save to NSR, that
> gave me a zero byte file. I tried to save to NBE, that gave me a file with
> only "timestamps" lines and no "results" lines (I gathered from another
> thread that there are these two kinds of lines supposed to be in there). I
> have tried this from the GUI and also from command line using batch mode.
> I have all the KB stuff turned off, though I was saving sessions. I am
> going to try it with session saving off before I give up (does batch mode
> look at sessions at all?).
Did you try to delete completely your .nessusrc and restart ? The format
has changed between 1.0.x and 1.2.x. Also, make sure you de-installed
the old 1.0.8 RPMs.
> Another problem has to to with Gdk. I lost results from a session when the
> GUI crashed at the end:
>
> Gdk-WARNING **: GdkWindow 0x31884da unexpectedly destroyed
>
> Gdk-ERROR **: called gdk_window_destroy on a pixmap (use gdk_pixmap_unref)
> aborting...
> Aborted (core dumped)
>
> The Nessus window was in the background at the time, a Gnome term was in
> front and I was typing into it.
do :
gdb /usr/local/bin/nessus core
gdb> backtrace
and send me the backtrace.
A last thing - Nessus 1.2.x writes data to a temporary file (located
under $TMP/nessus-xxxxx, (or /tmp/nessus-xxxx if your $TMP variable is
not set). You can easily reload it in the GUI by renaming xxxx.nbe.
-- Renaud
