Closed geotekberlin closed 5 years ago
I'm slightly confused - does this happen in the Icinga Web 2 monitoring module or when being in the Cube? And does the rest of Icinga Web 2 work fine? Host/service lists, choosing single hosts or services? Historically, the IDO has never been utf8, and it has not been treated as such.
Honestly I do not even know if that would really work without any issues :p All things we built from scratch are UTF8-only, but the IDO is something we inherited from looooong time ago. There will be a successor, but for now I'd strongly suggest to not work with UTF8 for that single DB resource.
@lippserd: did recently anything change in that relation? Do we support UTF8 for the IDO?
Thomas, this error shows up only in the Icinga2 Web frontend after enabling the Cube module, adding an arbitraty dimension (doesn't matter which one), clicking on the Cube link to see more details and then clicking on "Show host status". Outside of the Cube menu item Icingaweb2 does not show any SQL errors whatsoever and works as expected.
Interesting, thank you! I'll try to reproduce this
This is a dupe of https://github.com/Icinga/icingaweb2/issues/2508 which is fixed since Icinga Web 2 v2.6. Closed.
All databases have utf8 collation and are configured in icingaweb2 to use utf8 charset, but Show Host Status consistently throws errors similar to:
I have no idea where latin1_general_ci comes into play. Any ideas?