You'll now try to disable binary log-bin in MAMP (or MAMP PRO) #log-bin=mysql-bin
MAMP MYSQL SERVER NOT STARTING WINDOWS
With Windows Explorer go to folder C:\MAMP\db\mysql\ First backup all files that begin with mysql-bin.*, then delete them (including mysql-bin.index file.) Then try starting all MAMP servers again (wait for MySQL to turn light on).
MySQL Server on MAMP-Windows Will Not Start
MAMP MYSQL SERVER NOT STARTING CODE
PHP Warning: mysqli_close() expects parameter 1 to be mysqli, boolean given in Command line code on line 1 PHP Warning: mysqli_fetch_assoc() expects parameter 1 to be mysqli_result, null given in Command line code on line 1 PHP Warning: mysqli_query() expects parameter 1 to be mysqli, boolean given in Command line code on line 1 PHP Warning: mysqli_connect(): (HY000/2002): No connection could be made because the target machine actively refused it. Operations related to importing and exporting data are disabled Normally deleting ib_logfile0 and ib_logfile1 fixed that for me, but with MAMP, I took your advice and deleted the index file.
However with MAMP, this appears to happen all the time. This is in all installations, including a real one on a Linux server. I find that MySQL is a bit flaky and doesn’t restart if it hasn’t shut down properly. Sudo rm -rf /var/db/receipts/com.mysql.* rm -rf /Library/Application\ Support/appsolute/MAMP\ PRO/db/mysql56/ib_logfile* Vim /etc/hostconfig and removed the line MYSQLCOM=-YES.
Sudo rm -rf /Library/PreferencePanes/MySQL* Sudo rm -rf /Library/StartupItems/MySQLCOM Rm /Applications/MAMP/db/mysql56/ib_logfile* Rm /Applications/MAMP/db/mysql/ib_logfile* #(or wherever your MAMP is installed) Version: '5.5.25' socket: '/Applications/MAMP/tmp/mysql/mysql.sock' port: 0 Source distribution
My solution for this issue was to: Close MAMP Go to Applications/MAMP/tmp/mysql delete the file Restart MAMP Share 130415 13:42:12 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysqlġ30415 13:42:12 Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql/ is case insensitiveġ30415 13:42:12 Plugin 'FEDERATED' is disabled.ġ30415 13:42:12 InnoDB: The InnoDB memory heap is disabledġ30415 13:42:12 InnoDB: Mutexes and rw_locks use GCC atomic builtinsġ30415 13:42:12 InnoDB: Compressed tables use zlib 1.2.3ġ30415 13:42:12 InnoDB: Initializing buffer pool, size = 128.0Mġ30415 13:42:12 InnoDB: Completed initialization of buffer poolġ30415 13:42:12 InnoDB: highest supported file format is Barracuda.ġ30415 13:42:13 InnoDB: Waiting for the background threads to startġ30415 13:42:14 InnoDB: 1.1.8 started log sequence number 1707549ġ30415 13:42:14 Event Scheduler: Loaded 0 eventsġ30415 13:42:14 /Applications/MAMP/Library/bin/mysqld: ready for connections. This sometimes leads to a problem where, after restarting the machine MAMP can start the Apache Server, but can not start the MySQL server for some reason. I had to hard reset my computer while MAMP was still running. I think it's possible the socket lock file ( tmp/mysql/) gets corrupted and needs to be regenerated. Recreate the folder and a subfolder: mkdir tmp mkdir tmp/mysql. Here's what worked for me: cd /Applications/MAMP. Previous Post Next Post Mysql server on MAMP won't startġ.
0 kommentar(er)
