Skip to main content

CloudLinux Knowledge Base

WordPress site health check: utf8mb4 requires a newer client library

Comments

4 comments

  • Dariofg

    In my case, I had to remove "character_set_client" (or "character-set-client") for these instructions to work, because MySQL did not recognize this option. But the other lines did it for me!

    1
  • Vitaly Nemykin

    You are right. This option may not work on some MySQL versions.

    Could you please provide your MySQL version:
    # mysql -V

    0
  • Dariofg

    My MySQL version is 8.0.30 for Linux on x86_64.

    0
  • Nicolas
    • Starting from MariaDB 10.6 the utf8 character set (and related collations) is now by default alias for utf8mb3

    Since this update change the behaviors of saving "emojis" in the database, please, if you found a solution or if you have want to join the discussion, there is a thread opened at StackOverflow:

    https://stackoverflow.com/questions/75809245/cannot-save-emojis-in-utf8mb3-tables-overnight-since-mariadb-10-6-update-and-s

    _

    I also got some errors and this article should maybe being updated accodingly :

    [Note] Using unique option prefix 'character_set_client' is error-prone and can break in the future. Please use the full name 'character-set-client-handshake' instead.

    But don't try this: 

    [Warning] /usr/sbin/mariadbd: ignoring option '--character-set-client-handshake' due to invalid value 'utf8mb4' 

    Which means…

    Don't ignore client side character set value sent during handshake. (Defaults to on; use --skip-character-set-client-handshake to disable.)

    So I cannot wonder if we should switch to "false" and/or using --skip-character-set-client-handshake 

    If someone walking through here have an idea? 

    0

Please sign in to leave a comment.