Getting “Error establishing a database connection” after restart. Checked the logs: [ERROR] [MY-013183] [InnoDB] Assertion failure: fut0lst.ic:86:addr.page == FIL_NULL
Happens on one site. Created a plain, new site - works fine.
Can not access Adminer either.
I have reviewed most articles in the forum pertaining the “Error establishing a database connection” however no solutions have worked or matched the error I’m receiving.
Hi @willjrc - thanks for using Local! I’m sorry you’re running into issues.
That is quite the interesting error log… Did your machine crash to cause the restart? It looks like something prevented Local from saving to the database correctly. I’m sure you’ve seen this in there, but this is in the logs on repeat:
[MY-010229] [Server] Starting crash recovery…“,“timestamp”:“2022-08-09T17:36:37.759Z”}
[MY-010232] [Server] Crash recovery finished.”,“timestamp”:“2022-08-09T17:36:37.759Z”}
[MY-013183] [InnoDB] Assertion failure: fut0lst.ic:86:addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA thread 123145313951744",“timestamp”:“2022-08-09T17:36:37.760Z”}
“InnoDB: We intentionally generate a memory trap.”,“timestamp”:“2022-08-09T17:36:37.760Z”}
“InnoDB: Submit a detailed bug report to http://bugs.mysql.com.”,“timestamp”:“2022-08-09T17:36:37.760Z”}
“InnoDB: If you get repeated assertion failures or crashes, even immediately after the mysqld startup, there may be corruption in the InnoDB tablespace. Please refer to http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html about forcing recovery. Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware… The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash.”
This mentions setting a flag in the config to force InnoDB to recover on it’s next boot. There are also steps a little further down for regenerating the site’s DB. I would try to back up whatever you have before trying this, but maybe give this a shot?