I reinstalled the latest stable release of OpenVAS-7 (including libs), but the behavior persists.
"sql_giveup: cannot initiate a transaction within an existing transaction" found in openvasmd.log I did some research on sqlite3 and I found that the error might be associated with the fact that sqlite3 does not support nested transactions. Does openvasmd run nested transaction against sqlite3 when you run a clustered scan? Thanks. Michelangelo On 6/2/14, 2:50 AM, Jan-Oliver Wagner wrote: > Hi, > > I have not observed this type of error myself. > > However, using beta13 of OpenVAS Manager is really suboptimal. > It does not match with the other releases to form a OpenVAS-7. > > I recommend to upgrade to stable release and then re-check for the behaviour. > While you are at it, newer libs and scanner are also making sense. > > Best > > Jan > > On Freitag, 30. Mai 2014, NopSec wrote: >> I deployed an openvas cluster composed by one master and 6 slaves. >> >> We deployed the following packages: >> >> openvas-libraries-7.0.0 >> >> openvas-manager-5.0+beta13 >> >> openvas-scanner-4.0.0 >> >> We scanned a class C and after about an hour the slaves are done but the >> master indicate that the scan is still running. >> >> Upon further investigation, the openvasmd log in the master included the >> following error: >> >> "sql_giveup: cannot initiate a transaction within an existing transaction" >> >> It sounds like the slaves are trying to the master sqlite3 database >> while the database is locked. The net result is that the slaves are done >> their job but the results are not into the master and also the master >> does not know that the slaves are done. >> >> Trying to troubleshoot further this condition. >> >> Do you know if the updated latest stable openvas packages resolve this >> condition? > _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
