or Create a profile
09 May, 2017 12:21 PM
I ran a scan from the web api which failed due to a disk space issue. It had found a number of issues and displayed them but a report could not be generated.
I fixed the space error and rescaned that application. I stopped the scan after a short time and it had found two issues. I exported a report from this scan but it had access to more issues than those listed on the web front end.
I am the curious about the relationship between issues and reports. In the PostgreSQL db I see a reports table with a report object and a issues table with issues. Is the report object only generated at the end of a scan? What is the relationship between issues and reports?
Is there anyway to recover the corrupted scan perhaps pointing issues to a new scan??
on 12 May, 2017 12:36 PM
The report object is basically the contents of the AFR file, like you'd get at the end of a CLI scan. That object is later used to generate reports in different formats.
If the scan crashes though, for whatever reason, the WebUI won't get a chance to retrieve the AFR report, since that happens at the end of the scan.
Also, unfortunately, there's no way to recover a corrupted scan.
Formatting help /
(switch to plain text)
(switch to Markdown)
You can attach files up to 10MB
If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.
A conversation has been started with the Arachni staff to resolve this discussion.
This discussion is private.
Only you and Arachni support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
You can use Command ⌘ instead of Control ^ on Mac
Powered by Tender™.