So, you asked was the site ever working: yes, as I said in the original note, for several days. Here’s my issue: what had been working for several days-starting up the servers using MAMP, logging into the EE2 Control Panel or going directly to pages I was creating via EE2-simply stopped working. And email is tricky business about tone, but I’m not sure what you mean about just having issues. But be careful: do notġ10522 14:52:26 InnoDB: remove old data files which contain your precious data!ġ10522 14:52:26 Plugin ‘InnoDB’ init function returned error.ġ10522 14:52:26 Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.ġ10522 14:52:26 Unknown/unsupported storage engine: InnoDB
#Mamp not starting mysql server full#
InnoDB only wrote those files full ofġ10522 14:52:26 InnoDB: zeros, but did not yet use them in any way. InnoDB: Some operating system error numbers are described atġ10522 14:52:26 InnoDB: Could not open or create data files.ġ10522 14:52:26 InnoDB: If you tried to add new data files, and it failed here,ġ10522 14:52:26 InnoDB: you should now edit innodb_data_file_path in my.cnf backġ10522 14:52:26 InnoDB: to what it was, and remove the new ibdata files InnoDB createdġ10522 14:52:26 InnoDB: in this failed attempt. InnoDB: Error number 35 means ‘Resource temporarily unavailable’.
(see below)Īnybody have this experience and find a way out?ġ10522 14:52:26 InnoDB: Unable to open the first data fileġ10522 14:52:26 InnoDB: Operating system error number 35 in a file operation. I looked at the MAMP mysql error log, but got no great insight. The Apache Server status light is green, but the MySQL Server status stays red.
Today, I used them again, logged out, and then later attempted to restart MAMP. I recently installed MAMP and EE2 on my Mac (OS X 10.6) and have been using them for the last several days.
0 kommentar(er)
