Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #10554] Non-UTF8 characters from plugins causes IDO to fail #3613
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10554
Created by dgoetz on 2015-11-06 12:35:23 +00:00
A plugin giving output with non-UTF8 characters causes IDO to fail. Because we can not make sure every plugin handles this correctly. Can we get Icinga 2 to ignore such plugin output?
2015-12-10 11:26:19 +00:00 by (unknown) fba0b49
2016-02-23 08:08:32 +00:00 by (unknown) 2e93082
Updated by gbeutner on 2015-11-18 08:59:36 +00:00
The underlying problem is that there's no way to determine which encoding things like plugin output and config object names are in.
One idea would be to set the client encoding to latin1:
Updated by mfrosch on 2015-11-23 15:56:49 +00:00
Best way seems to be setting connection encoding to 'latin1', since the IDO is modelled for latin.
Though it needs testing if we eradicate these problems with that change.
Icinga 1 would have similar problems with incorrect chars, but will write it to database, due to latin1.