Uploaded image for project: 'Percona Server for MySQL'
  1. Percona Server for MySQL
  2. PS-5757

Percona Server 5.7.26-29 - signal 11 "ACL_PROXY_USER"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Medium
    • Resolution: Duplicate
    • Affects Version/s: 5.7.26-29
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      After updating Percona Server 5.7.25 to 5.7.26-29, the server crashes with signal 11 every time.

       

      EL7 with all updates / kernel 3.10.0-957.21.3.el7.x86_64

       

      Percona-Server-shared-compat-57-5.7.26-29.1.el7.x86_64
      Percona-Server-shared-57-5.7.26-29.1.el7.x86_64
      Percona-Server-client-57-5.7.26-29.1.el7.x86_64
      Percona-Server-server-57-5.7.26-29.1.el7.x86_64

       

      After downgrade back to 5.7.25-28.1.el7.x86_64 it works as normal.

       

      From MySQL log:

      mysqld: 07:23:17 UTC - mysqld got signal 11 ;
      mysqld: This could be because you hit a bug. It is also possible that this binary
      mysqld: or one of the libraries it was linked against is corrupt, improperly built,
      mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
      mysqld: Attempting to collect some information that could help diagnose the problem.
      mysqld: As this is a crash and something is definitely wrong, the information
      mysqld: collection process might fail.
      mysqld: Please help us make Percona Server better by reporting any
      mysqld: bugs at https://bugs.percona.com/
      mysqld: key_buffer_size=8388608
      mysqld: read_buffer_size=131072
      mysqld: max_used_connections=0
      mysqld: max_threads=501
      mysqld: thread_count=0
      mysqld: connection_count=0
      mysqld: It is possible that mysqld could use up to
      mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 207292 K bytes of memory
      mysqld: Hope that's ok; if not, decrease some variables in the equation.
      mysqld: Thread pointer: 0x3b88130
      mysqld: Attempting backtrace. You can use the following information to find out
      mysqld: where mysqld died. If you see no messages after this, something went
      mysqld: terribly wrong...
      mysqld: stack_bottom = 7ffc4d479130 thread_stack 0x40000
      mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf1444b]
      mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x471)[0xd4e981]
      mysqld: /lib64/libpthread.so.0(+0xf5d0)[0x7faa4fbfa5d0]
      mysqld: /usr/sbin/mysqld(_ZN14ACL_PROXY_USER14check_validityEb+0x3a)[0xd9155a]
      mysqld: /usr/sbin/mysqld[0xd99442]
      mysqld: /usr/sbin/mysqld(_Z10acl_reloadP3THD+0x5c3)[0xd9a483]
      mysqld: /usr/sbin/mysqld(_Z8acl_initb+0x21f)[0xd9a8bf]
      mysqld: /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x1c78)[0xd4a188]
      mysqld: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7faa4dce6495]
      mysqld: /usr/sbin/mysqld[0x79e0e4]
      mysqld: Trying to get some variables.
      mysqld: Some pointers may be invalid and cause the dump to abort.
      mysqld: Query (0): Connection ID (thread ID): 0
      mysqld: Status: NOT_KILLED

       

      I note the `ACL_PROXY_USER` in the stack trace. LDAP authentication is used with Percona PAM auth plugin. This same configuration is used on Percona XtraDB cluster (currently still on 5.7.25-31.35.1.el7.x86_64) and I am afraid the cluster would crash when/if I updated it to 5.7.26.

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned
                Reporter:
                v__o Ville Ojamo
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: