Scheduled Reports

[trimoon]

Have you checked the logs? Web service logs and Zabbix Server logs.

I hadn't deleted and re-created the scheduled report in a while. Just did that and the error about not being able to connect to server is gone now.

Thank you for your help, i think one of the above steps fixed the underlying issue and the old report was stuck broken until re-created.

[vijayk]

I hadn't deleted and re-created the scheduled report in a while. Just did that and the error about not being able to connect to server is gone now.

Thank you for your help, i think one of the above steps fixed the underlying issue and the old report was stuck broken until re-created.

Nice to here..Enjoy the Weekend...

[trimoon]

Nice to here..Enjoy the Weekend...

I spoke too soon. The error is gone from the scheduled reports screen, but when i try and generate a test from within the new report, a similar error appears:


Different error which is encouraging but still seems to be broken in a related way.

[trimoon]

Have you checked the logs? Web service logs and Zabbix Server logs.

tail zabbix_web_service.log only shows starting / stopping web service. Nothing strange in there.

tail zabbix_server.log shows some variable name errors for some MIB's. Housekeeper deleting things... Doesnt look related.

[vijayk]

Refer the URL.

https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/429591-scheduled-reports-cannot-connect-to-web-service-couldn-t-connect-to-server/page2

SELinux is also causing the issue. Please verify it.

grubby --update-kernel ALL --args selinux=0
reboot

[trimoon]

Refer the URL.

https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/429591-scheduled-reports-cannot-connect-to-web-service-couldn-t-connect-to-server/page2

SELinux is also causing the issue. Please verify it.

grubby --update-kernel ALL --args selinux=0
reboot

That did it. Scheduled reports coming through.

I had ran:
sudo setenforce 0

But not:
grubby --update-kernel ALL --args selinux=0

Thank you VERY much for your help on this!

[vijayk]

That did it. Scheduled reports coming through.

I had ran:
sudo setenforce 0

But not:
grubby --update-kernel ALL --args selinux=0

Thank you VERY much for your help on this!

Yes, it will also disable the SELinux.