New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #10554] Non-UTF8 characters from plugins causes IDO to fail #3613
Comments
Updated by gbeutner on 2015-11-18 08:49:35 +00:00
|
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 gbeutner on 2015-11-18 19:19:06 +00:00
|
Updated by mfrosch on 2015-11-23 09:04:30 +00:00
|
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. |
Updated by mfriedrich on 2015-11-23 16:15:19 +00:00
|
Updated by mfriedrich on 2015-11-24 13:04:52 +00:00 Quick workaround: Fix the plugin output and strip non-utf8 characters before passing the output back to Icinga 2. |
Updated by mfriedrich on 2015-12-10 11:27:02 +00:00
|
Updated by Anonymous on 2015-12-10 11:30:04 +00:00
Applied in changeset fba0b49. |
Updated by gbeutner on 2016-02-23 09:58:17 +00:00
|
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
Assignee: gbeutner
Status: Resolved (closed on 2015-12-10 11:30:04 +00:00)
Target Version: 2.4.2
Last Update: 2016-02-23 09:58:17 +00:00 (in Redmine)
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?
An example:
Attachments
Changesets
2015-12-10 11:26:19 +00:00 by (unknown) fba0b49
2016-02-23 08:08:32 +00:00 by (unknown) 2e93082
The text was updated successfully, but these errors were encountered: