[ZBXNEXT-5603] Check DB character set and collation on initial frontend setup page Created: 2019 Nov 28  Updated: 2024 Apr 10  Resolved: 2020 Feb 16

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 4.0.15, 4.4.3
Fix Version/s: 4.0.18rc1, 4.4.6rc1, 5.0.0alpha2, 5.0 (plan)

Type: New Feature Request Priority: Minor
Reporter: Edgars Melveris Assignee: Roberts Lataria (Inactive)
Resolution: Fixed Votes: 7
Labels: collate, schema, utf8
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Causes
causes ZBX-17508 Oracle: "Invalid argument" error when... Closed
causes ZBX-17924 dashboard php errors in "System infor... Closed
Sub-task
depends on ZBXNEXT-5626 Server side: Check DB character set a... Closed
Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
ZBXNEXT-5799 Provide instructions how to fix incor... Documentation (Sub-task) Closed Martins Valkovskis  
Team: Team D
Sprint: Sprint 58 (Nov 2019), Sprint 59 (Dec 2019), Sprint 60 (Jan 2020), Sprint 61 (Feb 2020)
Story Points: 1

 Description   

A lot of Zabbix users incorrectly create the DB with default character set and collation settings. This usually works at first but causes problems later.
It would help, if the frontend setup page would check this and not allow to continue unless this is fixed.

 Comments   
Comment by Oleksii Zagorskyi [ 2019 Nov 28 ]

Also, server could check it too and print a warning on startup.
Frontend could indicate such warning (for existing installations) too.

Comment by Aleksejs Petrovs [ 2019 Nov 28 ]

I think that kind of check must be made by Server daemon and alert when collation/charset is wrong.

Comment by richlv [ 2019 Nov 29 ]

Note that this can be set per table.

Comment by Alexander Vladishev [ 2019 Nov 29 ]

... and can be set per text field.

Comment by Aleksejs Petrovs [ 2019 Nov 29 ]

Yes indeed, it can be per text field or per table, but this isn't a normal use case for Zabbix, if you made so then, most of the time you are aware of consequences.

The idea of this validation is to prevent fresh installs from collation/charset mistakes and installations with the wrong default charset.

It would be good to have default DB collation/charset verified by:

  • Daemon while starting and output this error in the log file. Optional: Notify ZAdmins using User group for database down message value configured under Administration -> General -> Other
  • Frontend during the installation wizard.

We have a statement in the documentation that specific options must be obeyed during the deployment so Zabbix could work properly.

Regards,
Aleksejs!

Comment by Roberts Lataria (Inactive) [ 2019 Dec 10 ]

Resolved in development branch feature/ZBXNEXT-5603-4.0.

Comment by richlv [ 2019 Dec 10 ]

Aleksej, there have been quite a lot of cases where people have created the DB wrong, later converted a few tables only as a quick approach.
Not the most common problem, but daemon checking for this could be very helpful indeed.

Comment by Alexander Vladishev [ 2019 Dec 11 ]

<richlv>, this check on server/proxy side will be implemented in ZBXNEXT-5626.

Comment by richlv [ 2019 Dec 12 ]

Sounds great, thank you for the link.

Comment by Roberts Lataria (Inactive) [ 2020 Feb 04 ]

Available in:

Comment by sles [ 2020 Feb 22 ]

This should not only check , but fix this, because it is expected that zabbix manages database changes during upgrade.

Generated at Sun Mar 30 09:48:27 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.