Manual start of scheduled scans stops

Archive Greenbone Community Edition
1

Hi,

I have some scheduled scans, which work just fine. However, I needed an extra run, and started them manual from task detail screen. After start i just waited in that screen and always it changes to Status [
Stopped at 0 %] after a minute or so. The logs shows:

/opt/gvm/var/log/gvm# tail -F *

event task:MESSAGE:2021-03-27 11h36.32 UTC:24549: Status of task scheduled_scan (72bb19f7-ddd5-4e2e-9ade-b4e4371482e1) has changed to Requested
event task:MESSAGE:2021-03-27 11h36.32 UTC:24549: Task scheduled_scan (72bb19f7-ddd5-4e2e-9ade-b4e4371482e1) has been requested to start by scanadmin

==> ospd-scanner.log <==
OSPD[4138] 2021-03-27 12:36:43,364: INFO: (ospd.command.command) Scan 03936fd7-cfcb-4d81-a004-6fbb07fcaf4b added to the queue in position 1.

==> gvmd.log <==
event task:MESSAGE:2021-03-27 11h36.43 UTC:24553: Status of task scheduled_scan (72bb19f7-ddd5-4e2e-9ade-b4e4371482e1) has changed to Queued
event task:MESSAGE:2021-03-27 11h36.47 UTC:24710: Status of task scheduled_scan (72bb19f7-ddd5-4e2e-9ade-b4e4371482e1) has changed to Stop Requested

==> ospd-scanner.log <==
OSPD[4138] 2021-03-27 12:36:47,030: INFO: (ospd.ospd) Scan 03936fd7-cfcb-4d81-a004-6fbb07fcaf4b has been removed from the queue.

==> gvmd.log <==
event task:MESSAGE:2021-03-27 11h36.47 UTC:24710: Status of task scheduled_scan (72bb19f7-ddd5-4e2e-9ade-b4e4371482e1) has changed to Stopped
event task:MESSAGE:2021-03-27 11h36.47 UTC:24710: Task scheduled_scan (72bb19f7-ddd5-4e2e-9ade-b4e4371482e1) has been stopped by scanadmin
event task:MESSAGE:2021-03-27 11h36.48 UTC:24553: Status of task scheduled_scan (72bb19f7-ddd5-4e2e-9ade-b4e4371482e1) has changed to Stopped

The Stop Requested surprises me but i did not do such thing!

Any ideas/suggestions ??

Thnx,
Ton

2

tested a bit more…

  • Deleted all reports (since I have a retention of only the last 4) -> “stopped at 0%”
  • Made a clone, removed schedule from clone and started manual -> It scans
3

I had similar issues. Scheduled scans were some times stopped at various percentages, without any reason nor any action from the admin account. Sometimes scheduled scans were not starting when they should.

Upgrading gvm / ospd-openvas to 20.08.1 fixed the problems for me.

1 Like
4

Tnx. But that’s where i’m already at: Version 20.08.1~git-fc9e55140-gsa-20.08

5

Are you using Postgresql-11 or another version ? GVMD doesn’t work too well with other versions. I had scan troubles with PSQL 12 and 13. Enforcing the use of PSQL 11 fixed many problems for me as well.

6

Yeah, that’s the one running
postgresql-11 11.11-0+deb10u1 amd64 object-relational SQL database, version 11 server