File errors on startup after update, plus .ibd file is missing error

I have been using local for roughly a year now with no trouble. I was out of the office over the holidays, returned today, and was prompted to update to 8.2. Afterwards, trying to start any of my local sites yields various errors. Once they are started, they are not able to connect to the database. I have numerous errors in the log file, but repeated ones are:

[ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35",“process”:“mysql”,“thread”:“main”,“timestamp”:“2024-01-04T17:13:29.653Z”}

{“class”:“Process”,“level”:“warn”,“message”:“2024-01-04T16:31:35.095172Z 10 [Warning] [MY-012049] [InnoDB] Cannot calculate statistics for table local.wp_options because the .ibd file is missing. Please refer to http://dev.mysql.com/doc/refman/8.0/en/innodb-troubleshooting.html for how to resolve the issue.”,“process”:“mysql”,“thread”:“main”,“timestamp”:“2024-01-04T16:31:35.096Z”}


What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

It appears that I can create, start, and run a new site without errors.

I receive various errors when trying to start an existing site:

CleanShot 2024-01-04 at 12.00.00@2x
CleanShot 2024-01-04 at 12.01.13@2x


System Details

  • Local Version: Version 8.2.0+6554

  • Operating System (OS) and OS version: MacOS 14.1.2


Local Logs

local-lightning.log (606.3 KB)

Hi @donb625

Since you can create new sites okay can you try reimporting a site getting the errors to see if that works? The steps would look like this:

  • Locate the site files on your machine, and save a copy of them to your desktop. If you click Go to Site Folder under your site name it should take you right to where they are located.
  • Once you have those copied, completely delete the site from Local
  • Restart Local/your machine
  • Reimport the site back into Local. You can refer here on how to Restore from only Local site files
1 Like

Thanks for the reply, @Nick-B! Just based on a quick test of two sites, the copy, delete, and re-import method that you outlined seems to get them back up and operational.

1 Like

Glad to hear it @donb625! :green_heart:

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.