-
-
Notifications
You must be signed in to change notification settings - Fork 7
[Bug] PDF Reports #9
Comments
Actually if I try to show a report in any format (CSV, PDF, XML, TXT, etc) all the reports are empty. Is this related to the same bug? |
I'm not sure I use in general only PDF Format. Will check on Monday if there are other known issues about this topic. |
Yes I use PDF only as well, previously with the fix in SSC #249
This fixed the PDF reports only, the other reports were working fine. But now all the reports are empty, so I'm wondering if it was related to this upstream bug. Thanks for checking! |
Are you using the default config on the webpage? Or did you set some different filters? |
Defaults config. apply_overrides=1 levels=hml rows=100 min_qod=70 first=1 sort-reverse=severity Includes Notes and Overrides. |
Should I run the /opt/setup/script/reportFix.sh? |
Never used this script, and have no idea if this will help or for which exact problem it was ever created. |
Its a GVM Reporting fix for lines over a certain amount. It says: "This tool allows you to modify the max_rows_per_page setting. A larger number will allow you to export more data, but it will make the web UI load much slower. Any scan with more than 15000 results should be broken into multiple scans." Won't run this then. |
Have been testing since early this morning. All report formats result in 0byte downloads. Notifications that are supposed to attach reports don't have any attachments. My docker run has OPT_PDF="1" which has installed the necessary texlive deps:
Secure-Compliance-Solutions-LLC/GVM-Docker#249 does not fix the situation. Thanks. |
can you move in you container to
|
I have no such directory.
Have I done something wrong? |
No but there is a difference between the docs and the code. (#15) Please use the code from https://github.com/DeineAgenturUG/greenbone-gvm-openvas-for-docker/blob/devel/GVMDocker/scripts/sync-all.sh and add it to Need later to release the fixes to the latest images. |
Thanks @Dexus, I’m not at my desk at the moment will come back and do it. |
I copied the code from https://github.com/DeineAgenturUG/greenbone-gvm-openvas-for-docker/blob/devel/GVMDocker/scripts/sync-all.sh to my container /opt/setup/scripts/sync-all.sh. The only difference between them is:
I ran the script, it did some updates, but my In my feed status, it says all the feeds are updating. After updating, I tried to generate different reoprts (TXT, CSV, etc) they are all still 0 bytes. |
is the folder still empty? maybe I found the bug.
But this is more a upstream bug, so I'm not able to do here something else as wait... not sure if it is latex bug or one for the greenbone side. |
Yes, still empty.
I even restarted the container and let it update again. |
what does the gvmd log tells you? /var/log/gvm/gvmd.log` If there is no error to find, please try it with a complete clean system (all volume should be empty) and change after the feeds are synced and ~10 minutes idle time the database folder to your updated db and restart the container. I see this very very rarely and most when the system was stopped before the sync was done, that files are missing. |
I see a whole bunch of these messages in /var/log/gvm/gvmd.log, which corresponds to every time my tasks try to generate a report or I manually try to generate a report of any type (TXT, CSV, PDF, etc).
|
Ok will try this after dinner - thank you!
|
maybe a
|
I tried But then, I think I found the issue. The directory name for report generation directory (/var/lib/gvm/gvmd/report_formats/<report_generation_directory>) is stored in the database. When I use the old database, it somehow doesn't create the directory. I checked my previous version of gvm container and found that the <report_generation_directory> name is the same as what was showing up in the warnings in the gvmd.log in the new container (27127ef5-e2b9-4d04-a1ed-368e97fd8448). I recalled from the SC github pages, some one (was it you or pixel) mentioned that the location of the generate scripts for all the report types is stored in the pg db. So I made a copy of 27127ef5-e2b9-4d04-a1ed-368e97fd8448 and all its sub-directories and contents from my old container and put it into the new container in /var/lib/gvm/gvmd, set the permissions, the owner and group to gvm and now all reports are working properly, including PDF. Thanks for the help! |
btw. why did you not reuse the volumes from the old one? only the DB volume need to be changed after the update to match PGSql 13. |
You’re right! Stupid of me. Sorry to waste your time on this issue, it was not intentional. Completely my fault. |
No problem. |
Describe the bug
A upstream bug, that lets not create PDF if you not use the default report settings.
To Reproduce
Steps to reproduce the behavior:
...
Expected behavior
Create PDF with all kind of settings.
Screenshots
WORKING:
NOT WORKING:
Image in use:
current latest
Additional
GB Ticket: AP-1987
The text was updated successfully, but these errors were encountered: