Announcement

Announcement Module
Collapse
No announcement yet.

character set warning

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • character set warning

    I got lots of warnings in the error file:

    [Warning] Client failed to provide its character set. 'latin1' will be used as client character set

    How can I fixed it? the only connection is the slave replication.

    Thanks

  • #2
    Hi,

    Which MySQL/Percona version you are using ? I'm not sure but you might be hitting this bug http://bugs.mysql.com/bug.php?id=69160
    Can you provide some more details like which connector you are using with version? also my.cnf of master and slave? Thanks.

    Comment


    • #3
      Hi Folks, I have the same issue. The error log file start to be huge.

      I tried to disable the warnings from my.cnf using log-warnings=0 and log_warnings_suppress=1592 but without any result, warnings are still there.

      This error is generated because of Haproxy when he's doing mysql-check. Any idea how to solve this issue or disable warnings?

      bug already reported by someone else: http://bugs.mysql.com/bug.php?id=72543


      Installed packages:
      ii percona-toolkit 2.2.7 Advanced MySQL and system command-line tools
      ii percona-xtrabackup 2.1.9-744-1.precise Open source backup tool for InnoDB and XtraDB
      ii percona-xtradb-cluster-client-5.6 5.6.15-25.5-759.precise Percona Server database client binaries
      ii percona-xtradb-cluster-common-5.6 5.6.15-25.5-770.precise Percona Server database common files (e.g. /etc/mysql/my.cnf)
      ii percona-xtradb-cluster-galera-3.x 216.precise Galera components of Percona XtraDB Cluster
      ii percona-xtradb-cluster-server-5.6 5.6.15-25.5-759.precise Percona Server database server binaries


      Thanks in advance

      Comment


      • #4
        Any idea up ...

        Comment


        • #5
          Hi Folks, after one month I'm still looking for a solution related to this issue. Anyone from Percona team have an idea about this bug?

          Comment


          • #6
            Hello, I'm checking on this now for you - I'll post here when I get the info. Sorry for the delay!
            Is this an emergency? Get immediate assistance from Percona Support 24/7. Click here.

            Comment


            • #7
              Hi TomD,

              Thanks for looking this case.

              Just FYI:

              Distro: Ubuntu Precise (12.04.4)

              Error log:
              - Size: -rw-r----- 1 mysql root 1.1G Jun 12 16:45 staging.err
              - Message: 2014-06-12 16:45:41 1243 [Warning] Client failed to provide its character set. 'latin1' will be used as client character set.

              Installed Packages related to Percona:
              percona-toolkit ---- 2.2.8
              percona-xtrabackup ---- 2.1.9-744-1.precise
              percona-xtradb-cluster-client-5.6 ---- 5.6.15-25.5-759.precise
              percona-xtradb-cluster-common-5.6 ---- 5.6.15-25.5-770.precise
              percona-xtradb-cluster-galera-3.x ---- 216.precise
              percona-xtradb-cluster-server-5.6 ---- 5.6.15-25.5-759.precise


              haproxy ---- 1.5~dev26-2ppa1~precise

              Thanks in advance

              Comment


              • #8
                Hi TomD,

                Have you been able to reproduce the bug?

                Best regards,

                Comment


                • #9
                  I've learned that it is indeed a bug but an Oracle bug. I'll let you know here if I learn of a fix.
                  Is this an emergency? Get immediate assistance from Percona Support 24/7. Click here.

                  Comment


                  • #10
                    Hi TomD,

                    Thanks for this info. Looking forward to have some news about this bug

                    Comment


                    • #11
                      I am sorry to say that we are not prioritising a fix for this bug at the moment and are leaving this for Oracle to address for the time being at http://bugs.mysql.com/bug.php?id=72543.

                      One thing that could be done now is to file this bug (with a reference to #72543) on https://bugs.launchpad.net/percona-server/. Someone might comment with a workaround there, and we also may get an idea of how many users are affected, which influences prioritisation.

                      Comment


                      • #12
                        Hi Iaurynas,

                        No problem. As it's upstream bug, you should just notify them to look at this.

                        Comment

                        Working...
                        X