You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fresh install of reporting module (v1.0.1) with icingadb v1.1.1 (with postgres database if it matters), everytime I access a report, I get the following error and so, report is not showing :
SQLSTATE[42725]: Ambiguous function: 7 ERROR: function get_sla_ok_percent(bytea20, unknown, unknown, unknown) is not unique
LINE 1: SELECT (get_sla_ok_percent(host.id, NULL, '1640991600000', '...
^
HINT: Could not choose a best candidate function. You might need to add explicit type casts. (Connection.php:402)
To Reproduce
Steps to reproduce the behavior:
Install and configure icingadb with postgresql
Install reporting module
Create a report
Expected behavior
Report should show up and not throw an error
Your Environment
Module version:
Dependent module versions: icingadb v1.1.1
Icinga Web 2 version and modules (System - About): 2.12.1
Web browser and version: Firefox 120.0.1
Icinga 2 version used (icinga2 --version): r2.14.0.-1
PHP version used (php --version): 8.2.7
Server operating system and version: Debian 12.4
The text was updated successfully, but these errors were encountered:
Describe the bug
Fresh install of reporting module (v1.0.1) with icingadb v1.1.1 (with postgres database if it matters), everytime I access a report, I get the following error and so, report is not showing :
SQLSTATE[42725]: Ambiguous function: 7 ERROR: function get_sla_ok_percent(bytea20, unknown, unknown, unknown) is not unique
LINE 1: SELECT (get_sla_ok_percent(host.id, NULL, '1640991600000', '...
^
HINT: Could not choose a best candidate function. You might need to add explicit type casts. (Connection.php:402)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Report should show up and not throw an error
Your Environment
icinga2 --version
): r2.14.0.-1php --version
): 8.2.7The text was updated successfully, but these errors were encountered: