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:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:6.2.3 OS:Microsoft Windows (Microsoft Windows 7 Home Premium Service Pack 1)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[4 Dec 2014 19:35] david higgins
Description:
10:57:53 [ERR][      Workbench]: Console redirection failed.
10:57:53 [INF][      WBContext]: Parsing application arguments.
10:57:53 [INF][      WBContext]:     C:\Program Files\MySQL\MySQL Workbench 6.2 CE\MySQLWorkbench.exe
10:57:53 [INF][      Workbench]: Starting up Workbench
10:57:53 [INF][      Workbench]: Current environment:
	Command line: "C:\Program Files\MySQL\MySQL Workbench 6.2 CE\MySQLWorkbench.exe" 
	CurrentDirectory: C:\Program Files\MySQL\MySQL Workbench 6.2 CE
	HasShutdownStarted: False
	OSVersion: Microsoft Windows NT 6.1.7601 Service Pack 1
	SystemDirectory: C:\Windows\system32
	TickCount: 1146420
	UserInteractive: True
	Version: 4.0.30319.18444
	WorkingSet: 33890304
10:57:53 [INF][      Workbench]: Environment variables:
	COMPUTERNAME = UserName-PC
	USERPROFILE = C:\Users\UserName
	HOMEPATH = \Users\UserName
	LOCALAPPDATA = C:\Users\UserName\AppData\Local
	asl.log = Destination=file
	PSModulePath = C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
	PROCESSOR_ARCHITECTURE = AMD64
	Path = C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Dell\DW WLAN Card;C:\Program Files (x86)\Common Files\Roxio Shared\DLLShared\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\MySQL\MySQL Utilities 1.4\;C:\Program Files (x86)\MySQL\MySQL Utilities 1.4\Doctrine extensions for PHP\
	CommonProgramFiles(x86) = C:\Program Files (x86)\Common Files
	ProgramFiles(x86) = C:\Program Files (x86)
	PROCESSOR_LEVEL = 6
	VS120COMNTOOLS = C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\
	LOGONSERVER = \\UserName-PC
	PATHEXT = .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
	HOMEDRIVE = C:
	SystemRoot = C:\Windows
	QTJAVA = C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip
	SESSIONNAME = Console
	ALLUSERSPROFILE = C:\ProgramData
	PUBLIC = C:\Users\Public
	FP_NO_HOST_CHECK = NO
	APPDATA = C:\Users\UserName\AppData\Roaming
	PROCESSOR_REVISION = 2505
	USERNAME = UserName
	CommonProgramW6432 = C:\Program Files\Common Files
	CommonProgramFiles = C:\Program Files\Common Files
	OS = Windows_NT
	PROCESSOR_IDENTIFIER = Intel64 Family 6 Model 37 Stepping 5, GenuineIntel
	ComSpec = C:\Windows\system32\cmd.exe
	SystemDrive = C:
	TEMP = C:\Users\UserN_~1\AppData\Local\Temp
	ProgramFiles = C:\Program Files
	CLASSPATH = .;C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip
	NUMBER_OF_PROCESSORS = 4
	BURN_AUTOPLAY = C:\Program Files (x86)\Roxio\Roxio Burn\
	TMP = C:\Users\UserN_~1\AppData\Local\Temp
	ProgramData = C:\ProgramData
	ProgramW6432 = C:\Program Files
	windir = C:\Windows
	USERDOMAIN = UserName-PC
10:57:53 [INF][      Workbench]: Current version given by meta info is: 6.2.3
10:57:53 [DB1][      Workbench]: Creating single instance setup
10:57:53 [DB2][      Workbench]: Trying to open existing event wait handle
10:57:53 [DB2][      Workbench]: This is the first application instance
10:57:53 [DB2][      Workbench]: Registering IPC channel and instance proxy
10:57:54 [INF][      Workbench]: Setting PATH to: C:\Windows\system32;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Dell\DW WLAN Card;C:\Program Files (x86)\Common Files\Roxio Shared\DLLShared\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\MySQL\MySQL Utilities 1.4\;C:\Program Files (x86)\MySQL\MySQL Utilities 1.4\Doctrine extensions for PHP\
10:57:54 [INF][ mforms managed]: Initializing mforms wrapper
10:57:54 [DB2][ mforms backend]: Initializing mforms factory
10:57:54 [DB1][      WBContext]: Creating WBContext
10:57:54 [DB1][WBContext managed]: Creating WbContext
10:57:54 [DB1][ Managed Notify]: Registered managed observer for GNColorsChanged
10:57:54 [DB1][ Managed Notify]: Registered managed observer for GNFocusChanged
10:57:54 [DB1][ mforms managed]: Creating application wrapper
10:57:54 [DB1][    WBCallbacks]: Creating callbacks wrapper
10:57:54 [INF][   WBContext UI]: Initializing workbench context UI with these values:
	base dir: C:\Program Files\MySQL\MySQL Workbench 6.2 CE
	plugin path: C:\Program Files\MySQL\MySQL Workbench 6.2 CE
	struct path: 
	module path: C:\Program Files\MySQL\MySQL Workbench 6.2 CE/modules
	library path: C:\Program Files\MySQL\MySQL Workbench 6.2 CE
	user data dir: C:\Users\UserName\AppData\Roaming\MySQL\Workbench
	open at start: 
	open type: 
	run at startup: 
	run type: 
	Force SW rendering: No
	Force OpenGL: No
	quit when done: No

How to repeat:
This is the second time within about 3 weeks that MySQL server stopped responding.  The first time, I uninstalled MySQL then reinstalled, and it worked fine.  All my other programs are working fine.  Every night at midnight the Windows Task Scheduler runs "MySQL ManifestUpdate" (C:programfiles(x86)\MySQL\MySQL Installer Windows\MySQLInstallerConsole.exe" Community Update).  It ran last night, and that was the last time MySQL worked.

Any ideas why this is happening?

Thanks,
Dave H
[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