[Openvas-devel] No eggs found - Need help with Concurrent Checks Bug

Matthew Mundell matt at mundell.ukfsn.org
Tue Apr 14 13:20:36 CEST 2009


> Status update:
>
> My search so far was frustrating and fruitless.
>
>
> A couple of insights:
>
> - With recent versions of OpenVAS, timeout setting from client-side works.
>
> - My hypothesis, that timeout checking was faulty and nvts were incorrectly
> timed out seems to be false, as long as i can trust the logs.
>
> - The problem arises with the latest 1.0x versions, too (did not check the
> earlier ones, might be worth it), running with recent plugins. At least on
> the surface one can observe the same effects (reports differ between
> subsequent scans with number of concurrent checks 1/1+ ).
>
> - The number of concurrent checks/processes is changeable at many places in
> source, config and from client-side. However, in reality I never got it
> beyond 10.
>
>
> Technical mini wrap-up:
>
> - openvasd forks at incoming connection. The child has an array of processes
> that talk to the child through sockets (openvasd/pluginlaunch.c). Chandra
> populated nasl scripts with reporting functions (log_message etc) and found
> out that sometimes a script stops reporting in the middle of nowhere. Now,
> does the process really stop or do the message not arrive? E.g. when for some
> reason the inter-process communication in pluginlaunch breaks together, the
> script does its job but nobody notices.
>
> I hope we find (much) more, help me searching
> and
> Happy Easter
> felix
>
> On Tuesday 07 April 2009 12:32:17 Felix Wolfsteller wrote:
> > Time has come to get rid of the concurrent checks problem.
> >
> > Some bug prevents checks to result in a deterministic report if "Checks to
> > perform concurrently" is set != 1.
> >
> > The proposed solution (set "Checks to perform concurrently" != 1) is a
> > workaround at best.
> >
> > Therefore it is now time to find and eliminate this bug. I am calling for
> > help.
> >
> > The main bug report is
> > http://bugs.openvas/779
> > but I feel that http://bugs.openvas/788 and http://bugs.openvas/886 might
> > be connected to it.
> >
> > It seems that the bug appears only when local checks are employed.
> >
> > Any help (logs, openvasrcs, tons of lines of code, words of encouragement,
> > insights) would be greatly appreciated.
> >
> > felix
>
>
> --
> Felix Wolfsteller |  ++49-541-335 08 3451  |  http://www.intevation.de/
> PGP Key: 39DE0100
> Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
> Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
> _______________________________________________
> Openvas-devel mailing list
> Openvas-devel at wald.intevation.org
> http://lists.wald.intevation.org/mailman/listinfo/openvas-devel


More information about the Openvas-devel mailing list