Mamp not starting5/7/2023 T02:36:17.415180Z 0 InnoDB: Highest supported file format is Barracuda. T02:36:17.390613Z 0 InnoDB: Completed initialization of buffer pool T02:36:17.380118Z 0 InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M T02:36:17.373365Z 0 InnoDB: GCC builtin _atomic_thread_fence() is used for memory barrier T02:36:17.373326Z 0 InnoDB: Mutexes and rw_locks use GCC atomic builtins T02:36:17.363631Z 0 Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql57/ is case insensitive Operations related to importing and exporting data are disabled ![]() Please use -explicit_defaults_for_timestamp server option (see documentation for more details). T02:36:17.347806Z 0 TIMESTAMP with implicit DEFAULT value is deprecated. Mysqld: World-writable config file '/Applications/MAMP/tmp/mysql/my.cnf' is ignored. T02:36:17.6NZ mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql57 ![]() So the database is still somewhere? But why can't I see it? T02:36:17.6NZ mysqld_safe Logging to '/Applications/MAMP/logs/mysql_error.log'. However, I can see in the error log that there is an issue with one of my databases (drupal8). I was able to log in to MYSQL only over command line with /Applications/MAMP/bin/startMysql.sh ![]() I am assuming I can re-connect it to the existing MySQL database so I don’t lose that work.My Macbook crashed and now MAMP (latest version v6.6.3) is not working anymore. I also went back to my browser history to re-enter the url I was using to go directly to the site I have been developing, and that doesn’t work either ( I have no problem with just reinstalling the EE2 software from scratch if that is the simplest approach. Moreover, I know I am using the same url in the browser to get to the control panel, since I use the application 1password to login which generates the same string as I used since the start of this project. No, I don’t believe I changed anything regarding my EE installation (although I wouldn’t be the first person who made such a claim). 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 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 Comments
Leave a Reply. |