Crashing after reverting back to MySQL [Updated]

I decided to try Percona on one of my servers to see how well it performed.

I was using MySQL 5.0 so I installed Percona 5.0 but I heard Percona 5.5 was better, so I upgraded it.

After a while I removed Percona and all Percona libraries, reinstalled MySQL, and restored a backup I had made before I installed Percona. (The database itself, not a dump of the queries to create it)

Now I’m being bombarded with errors. I tried with a fresh install of MySQL with the default databases too.


111022 16:45:56 mysqld started111022 16:45:57 InnoDB: Started; log sequence number 3 596986169111022 16:45:57 [Note] /usr/libexec/mysqld: ready for connections.Version: ‘5.0.77’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 Source distribution len 1000; hex ffffffff0000ffffffff000005d669d2000088b0ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000000057c50000000000000000ffffffff0000ffffffff000000000000ffffffff0000ffffffff000000000000ffffffff0000ffffffff000005d669d20002000fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff01cb01130065db85188423900112ec9b5b5f00008000000069f0000069f200000003239142d545bf00000000000000000000000000083b7c80210000000000000002001e001f00000000000000000000000000000000004c202061333034302020202031323638333639390d0100020020696e66696d756d0008000b000073757072656d756d000dfe860718000010077500061cff00000000066dc000001b3420f60000b25f00000000000700038000009e00020000009e00000003aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa0000000000000f9e00004000234e00008000011600000001ffffffffffffffffffffffffffffffff0000000000000f9e00004000237600008000016600000001ffffffffffffffffffffffffffffffff0000000000000f9e0000800000c600008000013e00000001ffffffffffffffffffffffffffffffff0000000000000f9e0000800001160000800004ae00000001ffffffffffffffffffffffffffffffff0000000000000f9e0000800000ee00008000018e00000001ffffffffffffffffffffffffffffffff0000000000000f9e0000800001660000800001b600000001ffffffffffffffffffffffffffffffff0000000000000f9e00008000018e0000800001de00000001ffffffffffffffffffffffffffffffff0000000000000f9e0000800001b600008000020600000001ffffffffffffffffffffffffffffffff0000000000000f9e0000800001de00008000022e00000001ffffffffffffffffffffffffffffffff0000000000000f9e00008000020600008000025600000001ffffffffffffffffffffffffffffffff0000000000000f9e00008000022e0000800002a600000001ffffffffffffffffffffffffffffffff0000000000000f9e0003c0000a4e000200001b56; asc i W i e # [_ i i # B E ;| ! L a3040 12683699 infimum supremum u m 4 _ @ #N @ #v f > f . V . N V;111022 16:50:26InnoDB: Assertion failure in thread 1164069184 in file fsp0fsp.c line 1431InnoDB: We intentionally generate a memory trap.InnoDB: Submit a detailed bug report to If you get repeated assertion failures or crashes, evenInnoDB: immediately after the mysqld startup, there may beInnoDB: corruption in the InnoDB tablespace. Please refer toInnoDB: about forcing recovery.111022 16:50:26 - mysqld got signal 11 ;This could be because you hit a bug. It is also possible that this binaryor one of the libraries it was linked against is corrupt, improperly built,or misconfigured. This error can also be caused by malfunctioning hardware.We will try our best to scrape up some info that will hopefully help diagnosethe problem, but since we have already crashed, something is definitely wrongand this may fail.key_buffer_size=8384512read_buffer_size=131072max_used_connections=3max_connections=100threads_connected=2It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225787 Kbytes of memoryHope that’s ok; if not, decrease some variables in the backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong…Cannot determine thread, fp=0x45623fb0, backtrace may not be correct.Bogus stack limit or frame pointer, fp=0x45623fb0, stack_bottom=0x45620000, thread_stack=262144, aborting backtrace.Trying to get some variables.Some pointers may be invalid and cause the dump to abort…thd->query at 0x17f29270 = ALTER TABLE exampleENGINE = InnoDBthd->thread_id=18The manual page at MySQL :: MySQL 8.0 Reference Manual :: B.3.3.3 What to Do If MySQL Keeps Crashing containsinformation that should help you find out what is causing the crash.

I created a database test, with the table example and inserted a few random rows.

The following on browser errors I receive:

Lost connection to MySQL server during query

MySQL server has gone away

Sometimes MySQL will shutdown after, forcing me to restart the daemon.

I’ve been working for days trying different things but I can’t solve this issue.

Can any one help me?

Try restoring the backup to MySQL 5.5 or Percona 5.5 to see if that helps. Maybe you took the backup at a later time than you think?

Also, hopefully you kept the database files that you upgraded to Percona 5.5, since you could use those to get a mysqldump and then go back to MySQL 5.0.

It’s not the backup that’s the issue. I reinstalled MySQL, removing all data from /var/lib/mysql/ then running mysql_secure_installation.

I then created a test database, which failed to perform correctly as indicated in the error log. Whether I’m using 5.0 or 5.5 it still fails.