Hi, as we didn’t touch the PDF report format for a long time this issue should have been caused by some changes in the PDF report dependencies. Could somebody maybe check if it still works with Debian oldstable? I guess it did break while updating our containers to the new Debian stable.
OK, I created this issue: Bug: corrupted PDF reports generated by gvmd 26.7.0 · Issue #2630 · greenbone/gvmd · GitHub
I set up debugging output for gvmd using the method below, but could not get any failure messages (for instance including system failed with ret). It looks like the process generating the PDFs finishes successfully, but generates garbage.
docker compose exec gvmd bash -lc "sed -i 's/^level *=.*/level = 128/' /etc/gvm/gvmd_log.conf"
docker compose restart gvmd
I really want to first get help diagnosing the failing component before creating an issue.
2 Likes
ok, from the logs i dont have any error, the command is executed but the pdf is garbage like JasaC said.
“command: /var/lib/gvm/gvmd/report_formats/0974e32b-570a-49d9-bf30-62fe437e7857/c402cc3e-b531-11e1-9163-406186ea4fc5/generate /tmp/gvmd_qo8EIn/report.xml ‘/tmp/gvmd_qo8EIn’ > /tmp/gvmd_qo8EIn/c402cc3e-b531-11e1-9163-406186ea4fc5-CuifKF.pdf 2> /dev/null”
On Debian 12 with Greenbone Vulnerability Manager 26.3.0 it’s working. 26.7.0 is not working.
This was purely a UI bug and gvmd/GMP were not affected. This is fixed with greenbone/gsa#4953 and Release gsa 26.4.1 · greenbone/gsa · GitHub
4 Likes
This topic was automatically closed after 90 days. New replies are no longer allowed.