MySQL issue A connection attempt failed

MySQL issue A connection attempt failed, #2002 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (0 Replies, Read 12654 times)

fillcraft	# October 29, 2013, 6:09 am
Group: Member Post Group: Newbie Posts: 3 Status:	I tried to find the solution first, nothing worked for me. Problem: I had wamp and ammps installed on same PC, Windows Ultimate 7 SP1. My Antivirus is Avast internet seurity 2014. I deleted wamp from my system without uninstalling it. My ammps stoped working phpmyadmin shows following error #2002 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. The server is not responding (or the local server's socket is not correctly configured). MySQL error log 2013-10-29 10:10:41 1228 [Note] Plugin 'FEDERATED' is disabled. 2013-10-29 10:10:41 1228 [Note] InnoDB: The InnoDB memory heap is disabled 2013-10-29 10:10:41 1228 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2013-10-29 10:10:41 1228 [Note] InnoDB: Compressed tables use zlib 1.2.3 2013-10-29 10:10:41 1228 [Note] InnoDB: Not using CPU crc32 instructions 2013-10-29 10:10:41 1228 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2013-10-29 10:10:42 1228 [Note] InnoDB: Completed initialization of buffer pool 2013-10-29 10:10:42 1228 [Note] InnoDB: The first specified data file .\ibdata1 did not exist: a new database to be created! 2013-10-29 10:10:42 1228 [Note] InnoDB: Setting file .\ibdata1 size to 12 MB 2013-10-29 10:10:42 1228 [Note] InnoDB: Database physically writes the file full: wait... 2013-10-29 10:10:43 1228 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB 2013-10-29 10:10:49 1228 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB 2013-10-29 10:10:52 1228 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0 2013-10-29 10:10:52 1228 [Warning] InnoDB: New log files created, LSN=45781 2013-10-29 10:10:52 1228 [Note] InnoDB: Doublewrite buffer not found: creating new 2013-10-29 10:10:52 1228 [Note] InnoDB: Doublewrite buffer created 2013-10-29 10:10:52 1228 [Note] InnoDB: 128 rollback segment(s) are active. 2013-10-29 10:10:54 1228 [Warning] InnoDB: Creating foreign key constraint system tables. 2013-10-29 10:10:54 1228 [Note] InnoDB: Foreign key constraint system tables created 2013-10-29 10:10:54 1228 [Note] InnoDB: Creating tablespace and datafile system tables. 2013-10-29 10:10:54 1228 [Note] InnoDB: Tablespace and datafile system tables created. 2013-10-29 10:10:54 1228 [Note] InnoDB: Waiting for purge to start 2013-10-29 10:10:54 1228 [Note] InnoDB: 5.6.14 started; log sequence number 0 2013-10-29 10:10:54 1228 [Note] Server hostname (bind-address): ''; port: 3306 2013-10-29 10:10:54 1228 [Note] IPv6 is available. 2013-10-29 10:10:54 1228 [Note] - '::' resolves to '::'; 2013-10-29 10:10:54 1228 [Note] Server socket created on IP: '::'. 2013-10-29 10:10:56 1228 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. for how you can resolve the problem. 2013-10-29 10:10:56 1228 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened. 2013-10-29 10:10:56 1228 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. for how you can resolve the problem. 2013-10-29 10:10:56 1228 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. for how you can resolve the problem. 2013-10-29 10:10:56 1228 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened. 2013-10-29 10:10:57 1228 [Note] Event Scheduler: Loaded 0 events 2013-10-29 10:10:57 1228 [Note] mysql\bin\mysqld.exe: ready for connections. Version: '5.6.14-log' socket: '' port: 3306 MySQL Community Server (GPL) Solutions I adopted:* 1. what ever I found online, did not work. 2. Restored the wamp and properly uninstalled it, then uninstalled ammps. and reinstalled ammps. Conclusion: Mysql is not working for me. I also noticed when I tried to stop the mysql from UI it does not stop either, when I close the ammp mysqld.exe still remain in task manager
IP: --

Users viewing this topic
	1 guests, 0 users.