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

With FIPS enabled and performance_schema=off, instance crashes on CREATE VIEW

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: 5.6, 5.7
    • Fix Version/s: 5.7.23-23
    • Component/s: None
    • Labels:
      None

      Description

      Enable FIPS mode on Centos 6:

       

      [root@localhost vagrant]# sysctl crypto.fips_enabled
      crypto.fips_enabled = 1

      Reproducible test case:

       

      mysql> create database test;
      Query OK, 1 row affected (0.00 sec)
      
      mysql> use test
      Database changed
      mysql> create table t1 (id int primary key auto_increment,s char(10)) engine=innodb;
      Query OK, 0 rows affected (0.01 sec)
      
      mysql> insert into t1 values (null,'a');
      Query OK, 1 row affected (0.01 sec)
      
      mysql> select * from t1;
      +----+------+
      | id | s    |
      +----+------+
      |  1 | a    |
      +----+------+
      1 row in set (0.00 sec)
      
      mysql> create view t1v as select * from t1;
      ERROR 2013 (HY000): Lost connection to MySQL server during query

       

      2018-02-16T13:58:41.552241Z 4 [Note] Access denied for user 'root'@'localhost' (using password: NO)
      md5_dgst.c(78): OpenSSL internal error, assertion failed: Digest MD5 forbidden in FIPS mode!
      13:59:16 UTC - mysqld got signal 6 ;
      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=8388608
      read_buffer_size=131072
      max_used_connections=1
      max_threads=152
      thread_count=1
      connection_count=1
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68324 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      
      Thread pointer: 0x7f5ab003f820
      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 = 7f5aecd8cd40 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec198c]
      /usr/sbin/mysqld(handle_fatal_signal+0x461)[0x799e11]
      /lib64/libpthread.so.0(+0xf7e0)[0x7f5aecad67e0]
      /lib64/libc.so.6(gsignal+0x35)[0x7f5aead0f495]
      /lib64/libc.so.6(abort+0x175)[0x7f5aead10c75]
      /usr/lib64/libcrypto.so.10(+0x6a07f)[0x7f5aebe9d07f]
      /usr/lib64/libcrypto.so.10(MD5_Init+0x49)[0x7f5aebea3ab9]
      /usr/sbin/mysqld(compute_md5_hash+0x24)[0xed0fe4]
      /usr/sbin/mysqld(_ZN10TABLE_LIST8calc_md5EPc+0x37)[0xd3f4a7]
      /usr/sbin/mysqld[0x75b339]
      /usr/sbin/mysqld(_Z17mysql_create_viewP3THDP10TABLE_LIST21enum_view_create_mode+0x8cc)[0xd273ac]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x11dd)[0xc991bd]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x5d5)[0xc9fa25]
      /usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xaca)[0xca057a]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x1b7)[0xca1fc7]
      /usr/sbin/mysqld(handle_connection+0x2a0)[0xd66830]
      /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xeda334]
      /lib64/libpthread.so.0(+0x7aa1)[0x7f5aecaceaa1]
      /lib64/libc.so.6(clone+0x6d)[0x7f5aeadc5bcd]
      
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (7f5ab003bfd0): is an invalid pointer
      Connection ID (thread ID): 5
      Status: NOT_KILLED
      
      You may download the Percona Server operations manual by visiting
      http://www.percona.com/software/percona-server/. You may find information
      in the manual which will help you identify the cause of the crash.

       

      Could not reproduce on MySQL Community edition 5.6 or 5.7 releases (latest only).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                satya.bodapati Satya Bodapati
                Reporter:
                jericho.rivera Jericho Rivera
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 26 minutes
                  26m