I have had similar problems when updating through CVS. My build process is:
for each directory in nessus-libraries, libnasl, nessus-core, nessus-plugins:
make distclean; ./configure; make; make install
follow all instructions printed during make/.configure above
Even after this, I have had problems with nessus exiting prematurely with
empty reports. The only thing that I have found works reliably is to delete
anything nessus, such as /usr/local/etc/nessus, /usr/local/var/nessus, etc.
before running the configure/makes as above. This is obviously a
"sledgehammer" approach, and destroys all accounts, certificates etc., but
seems to work every time. I have not had time to research exactly what
remnant is causing the behavior. Does anyone have any suggestions? Is there
a published build procedure for new CVS updates?
Hope this helps someone to track down the real problem.
Best regards,
Dave.
On Sunday 30 December 2001 02:39 pm, Renaud Deraison wrote:
> On Thu, Dec 27, 2001 at 12:57:43PM -0500, W. Mark Herrick, Jr. wrote:
> > v1.1.12, compiled today from CVS tree
> >
> > Scanned 2 hosts, no reports come up, even though vulnerabilities were
> > found.
> >
> > Same bug, new version?
>
> Should not happen, but still possible. Please send me (privately) as
> many details regarding the scan as possible (ie: did you run another
> scan before, was it in command line or gui, and so on), and I'll look
> into it when I come back from vacations.
>
>
> -- Renaud
