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

MySQL crashing after reaching max connections

    Details

    • Type: Bug
    • Status: Done
    • Priority: High
    • Resolution: Cannot Reproduce
    • Affects Version/s: 5.7.22-22
    • Fix Version/s: None
    • Component/s: None

      Description

      Hello Team, 

       

      MySQL crashed few times due to maxed out connections. We are using 5.7.22-22-log Percona Server (GPL), Release 22, Revision f62d93c on CentOS release 6.10 (Final) 64 bit OS.

       

      Please find the below reference from error log.

       

      09:27:48 UTC - mysqld got signal 11 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
      Attempting to collect some information that could help diagnose the problem.
      As this is a crash and something is definitely wrong, the information
      collection process might fail.
      Please help us make Percona Server better by reporting any
      bugs at http://bugs.percona.com/

      key_buffer_size=268435456
      read_buffer_size=2097152
      max_used_connections=583
      max_threads=1001
      thread_count=512
      connection_count=512
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4372306 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

       

      Thread pointer: 0x7f2bf805f810
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 7f30d8911d40 thread_stack 0x80000
      /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec60ec]
      /usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79e811]
      /lib64/libpthread.so.0[0x347000f7e0]
      /lib64/libc.so.6(memcpy+0xd2)[0x346fc897f2]
      /usr/lib64/mysql/plugin/server_audit.so(auditing+0xb5b)[0x7f31c87aa97b]
      /usr/lib64/mysql/plugin/server_audit.so(+0x95cb)[0x7f31c87ab5cb]
      /usr/sbin/mysqld[0x79f00e]
      /usr/sbin/mysqld(_Z18mysql_audit_notifyP3THD30mysql_event_general_subclass_tPKciS3_m+0x25d)[0x79f4dd]
      /usr/sbin/mysqld(_ZN12Query_logger17general_log_writeEP3THD19enum_server_commandPKcm+0x67)[0xbe7947]
      /usr/sbin/mysqld(_ZN12Query_logger17general_log_printEP3THD19enum_server_commandPKcz+0x15f)[0xbe7cff]
      /usr/sbin/mysqld(_Z15mysql_change_dbP3THDRK25st_mysql_const_lex_stringb+0x377)[0xc66037]
      /usr/sbin/mysqld(_Z16acl_authenticateP3THD19enum_server_commandb+0x1349)[0x7a9759]
      /usr/sbin/mysqld[0xc60aa4]
      /usr/sbin/mysqld(_Z22thd_prepare_connectionP3THDb+0x5a)[0xc6239a]
      /usr/sbin/mysqld(handle_connection+0x281)[0xd6a411]
      /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xeddd84]
      /lib64/libpthread.so.0[0x3470007aa1]
      /lib64/libc.so.6(clone+0x6d)[0x346fce8c4d]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0): is an invalid pointer
      Connection ID (thread ID): 73820
      Status: NOT_KILLED

       

      There was no error related to too many connections errors in the mysql error log. There was no core dump enabled in the server.

       

       

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                federoit Shishu Naik
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: