[20.8.1] gvmd vaccum fails

[pomac303]

MIght be related to:
greenbone/gsa#2768

md main:MESSAGE:2021-03-02 09h55.00 utc:43810: Greenbone Vulnerability Manager version 20.08.1 (DB revision 233)
md manage: INFO:2021-03-02 09h55.00 utc:43810: Optimizing: vacuum.
md manage:WARNING:2021-03-02 09h55.01 utc:43810: manage_optimize: failed to stat database: Bad address
md manage:WARNING:2021-03-02 09h55.01 utc:43810: manage_optimize: failed to stat database: Bad address
Optimized: vacuum.
md manage:MESSAGE:2021-03-02 09h55.01 utc:43810: Optimized: vacuum.

[cfi-gb]

Have you verified that you are running the command with the correct user (the one running gvmd / having the access permissions to the PostgreSQL database)?

[pomac303]

Yes, the same command ran for 41 minutes - it does clear data but something goes wrong - somehow the database has ended up in a 'inconsistent state', but there doesn't seem to be anything i can do to fix it - not even trying to clear out old reports.

[timopollmeier]

The "failed to stat database" warnings should only affect the file size comparison, not the vacuum command itself.

As for the inconsistent state: Can you describe what is wrong and check the gvmd log for other warnings?
If you are getting the same error as in greenbone/gsa#2768, have you checked if the report formats are accessible? Since GVM 20.08 the report formats are no longer pre-installed but supplied via a gvmd-data feed.
I think it's unlikely that this is related to the vacuum command but if there is some database corruption, there should be more warnings about failed SQL commands.

[pomac303]

Yeah I tought it was a inconsistent state since i couldn't see the reports - turns out that it seems to be a error in the webui fixed in 20.8.6 - haven't tested to confirm yet though

[cfi-gb]

Closing as #1447 has been merged just a few minutes ago. Thanks for your report 👍