Closed Akrugerus closed 3 years ago
This is a bug in ospd - it creates a scan with no 'end_time' (https://github.com/greenbone/ospd/blob/532169f28f65051eb0afa64dd4bf8eef6057c09f/ospd/scan.py#L282), and then assumes 'end_time' is always available (https://github.com/greenbone/ospd/blob/532169f28f65051eb0afa64dd4bf8eef6057c09f/ospd/scan.py#L421). I'm not sure if there's a good workaround for this.
Hello @Akrugerus
Thanks for reporting the bug. I was able to reproduce it, setting the config option scaninfo_store_time
, so I assume this is your case.
PR greenbone/ospd#354 fix this issue
I'm attempting to set up a distributed scan environment with gvmd and gsa running on a central system and ospd-openvas instances spread around to execute the tasks and send them back to the central system. I found a super convenient docker implementation of this environment that handles the setup and connection of these instance here https://github.com/Secure-Compliance-Solutions-LLC/GVM-Docker. I'm able to get both an instance of the gvm controller and an instance of the ospd-openvas scanner running and connected. My problem comes when I try to initiate my first remote scan. When I queue the scan to start, it is sent to the remote scanner and immediately prints out the stack error pasted below in openvas.log.
I'm unsure if the docker environment I'm using could be causing this, but it seems to just be an error when starting a remotely initiated scan. Any help would be appreciated.