# InnoDB: ibuf cursor restoration fails!. ibuf record inserted to page **URL:** \ **Category:** Percona XtraDB Cluster 5.x\ **Created:** [January 31, 2020, 12:17pm UTC](https://forums.percona.com/t/innodb-ibuf-cursor-restoration-fails-ibuf-record-inserted-to-page/7407 "2020-01-31T12:17:21Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![jbiancot](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jbiancot/32/6030_2.png) [@jbiancot](https://forums.percona.com/u/jbiancot)\ **Post date:** [January 31, 2020, 12:17pm UTC](https://forums.percona.com/t/innodb-ibuf-cursor-restoration-fails-ibuf-record-inserted-to-page/7407/1 "2020-01-31T12:17:21Z")
Hi, We have a few Percona MySQL cluster XtraDB, on QAs on DEV and on Production servers. One of our QA environments just crashes. I don’t remember I have seen that error before. mysql Ver 14.14 Distrib 5.7.25-28, for debian-linux-gnu (x86\_64) using 6.3 Aborted connection 601343 to db: ‘information\_schema’ user: ‘root’ host: ‘10.102.60.212’ (Got an error reading communication packets) 2020-01-31T10:54:28.208251-05:00 603585 [Note] Aborted connection 603585 to db: ‘information\_schema’ user: ‘root’ host: ‘10.102.60.212’ (Got an error reading communication packets) 2020-01-31T11:28:52.216454-05:00 0 [ERROR] InnoDB: ibuf cursor restoration fails!. ibuf record inserted to page 2106:30778 2020-01-31T11:28:52.218591-05:00 0 [ERROR] InnoDB: Submit a detailed bug report to [http://bugs.mysql.com](http://bugs.mysql.com) PHYSICAL RECORD: n\_fields 6; 1-byte offsets; info bits 0 0: len 4; hex 0000083a; asc :;; 1: len 1; hex 00; asc ;; 2: len 4; hex 00002249; asc "I;; 3: len 16; hex 000001010c0f00c880e0860800088000; asc ;; 4: len 21; hex 50562d444454382d44414d532d4368726973747573; asc PV-DDT8-DAMS-Christus;; 5: len 8; hex 8000000056502313; asc VP# ;; PHYSICAL RECORD: n\_fields 6; 1-byte offsets; info bits 0 0: len 4; hex 0000083a; asc :;; 1: len 1; hex 00; asc ;; 2: len 4; hex 00002249; asc "I;; 3: len 16; hex 000001010c0f00c880e0860800088000; asc ;; 4: len 21; hex 50562d444454382d44414d532d4368726973747573; asc PV-DDT8-DAMS-Christus;; 5: len 8; hex 8000000056502313; asc VP# ;; DATA TUPLE: 3 fields; 0: len 4; hex 0000083a; asc :;; 1: len 1; hex 00; asc ;; 2: len 4; hex 0000783a; asc x:;; PHYSICAL RECORD: n\_fields 6; 1-byte offsets; info bits 0 0: len 4; hex 0000083a; asc :;; 1: len 1; hex 00; asc ;; 2: len 4; hex 0000796f; asc yo;; 3: len 16; hex 000001010c0f00c880e0860800088000; asc ;; 4: len 18; hex 50562d45636f5f4444542833292d44656d6f; asc PV-Eco\_DDT(3)-Demo;; 5: len 8; hex 800000005651df28; asc VQ (;; 2020-01-31T11:28:52.230235-05:00 0 [ERROR] [FATAL] InnoDB: Failed to restore ibuf position. 2020-01-31 11:28:52 0x7fefb61bd700 InnoDB: Assertion failure in thread 140667529189120 in file ut0ut.cc line 947 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to [http://bugs.mysql.com](http://bugs.mysql.com). InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: [url][http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html[/url]](http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html%5B/url%5D) InnoDB: about forcing recovery. 16:28:52 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 XtraDB Cluster better by reporting any bugs at [url][https://jira.percona.com/projects/PXC/issues[/url]](https://jira.percona.com/projects/PXC/issues%5B/url%5D) key\_buffer\_size=8388608 read\_buffer\_size=131072 max\_used\_connections=31 max\_threads=152 thread\_count=30 connection\_count=21 It is possible that mysqld could use up to key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_threads = 68412 K bytes of memory Hope that’s ok; if not, decrease some variables in the equation. Thread pointer: 0x0 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 = 0 thread\_stack 0x40000 /usr/sbin/mysqld(my\_print\_stacktrace+0x2c)[0xed82fc] /usr/sbin/mysqld(handle\_fatal\_signal+0x479)[0x7a8609] /lib/x86\_64-linux-gnu/libpthread.so.0(+0xf890)[0x7ff0b8b99890] /lib/x86\_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7ff0b6b1f067] /lib/x86\_64-linux-gnu/libc.so.6(abort+0x148)[0x7ff0b6b20448] /usr/sbin/mysqld[0x776ea9] /usr/sbin/mysqld(\_ZN2ib5fatalD1Ev+0x15d)[0x119017d] /usr/sbin/mysqld[0x101bcc0] /usr/sbin/mysqld[0x101c7b1] /usr/sbin/mysqld(\_Z29ibuf\_merge\_or\_delete\_for\_pageP11buf\_block\_tRK9page\_id\_tPK11page\_size\_tm+0xb28)[0x1022c98] /usr/sbin/mysqld(\_Z20buf\_page\_io\_completeP10buf\_page\_tb+0x1475)[0x11d5d55] /usr/sbin/mysqld(\_Z12fil\_aio\_waitm+0x216)[0x124c576] /usr/sbin/mysqld(io\_handler\_thread+0x108)[0x11341e8] /lib/x86\_64-linux-gnu/libpthread.so.0(+0x8064)[0x7ff0b8b92064] /lib/x86\_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff0b6bd262d] You may download the Percona XtraDB Cluster operations manual by visiting [url][http://www.percona.com/software/percona-xtradb-cluster/[/url]](http://www.percona.com/software/percona-xtradb-cluster/%5B/url%5D). You may find information in the manual which will help you identify the cause of the crash.