GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

mysqlbinlog segfault on 5.1.61-rel113.2-log

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

  • mysqlbinlog segfault on 5.1.61-rel113.2-log

    It's a normal situation where one want to decode the binlog to understand in case a replication failed.
    normally one would do:
    $ mysqlbinlog --verbose --base64-output=DECODE-ROWS >
    For some reason, starting with v5.1.60 it segfault.
    If i use the binary of mysqlbinlog from 5.1.59 it works.
    I have tried to run it both on rhel 5.7 and rhel 6.2, both segfault.

    [Percona-Server-5.1.61-rel13.2-430.Linux.x86_64/bin]# ldd mysqlbinlog
    linux-vdso.so.1 => (0x00007fff59ffc000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003e21800000)
    libmysqlclient.so.16 => /usr/lib64/libmysqlclient.so.16 (0x0000003631200000)
    libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003e23000000)
    libnsl.so.1 => /lib64/libnsl.so.1 (0x0000003e23400000)
    libm.so.6 => /lib64/libm.so.6 (0x0000003e21c00000)
    libz.so.1 => /usr/lib64/libz.so.1 (0x0000003e22400000)
    librt.so.1 => /lib64/librt.so.1 (0x0000003e22c00000)
    libc.so.6 => /lib64/libc.so.6 (0x0000003e21000000)
    /lib64/ld-linux-x86-64.so.2 (0x0000003e20c00000)

    [Percona-Server-5.1.59-rel13.0-325.Linux.x86_64/bin]# ldd mysqlbinlog
    linux-vdso.so.1 => (0x00007fff8e8e6000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003e21800000)
    libmysqlclient.so.16 => /usr/lib64/libmysqlclient.so.16 (0x0000003631200000)
    librt.so.1 => /lib64/librt.so.1 (0x0000003e22c00000)
    libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003e23000000)
    libnsl.so.1 => /lib64/libnsl.so.1 (0x0000003e23400000)
    libm.so.6 => /lib64/libm.so.6 (0x0000003e21c00000)
    libz.so.1 => /usr/lib64/libz.so.1 (0x0000003e22400000)
    libc.so.6 => /lib64/libc.so.6 (0x0000003e21000000)
    /lib64/ld-linux-x86-64.so.2 (0x0000003e20c00000)

  • #2
    Is this specific to Percona Server's distribution or does it happen with standard MySQL too?

    Comment


    • #3
      I haven't tried yet, is there a way to get the binaries as you can with percona?

      Comment


      • #4
        Sure, just download the tarball and extract it.

        Comment


        • #5
          Baron, it is not mysqlbinlog binary problem. It seems that this is libmysqlclient16 bug.
          Segmentation fault happens for me after I update the libmysqlclient16 only to 5.1.61 and all other packages are left with older versions.

          I use Percona lucid version.

          The ubuntu mysql community version (lucid backported 5.1.61-0ubuntu0.10.04.1) works fine though.

          Comment


          • #6
            If the bug is in Percona's libmysqlclient16, I am sure the developers would like you to file a bug report on Launchpad. (It would be nice if you paste a link on this forum too).

            Comment


            • #7
              I was going to after I gather some more data. After all the issue seems much more complicated than I thought.
              I'm able to reproduce the segmentation fault only if I have the libmysqlclient16 package in newer version than percona-server-server-5.1. For example if:
              libmysqlclient16 5.1.60-rel13.1-413.lucid
              percona-server-server-5.1 5.1.59-rel13.0-325.lucid
              When I update percona-server-server-5.1 to the same version or newer than libmysqlclient16 - all works well.
              When I tried
              mysql-server-5.1 5.1.41-3ubuntu12
              libmysqlclient16 5.1.61-0ubuntu0.10.04.1
              the problem didn't happen though. I had not enough time to check other community versions.

              Any way it does not look like a valid bug to be filed, since it's never recommended to use inconsistent package versions within mysql pieces.

              Infin1ty: were your packages in exactly the same versions?

              Comment


              • #8
                przemek wrote on Tue, 03 April 2012 18:50
                I was going to after I gather some more data. After all the issue seems much more complicated than I thought.
                I'm able to reproduce the segmentation fault only if I have the libmysqlclient16 package in newer version than percona-server-server-5.1. For example if:
                libmysqlclient16 5.1.60-rel13.1-413.lucid
                percona-server-server-5.1 5.1.59-rel13.0-325.lucid
                When I update percona-server-server-5.1 to the same version or newer than libmysqlclient16 - all works well.
                When I tried
                mysql-server-5.1 5.1.41-3ubuntu12
                libmysqlclient16 5.1.61-0ubuntu0.10.04.1
                the problem didn't happen though. I had not enough time to check other community versions.

                Any way it does not look like a valid bug to be filed, since it's never recommended to use inconsistent package versions within mysql pieces.

                Infin1ty: were your packages in exactly the same versions?
                # rpm -qa | grep -i Percona
                Percona-Server-devel-51-5.1.61-rel13.2.430.rhel5
                percona-release-0.0-1
                Percona-Server-client-51-5.1.61-rel13.2.430.rhel5
                Percona-Server-shared-compat-5.1.61-rel13.2.430.rhel5
                Percona-Server-server-51-5.1.61-rel13.2.430.rhel5

                binlog segfault.
                But!, if i remove Percona-Server-shared-compat and replace it with Percona-Server-shared-5.1 it works, but i need the compat package to use perl-DBD-MySQL and other libraries.
                What can i do about it?

                Comment

                Working...
                X