Hello,
I have identified an issue between the IncidentInvestigation module and Zabbix Scheduled Reports.
Environment:
- Zabbix Server 7.4.10
- Zabbix Web 7.4.10
- Zabbix Web Service 7.4.10
- PostgreSQL 16 + TimescaleDB 2.15.3
- Chromium used by zabbix-web-service
- IncidentInvestigation module enabled
Problem:
When the IncidentInvestigation module is enabled, Scheduled Reports generate an almost empty PDF (grey/blank pages).
The report email is sent successfully but the generated PDF content is missing.
What I observed:
- Scheduled Reports stop working only when IncidentInvestigation is enabled.
- The issue affects even a brand-new dashboard containing only a Clock widget.
- Creating a new user does not solve the issue.
- Creating a new report does not solve the issue.
- Recreating dashboards does not solve the issue.
- Upgrading from Zabbix 7.4.3 to 7.4.10 does not solve the issue.
- Replacing zabbix-web-service versions does not solve the issue.
Troubleshooting performed:
- Created a completely new Zabbix installation with a fresh database.
- Scheduled Reports worked correctly.
- Compared database contents and configuration.
- Eventually identified the IncidentInvestigation module as the root cause.
Resolution:
After removing/disabling the IncidentInvestigation module, Scheduled Reports started working immediately and PDFs were generated correctly.
Possible cause:
The module appears to inject JavaScript globally. It may be affecting pages rendered through the Zabbix print/report mode (dashboard.print) used by zabbix-web-service and Chromium.
Thank you.
Hello,
I have identified an issue between the IncidentInvestigation module and Zabbix Scheduled Reports.
Environment:
Problem:
When the IncidentInvestigation module is enabled, Scheduled Reports generate an almost empty PDF (grey/blank pages).
The report email is sent successfully but the generated PDF content is missing.
What I observed:
Troubleshooting performed:
Resolution:
After removing/disabling the IncidentInvestigation module, Scheduled Reports started working immediately and PDFs were generated correctly.
Possible cause:
The module appears to inject JavaScript globally. It may be affecting pages rendered through the Zabbix print/report mode (
dashboard.print) used by zabbix-web-service and Chromium.Thank you.