Scared me there for a sec! The "tasks.db" file in mine that actually has
data in it is under /var/lib/openvas/mgr. There was an empty one in
/var/lib/openvas, thought it had wiped out my db :)
I never even got a chance to tie a task to the schedule entry before it
bombed. Any idea what would be in the "schedule" column for one that is
set to start at 6:00:00 UTC on the 23rd and repeat every 4 weeks? I
can't make any sense out of the single digit numbers that are there for
the other tasks.
On 6/18/2012 3:01 PM, Matthew Mundell wrote:
I added a schedule that was supposed to repeat every 4 weeks using GSA.
After doing so the manager process bombed and I have been unable to
start it again. Attempting to start it up after adding the schedule yields:
I tried to reproduce but it works OK. Maybe the assertion is wrong.
This is latest openvas available on CentOS 6.2. Any ideas how I can get
my management process back?
You could remove the schedule from the task in the db. Find the UUID of the
task
sqlite3 var/lib/openvas/tasks.db "select name, uuid from tasks;"
then replace the UUID with it in this command to clear the schedule.
sqlite3 var/lib/openvas/tasks.db "update tasks set schedule = 0 where uuid =
'UUID';"
--
Greenbone Networks GmbH
Neuer Graben 17, 49074 Osnabrueck, Germany | AG Osnabrueck, HR B 202460
Executive Directors: Lukas Grunwald, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
