Hi, On 21.08.2017 16:32, Scott Knauss wrote: > Michael, > Thanks. Though I originally saw this on a machine that was > working fine until the most recent update, which is what led me to > building a fresh install. Also, the only Task currently created was > using the wizard for an immediate scan.
to avoid unnecessary work here: This is known, see the recent posts and possible solutions: https://lists.wald.intevation.org/pipermail/openvas-discuss/2017-August/011362.html https://lists.wald.intevation.org/pipermail/openvas-discuss/2017-August/011366.html (and a few more in the last few days) Regards, -- Christian Fischer | PGP Key: 0x54F3CE5B76C597AD Greenbone Networks GmbH | http://greenbone.net Neumarkt 12, 49074 Osnabrück, Germany | AG Osnabrück, HR B 202460 Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner > Scott Knauss > [email protected] <mailto:[email protected]> > * > * > *ITS* > *Immauss Technology Solutions* > *It's about solutions* > >> On Aug 21, 2017, at 6:46 AM, [email protected] >> <mailto:[email protected]> wrote: >> >> Dear Scot, >> >> not sure if i can fully help you with this, >> but you mentioned this came right after a fresh installation >> of OpenVAS. I have a suspect there, if you wouldn't mind to >> take a screenshot of the Tasks settings (task details view, >> you can open it by simply clicking on the taskname in taskview), >> i would take a closer look then and see if we can narrow down >> the problem. >> >> Thank you very much. >> >> Cheers, >> Michael Eissele. >> >> >> On 19.08.2017 13:51, Scott Knauss wrote: >>> Hello all! >>> I started getting this error after a recent update. Initially, I >>> wasn’t sure it was the update, as a few other things had changed >>> around the same time. So I built a new clean VM and reinstalled and >>> I’m still getting the same errors. >>> ==> openvasmd.log <== >>> event task:MESSAGE:2017-08-19 11h41.01 UTC:11988: Status of task >>> (1d4d7bcd-f377-4915-bd1c-2dd0a8b18eb7) has changed to New >>> event task:MESSAGE:2017-08-19 11h41.01 UTC:11988: Task Immediate scan >>> of IP 172.16.101.11 (1d4d7bcd-f377-4915-bd1c-2dd0a8b18eb7) has been >>> created by admin >>> event task:MESSAGE:2017-08-19 11h41.01 UTC:11988: Status of task >>> Immediate scan of IP 172.16.101.11 >>> (1d4d7bcd-f377-4915-bd1c-2dd0a8b18eb7) has changed to Requested >>> event task:MESSAGE:2017-08-19 11h41.01 UTC:11988: Task Immediate scan >>> of IP 172.16.101.11 (1d4d7bcd-f377-4915-bd1c-2dd0a8b18eb7) has been >>> requested to start by admin >>> event wizard:MESSAGE:2017-08-19 11h41.01 UTC:11988: Wizard >>> quick_first_scan has been run by admin >>> md manage:WARNING:2017-08-19 11h41.02 UTC:11995: sql_prepare_internal: >>> sqlite3_prepare failed: near "(": syntax error >>> md manage:WARNING:2017-08-19 11h41.02 UTC:11995: init_iterator: >>> sql_prepare failed >>> md manage:WARNING:2017-08-19 11h41.02 UTC:11995: >>> manage_cleanup_process_error: Error exit, setting running task to >>> Internal Error >>> md manage:WARNING:2017-08-19 11h41.02 UTC:11995: sql_prepare_internal: >>> sqlite3_prepare failed: near "(": syntax error >>> md manage:WARNING:2017-08-19 11h41.02 UTC:11995: init_iterator: >>> sql_prepare failed >>> This is running in an overt VM with 16G of RAM. I’ve been using this >>> setup for 2+ years, so no exception of a hardware issue. >>> Scott Knauss >>> [email protected] <mailto:[email protected]> >>> ITS >>> Immauss Technology Solutions >>> It's about solutions >>> _______________________________________________ >>> Openvas-discuss mailing list >>> [email protected] >>> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss >> > > > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
