Performance Schema MD5sum abort in RHEL FIPS=1 mode
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
New
|
Undecided
|
Unassigned | |||
5.6 |
Triaged
|
High
|
Unassigned | |||
5.7 |
Triaged
|
High
|
Unassigned | |||
8.0 |
New
|
Undecided
|
Unassigned |
Bug Description
Stack trace from percona xtradb cluster 5.6.37-82.2-56-log
Thread pointer: 0x26e8a80
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 = 7f23fc51ccf0 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/lib64/
/usr/lib64/
How to reproduce:
Setup new centos 7 instance https:/
Setup FIPS: https:/
do not forget to add ips=1 boot=/dev/sda2 to the end of GRUB_CMDLINE_LINUX line located in /etc/sysconfig/grub and generate new config with grub2-mkconfig -o /boot/grub2/
Execute any statement against mysql server 5.6 or 5.7 compiled against openssl with performance schema enabled.
Upstream?