Bug #75108 | No Connection to MySQL server. Port 3306 not available. | ||
---|---|---|---|
Submitted: | 4 Dec 2014 19:35 | Modified: | 15 Jan 2015 19:26 |
Reporter: | david higgins | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 6.2.3 | OS: | Windows (Microsoft Windows 7 Home Premium Service Pack 1) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[4 Dec 2014 19:35]
david higgins
[4 Dec 2014 19:37]
david higgins
complete wb.log error file
Attachment: wb.log for MySQL error server not available - port3306 no connection.txt (text/plain), 23.89 KiB.
[9 Dec 2014 20:24]
Sveta Smirnova
Thank you for the report. Please provide MySQL Server error log file.
[9 Dec 2014 20:39]
david higgins
wb.log file requested by Sveta Smirnova (MySQL tech support)
Attachment: wb.log (application/octet-stream, text), 23.89 KiB.
[9 Dec 2014 20:41]
david higgins
Hi Sveta, Per your request on December 9, I have just posted the "wb.log" file. Thank you in advance for your assistance. Dave Higgins
[9 Dec 2014 20:46]
Sveta Smirnova
David, thank you for the file, but I asked for *server* error log file, not MySQL Workbench log file. It is usually located in C:\Program Data\MySQL\MySQL Server VERSION_NUMBER\data directory. Or, if your server was restarted you can query log_error system variable.
[9 Dec 2014 22:34]
david higgins
MySQL server error log file requested by Sveta Smirnova on 20141209
Attachment: DAVIDHIGGINS-PC (from 20141108-20141209).err (application/octet-stream, text), 430.22 KiB.
[9 Dec 2014 22:40]
david higgins
Hi Sveta, Per your request on December 9, I have just posted the MySQL Server error log file called "DAVIDHIGGINS-PC (from 20141108-20141209).err". The error log file is rather large, so I copied the file, then deleted everything older than 20141108 (except for the initial MySQL installation). If it helps, the first time the MySQL server stopped responding was on 2014-11-11, and the second time was 2014-12-04. Thank you in advance for your assistance. Dave Higgins
[11 Dec 2014 21:12]
Sveta Smirnova
Thank you for the feedback. Error log file contains records, showing what MySQL server was restarted few times per day lately: 2014-12-08 10:11:09 2800 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: ready for connections. Version: '5.6.21' socket: '' port: 3306 MySQL Community Server (GPL) 2014-12-08 12:45:57 2800 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: Normal shutdown 2014-12-08 12:45:58 2800 [Note] Giving 0 client threads a chance to die gracefully 2 ... 2014-12-08 12:46:00 2800 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: Shutdown complete 2014-12-08 15:42:47 2408 [Note] Plugin 'FEDERATED' is disabled. 20 ... 2014-12-08 15:43:19 2408 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: ready for connections. Version: '5.6.21' socket: '' port: 3306 MySQL Community Server (GPL) 2014-12-08 19:55:01 2408 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: Normal shutdown 2014-12-08 19:55:01 2408 [Note] Giving 0 client threads a chance to die gracefully 2 ... 2014-12-08 19:55:04 2408 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe: Shutdown complete 2014-12-09 08:48:33 2488 [Note] Plugin 'FEDERATED' is disabled. 2 This certainly more often than once per night when the job is run. Also I see only graceful shutdowns with one exception: corruption of InnoDB files at Dec, 04. So looks like some other process on your system involved. Please check.
[26 Dec 2014 0:12]
david higgins
MySQL server error log file requested by Sveta Smirnova (20141225)
Attachment: DAVIDHIGGINS-PC (mysql errors every 22 days on Nov11 and Dec03 and Dec25).err (application/octet-stream, text), 574.20 KiB.
[26 Dec 2014 0:27]
david higgins
Hi Sveta, Sorry to bug you again (especially on Christmas), but MySQL had the very same file corruption and error as before (Port 3306 not available). This is the 3rd time (it seems to happen every 22 days: November 11, December 3, December 25). In your previous correspondence, you mentioned that there may be a process running on my computer that is causing MySQL to become corrupt ... Any ideas what process could do this? I am currently running MySQL on my laptop (since it is being used for development), which means that I normally shut down MySQL on a daily basis (gracefully). I am concerned since I expect to roll out the application soon onto a server. Attached is the MySQL error log file that you requested in our previous conversation. Any ideas what could cause this? Thanks, Dave Higgins
[13 Jan 2015 19:52]
Sveta Smirnova
Thank you for the feedback. In newly uploaded error log file I see message: "[ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace 1on1/dmssale uses space ID: 27 at filepath: .\1on1\dmssale.ibd. Cannot open tablespace 1on1bak/dmssale which uses space ID: 27 at filepath: .\1on1bak\dmssale.ibd InnoDB: Error: could not open single-table tablespace file .\1on1bak\dmssale.ibd" Have you moved/renamed directory lon1 manually?
[14 Jan 2015 3:34]
david higgins
Hi Sveta, You are absolutely correct. On November 13, I did indeed change the folder from "C:\1on1\1on1dev\1on1_web" to "C:\1on1\1on1dev\1on1". But the first time I encountered the error was 2 days PRIOR to renaming the file folder (on Nov 11). And it seemed to work fine until December 3, and again on December 25. How should I have renamed the folder? Thanks, Dave Higgins
[15 Jan 2015 19:16]
Sveta Smirnova
Thank you for the feedback. You should've not rename the folder at all. Regarding to earlier issues: error log, provided earlier clearly show you stopped the server, therefore it was not accessible. Maybe you simply forgot to start it? Anyway, this report looks like support request mostly and not as result of MySQL bug. Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/ Please consider to open topic or ticket there or we need repeatable test case, proving this is bug in MySQL code and not usage issue.
[15 Jan 2015 19:26]
david higgins
Hi Sveta, Thank you for your assistance. I consider this issue resolved, and appreciate your help. Have a great day, Dave Higgins