Check if the scan was stopped before launching OpenVAS. #332
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
Check if the scan was stopped before launching OpenVAS.
Why:
If the scan was stopped during the preferences handling before spawining the OpenVAS process,
the process was spawned but still marked as stopped.
Now the scan is indeed stopped and the new process is not being spawned.
How:
The issue is that ospd-openvas set the task as running, while it is still preparing the scan preferences to be sent to the scanner. In other words, Openvas has not been started when ospd-openvas received the stop command.
With a small scan config, this problem is probably harder to reproduce, since ospd-openvas prepares the preferences and starts Openvas faster
If you see in the logs, you can see that Openvas is started after the stop cmd is received. If you wait until Openvas is indeed started, the scan is stopped as expected.
To reproduce the issue and check the fix:
Checklist: