It has been found that the TRA will crash on the following scenario:
1 - from an existing project, add a scan item on any domain.
2 - launch the scan and wait for it to complete successfully.
3 - go back to the scan items list and delete the existing item, and add a new one.
4 - launch a new scan as an update scan.
The scan will not be marked as failed, but on another hand the DBCalculation job will remain in this status :
The following typical log can be seen from the job log from the Backoffice:
DEB: GetJobJsonConfig successful
asyncio.run(main())
File \"/usr/local/lib/python3.10/asyncio/runners.py\", line 44, in run
return loop.run_until_complete(main)
File \"/usr/local/lib/python3.10/asyncio/base_events.py\", line 649, in run_until_complete
return future.result()
File \"/app/TRA.py\", line 3795, in main
if not sqlite.SetInstanceOf(szLocalTmpTestDb):
File \"/app/lib/jobs/sqlite.py\", line 4462, in SetInstanceOf
if iInstanceOf[0] == None:
TypeError: 'NoneType' object is not subscriptable
\rNumber of URLs: 1 \rNumber of URLs: 2 "
}
}
Root cause:
This is a direct consequence of defect #1789 in GitLab
Resolution:
On experiencing this, please log a new Support case and reference defect #1789 and link to this article.
Workaround:
Access the Backoffice and search for the ProjectID where the problem happens.
Scroll down on the page and go to the "Internal data" >> "Info"section near the bottom of the page.
Delete the existing "tmpDBFileName". Delete the key and the value associated to it (complete line)
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article