Skip to content
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

module graphite 0.9.0 on jjethwa/icinga2 have problem #121

Closed
cyrus0880 opened this issue Dec 12, 2017 · 3 comments · May be fixed by #141
Closed

module graphite 0.9.0 on jjethwa/icinga2 have problem #121

cyrus0880 opened this issue Dec 12, 2017 · 3 comments · May be fixed by #141

Comments

@cyrus0880
Copy link

how to fix this problem
on icingaweb > graphite > hosts
SQLSTATE[42000]: Syntax error or access violation: 1253 COLLATION 'latin1_general_ci' is not valid for CHARACTER SET 'utf8', query was: SELECT ho.name1 AS host_name, h.display_name COLLATE latin1_general_ci AS host_display_name, hs.check_command AS host_check_command, hcv_check_command.varvalue AS _host_check_command FROM icinga_objects AS ho
INNER JOIN icinga_hosts AS h ON h.host_object_id = ho.object_id AND ho.is_active = 1 AND ho.objecttype_id = 1
INNER JOIN icinga_hoststatus AS hs ON hs.host_object_id = ho.object_id
LEFT JOIN icinga_customvariablestatus AS hcv_check_command ON h.host_object_id = hcv_check_command.object_id AND hcv_check_command.varname = 'check_command' COLLATE latin1_general_ci ORDER BY h.display_name COLLATE latin1_general_ci ASC LIMIT 25

on icingaweb > graphite > hosts services
SQLSTATE[42000]: Syntax error or access violation: 1253 COLLATION 'latin1_general_ci' is not valid for CHARACTER SET 'utf8', query was: SELECT so.name1 AS host_name, h.display_name COLLATE latin1_general_ci AS host_display_name, so.name2 AS service_description, s.display_name COLLATE latin1_general_ci AS service_display_name, ss.check_command AS service_check_command, scv_check_command.varvalue AS _service_check_command FROM icinga_objects AS so
INNER JOIN icinga_services AS s ON s.service_object_id = so.object_id AND so.is_active = 1 AND so.objecttype_id = 2
INNER JOIN icinga_hosts AS h ON h.host_object_id = s.host_object_id
INNER JOIN icinga_hoststatus AS hs ON hs.host_object_id = s.host_object_id
INNER JOIN icinga_servicestatus AS ss ON ss.service_object_id = so.object_id
LEFT JOIN icinga_customvariablestatus AS scv_check_command ON s.service_object_id = scv_check_command.object_id AND scv_check_command.varname = 'check_command' COLLATE latin1_general_ci ORDER BY s.display_name COLLATE latin1_general_ci ASC LIMIT 25

@cyrus0880 cyrus0880 changed the title module graphite 0.9.0 on your docker have problem module graphite 0.9.0 on your jjethwa/icinga2 have problem Dec 12, 2017
@cyrus0880 cyrus0880 changed the title module graphite 0.9.0 on your jjethwa/icinga2 have problem module graphite 0.9.0 on jjethwa/icinga2 have problem Dec 12, 2017
@jjethwa
Copy link
Owner

jjethwa commented Dec 12, 2017

Hi @cyrus0880

Please refer to: Icinga/icingaweb2#3170

We'll need to wait for it to be fixed 😞

@bebehei
Copy link
Contributor

bebehei commented Jan 18, 2018

@jjethwa The issue you referenced is already fixed. What should be done here now?

@jjethwa
Copy link
Owner

jjethwa commented Jan 18, 2018

Hmm, I don't see a new PR from the user that created the issue. So he might still be working in it. In any case, I think we can go ahead and close this issue as it's not a container specific problem 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants