Reports are missing after update to 20.8.0

After update to last version, all old reports are missing.
After migration of the database schema and the call of:
gvmd --modify-setting 78eceaec-3385-11ea-b237-28d24461215b --value
no reports are show in the ui.
Under the feed status all 4 are up to date.
On the report page I only the this error:


And in the log file of gvm this is shown:

md manage:WARNING:2020-09-02 11h39.29 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate
md manage:WARNING:2020-09-02 11h39.29 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate
md manage:WARNING:2020-09-02 11h39.29 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate
md manage:WARNING:2020-09-02 11h39.30 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate
md manage:WARNING:2020-09-02 11h39.30 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate
md manage:WARNING:2020-09-02 11h39.30 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate
md manage:WARNING:2020-09-02 11h39.31 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate
md manage:WARNING:2020-09-02 11h39.31 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate
md manage:WARNING:2020-09-02 11h39.31 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate
md manage:WARNING:2020-09-02 11h39.31 CEST:24610: run_report_format_script: No generate script found at /var/lib/greenbone/gvmd/report_formats/generate

Have any one an idea what goes wrong?

This issue has already been reported. See

For more background. It will be fixed with

After set it in debug mode I found the problem and solution.

  1. extract the /usr/share/gvm/gvmd/report_formats folder from the old 9’er package
  2. chmod -R report_formats
  3. call sudo -u gvmd gvmd --modify-setting 78eceaec-3385-11ea-b237-28d24461215b --value … gain.
    Now the old data are migrated and the old reports xml files are deleted.
    The hint in the debug mode was:
    md manage:WARNING:2020-09-02 09h58.01 utc:42910: move_report_format_dir: report dir missing: /usr/share/gvm/gvmd/report_formats/910200ca-dc05-11e1-954f-406186ea4fc5
    Now the old reports are visible again:
1 Like

Note that keeping the old report_formats dir from < 20.08 versions is a prerequisite is documented in the release notes below.

The linked PR of @bricks improves the situation for migrations where the user running gvmd doesn’t have any permission to access / remove the old files in that folder.

I am seeing this same error problem with a newly built release (make clean && make && make doc && make install) even though I had previously fixed this issue. Seems to crop up after any update, and now I cannot fix it at all.
Log entries are similar to above
md manage:WARNING:2020-09-17 16h50.34 AEST:45399: run_report_format_script: No generate script found at /opt/gvm/var/lib/gvm/gvmd/report_formats/generate

Cannot determine why this is occurring. Please provide a suggestion. There is no generate in that directory, but there are for every report format underneath it. Why is it still looking for this?
It does not exist on a VM I have on my desktop, same OS, all running fine after a rebuild.

What can I do to fix it?

BTW, after the machine was rebooted (increase processor and RAM), it gvmd refused to start, saying the database was the wrong version. I have no idea how that was the case. Anyway, gvmd -m fixed it and it was able to start.
Is this what caused the reports to look for the old generate script path? If so, how can I fix it?

Hi All,
Well, I have no idea what happened to the DB.
I have managed to repair the damage and get things functioning again.
It seems the Feed Owner setting went missing. I had to reconstruct it wit the correct UUID for the feed owner user to get it working again.
Cheers

1 Like