I checked logs > mysql > error.log and it looks like I need to edit the innodb_data_file in my.cnf back to what it was—but I’m not able to find “innodb_data_file_path” in conf > mysql > my.cnf Below is the error.log msg.
171220 20:53:20 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
171220 20:53:20 [Note] Plugin ‘FEDERATED’ is disabled.
171220 20:53:20 InnoDB: The InnoDB memory heap is disabled
171220 20:53:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
171220 20:53:20 InnoDB: Compressed tables use zlib 1.2.8
171220 20:53:20 InnoDB: Using Linux native AIO
171220 20:53:20 InnoDB: Initializing buffer pool, size = 8.0M
171220 20:53:20 InnoDB: Completed initialization of buffer pool
InnoDB: Error: checksum mismatch in data file ./ibdata1
171220 20:53:20 InnoDB: Could not open or create data files.
171220 20:53:20 InnoDB: If you tried to add new data files, and it failed here,
171220 20:53:20 InnoDB: you should now edit innodb_data_file_path in my.cnf back
171220 20:53:20 InnoDB: to what it was, and remove the new ibdata files InnoDB created
171220 20:53:20 InnoDB: in this failed attempt. InnoDB only wrote those files full of
171220 20:53:20 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
171220 20:53:20 InnoDB: remove old data files which contain your precious data!
171220 20:53:20 [ERROR] Plugin ‘InnoDB’ init function returned error.
171220 20:53:20 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
171220 20:53:20 [ERROR] Unknown/unsupported storage engine: InnoDB
171220 20:53:20 [ERROR] Aborting
My computer froze up (not something that normally occurs) and I did a hard restart. I’m not sure if this was related or not because I found 8 instances of the error I initially quoted in the thread above. Other than that all was going smoothly—or so I thought.
I was able to create a new site without using a blueprint
I was NOT able to create a site from my current blueprint
I was able to create a new site from an old blueprint
I created a new blueprint from the site I just created from the old blueprint
Attempted to create a new site from the above blueprint and was not able to.
Below are 3 screenshots showing adminer, local database control panel section, and the mysql error log.
Can you explain what you’re trying to do with Blueprints and how they fit into the issue that you mentioned at the beginning of this topic? Do you have a Blueprint that you want to use as a backup of sorts?
Does the site still exist that you created this topic for? If so, you may need to use innodb_force_recovery. You can enable it in the my.cnf file in the conf directory if you’re using the Custom environment. Once you do that, try restarting the site in Local.
Does the site still exist that you created this topic for?
It does, but I am not able to open it in Local. I re-created it from an offsite backup on a live dev site.
Can you explain what you’re trying to do with Blueprints and how they fit into the issue that you mentioned at the beginning of this topic?
The biggest advantage of using local is being able to whip up a starter site from a blueprint. Blueprints have to be updated as time goes by due to software updates and base tweaks in what you want included in a “starter” site. At this point I have no way to create blueprints that work. This makes Local pretty much useless to me----well I guess I could create a site and then import a “backup” to use a s a blueprint… Not the most ideal situation.
