Task is interrupted, but why?

Archive Greenbone Community Edition
1

GVM versions

Greenbone Security Assistant 20.08.1
Greenbone Vulnerability Manager 20.08.1
Manager DB revision 233
OpenVAS 20.8.1
gvm-libs 20.8.1

Environment

Linux monitor-ext 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

This is quite a basic question: I have one task which never (!) completes. The log reads:

event task:MESSAGE:2021-03-29 16h07.21 CEST:794534: Status of task DMZ-Metro 1-2 (366960d2-1b22-4e0b-ae16-b4011613f098) has changed to Requested
event task:MESSAGE:2021-03-29 16h07.21 CEST:794534: Task DMZ-Metro 1-2 (366960d2-1b22-4e0b-ae16-b4011613f098) has been requested to start by admin
event task:MESSAGE:2021-03-29 16h07.28 CEST:794537: Status of task DMZ-Metro 1-2 (366960d2-1b22-4e0b-ae16-b4011613f098) has changed to Queued
event task:MESSAGE:2021-03-29 16h07.43 CEST:794537: Status of task DMZ-Metro 1-2 (366960d2-1b22-4e0b-ae16-b4011613f098) has changed to Running
event task:MESSAGE:2021-03-29 17h03.25 CEST:794537: Status of task DMZ-Metro 1-2 (366960d2-1b22-4e0b-ae16-b4011613f098) has changed to Interrupted

So it was running, and it was interrupted (not by me).
But why? How can I change logging to see what failed and why?

2

Hi @hildeb,
there is an open issue in Github about interrupted scans. Maybe you can give it a look. Any information you can add to the issue will help me to solve this problem, as I am still not able to reproduce it.
Other issues related to interrupted scans were already solved. The last fix is from some days ago and therefore still not included in any release.

Some of the issues were related to unresolved hostnames in the target, duplicated hosts in the target, host in the excluded_hosts list which do not belong to the host list. These issues produced a wrong scan progress calculation. Check your host and exclude host lists and let me know if it helps.

Regards

1 Like