Hello, we are finding reports are timing out once the number of results for a scan grows large. 8000 results seems to be too much. The various tabs of the report field stay at 0 and we get the following message:
Error while loading Report f6cba155-b3e4-4161-9070-5aa820779c58
Please try again.
Hide Error Details
Rejection: Unknown Error
Error
at new $b (https://greenbone.ourdomain.com/static/js/main.cae1bbe1.js:2:1885360)
at https://greenbone.ourdomain.com/static/js/main.cae1bbe1.js:2:1888286
It seems to be about a minute before the timeout. Looking at top we can see postgres working hard,
Apart from splitting the scans into multiple IP blocks, is there anything we can adjust to have the front end wait longer for the database? (I’m guessing that is the issue here)
The host machiine is a VM with the containers on a SAN. We have allocated plenty of RAM, CPU and although postgres uses 100% on some cores there are still free resources on the machine.
Greenbone about shows version 22.9.1