[Openvas-discuss] Task failed to start but omp still show it as requested to start.
Jan-Oliver.Wagner at greenbone.net
Wed Jun 6 07:22:14 CEST 2012
On Friday 01 June 2012 11:11:33 Sebastien Aucouturier wrote:
> openvasmd.log show this :
> event task:MESSAGE:2012-05-30 15h38.26 UTC:29569: Status of task
> ikare_10.1.0.254 (a86a3752-ee59-4eaa-afc1-0b63394efa9b) has changed to
> event task:MESSAGE:2012-05-30 15h38.26 UTC:29569: Task
> a86a3752-ee59-4eaa-afc1-0b63394efa9b has been requested to start
> event task:MESSAGE:2012-05-30 15h43.06 UTC:29607: Task
> a86a3752-ee59-4eaa-afc1-0b63394efa9b has failed to start
> but an omp query still show task 'a86a3752-ee59-4eaa-afc1-0b63394efa9b'
> as requested.
> is there a workaround for that ? to help detecting task 'resquested to
> start' failed to start.
I did not experience such behaviour for a long time myself.
Which version of OpenVAS are you using?
Do you have a reliable way to reproduce this?
However, if you restart openvasmd, it does a self-check and
such tasks are set to "Stopped".
Dr. Jan-Oliver Wagner | ++49-541-335084-0 | http://www.greenbone.net/
Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B
Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner
More information about the Openvas-discuss