Ad Widget

Collapse

Repairing Zabbix database character set and collation doesn't fix my db

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • r0k
    Junior Member
    • May 2020
    • 6

    #1

    Repairing Zabbix database character set and collation doesn't fix my db

    Dear All,

    I know there are plenty of post about the above error on the forum but none of the solutions have helped me. I have upgraded my zabbix installation many many times and probably missed an important step somewhere in between the versions. Today I upgraded / migrated Zabbix 5.0 to Zabbix 5.4. I also had to setup a new VM based on CentOS 8 Stream as 5.4 is not availabe for CentOS 7. All went fine but then I noticed the following errors in zabbix_server.log:

    Code:
    4872:20210617:083703.873 Starting Zabbix Server. Zabbix 5.4.1 (revision ecb5b3378c).
    4872:20210617:083703.873 ****** Enabled features ******
    4872:20210617:083703.873 SNMP monitoring: YES
    4872:20210617:083703.873 IPMI monitoring: YES
    4872:20210617:083703.873 Web monitoring: YES
    4872:20210617:083703.873 VMware monitoring: YES
    4872:20210617:083703.873 SMTP authentication: YES
    4872:20210617:083703.873 ODBC: YES
    4872:20210617:083703.873 SSH support: YES
    4872:20210617:083703.873 IPv6 support: YES
    4872:20210617:083703.873 TLS support: YES
    4872:20210617:083703.873 ******************************
    4872:20210617:083703.873 using configuration file: /etc/zabbix/zabbix_server.conf
    4872:20210617:083703.877 current database version (mandatory/optional): 05040000/05040000
    4872:20210617:083703.877 required mandatory version: 05040000
    4872:20210617:083703.894 character set name or collation name that is not supported by Zabbix found in 432 column(s) of database "zabbix"
    4872:20210617:083703.894 only character set "utf8" and collation "utf8_bin" should be used in database
    First I thought I missed a step by upgrading to 5.4 but the same error is also shown on the old 5.0 server. I just never noticed since the server seems to be working fine.

    I ran the following already but this didn't seem to help:



    Even though the server seems to be working fine, I'm quite sure this needs fixing as I will stumble across this error again and again.

    Any help would be highly appreciated.

    Best Regards,
    Oliver
Working...