PDF-reports are empty #249
Comments
|
First question: you read the docs correctly? Volumes changed! Second question: was the database final initialized? Takes up to 1 hour on fresh setups. (Same as on new installations from source) |
Sorry I don't understand your remark here, but I changed my command now to:
I think so yes, is there some way to double check? The container was running for more than 1 hour when I tested. |
Let me check this one more time, on my tests it worked without problems. Has the report only some or many findings? Can you attach the pdf output? This would help if you think it's confidential then send it via email to me. Thank you.
I know that if the DB is not final initialized your reports can be incomplete and broken. Also the Tests not fully done. But mostly the DB is finished when you have no SCAP error in the NVT page in the UI and you have all the configs available, in other words the scanconfigs are there in the UI. |
|
I have the same problem, I'm using the image securecompliance/gvm:master-data-full |
All I get is an empty file. I can e-mail that you if you think it could be useful?
Looks like it finished then because I got all the 75288 NVT's there. |
|
It looks like the problem is that the generation of the PDF will fail, |
|
What I found so far: is looks like it is GVMD related. I have created a bug greenbone/gvmd#1658 |
|
I'm having the same problem and while I haven't found a solution, this is my report.log Hopefully this means something to people smarter than me. :) |
|
@kaptenkrille @tmuncks @rudnypc You can run in the container: #!/bin/sh
echo " --> updmap-sys --syncwithtrees"
yes 2> /dev/null | updmap-sys --syncwithtrees > /dev/null 2>&1 > /dev/null
echo " --> updmap-sys"
updmap-sys > /dev/null 2>&1 > /dev/null
echo " --> mktexlsr"
mktexlsr > /dev/null 2>&1 > /dev/null
echo " --> texhash"
texhash > /dev/null 2>&1 > /dev/null
echo " --> fmtutil-sys --all"
fmtutil-sys --all > /dev/null 2>&1 > /dev/null
echo " --> updmap-sys --force"
updmap-sys --force > /dev/null 2>&1 > /dev/null
exit 0This will fix the missing font maps. And PDF should work again. |
|
Just confirming that this solved the PDF problems here. Thanks a lot! :) |
|
You are welcome. With the upcomming release v21.4.3-v1 it will fixed with upstream package. Also it will be fixed if you run in container: |
|
Yes, I can confirm to that this solved the issue. Thank you very much! |
|
These workarounds were not helpful in my case. My container got broken after applying them. #249 (comment) did not fix anything for me. #249 (comment) broke the GVM, no scan was possible afterwards. I had to delete and create the GVM container from scratch again. |
Sorry but that can only be bull. |
|
The container was running several days before applying the workaround. |
|
It's working here now after installing the addon package:
In my case the workarounds mentioned above didn't work too. |
|
Doesn't make sense... It's already listed here. |
Yes, I agree. |
I merge that fix with all entrypoint code after that I mapped the entrypoint file to /entrypoint.sh . |
Hey Dexus, I faced the same issue after doing that fix above. My container is broken. |
|
I don't even see pdflatex in a fresh container build. I installed texlive-latex-base manually so now the command exists. The generate script is still failing, though, and I can't quite see why after the fact. md manage:WARNING:2021-12-16 19h09.57 UTC:216336: run_report_format_script: system failed with ret 256, 1, /var/lib/gvm/gvmd/report_formats/c012a19f-689f-464e-8679-079abe0b43e2/c402cc3e-b531-11e1-9163-406186ea4fc5/generate /tmp/gvmd_xwb72T/report.xml '/tmp/gvmd_xwb72T' > /tmp/gvmd_xwb72T/c402cc3e-b531-11e1-9163-406186ea4fc5-HQN1rN.pdf 2> /dev/null |
|
You can now use the https://hub.docker.com/r/deineagenturug/gvm images, which are using the latest gvmd and components releases. It use POSTGRESQL 13. What are meaning the tags: It can be used as direct replacement for the here provided image, with the same arguments on PDF support is always broken if the release is build on Github runners, because of limited memory. The releases of |
|
We have found another bug that related to the PDF Reports that we track on DeineAgenturUG/greenbone-gvm-openvas-for-docker#9 |
Describe the bug
I started a container with OPT_PDF="1" but pdf-reports are empty on exports, XML/TXT works. Command I used to deploy the container:
docker run --detach --publish 8080:9392 --env OPT_PDF="1" --volume gvm-data:/data --name gvm securecompliance/gvm
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A "normal" pdf-report.
Host Device:
docker image inspect![]()
Additional context
I'm probably doing something wrong but guides are pretty straight forward so I can't figure out where it goes wrong.
The text was updated successfully, but these errors were encountered: