MySQL Bugs: #95119: The db service is running, but won't connect to local instance

Bug #95119	The db service is running, but won't connect to local instance
Submitted:	25 Apr 2019 1:41	Modified:	25 May 2019 11:49
Reporter:	Barbara Bonser	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	8.0.15	OS:	Windows (Microsoft Windows 10 Home)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\Jack\AppData\Roaming\MySQL\Workbench\log\wb.log]

At the most inopportune times MYSQL workbench loses connection.  After trying Tools, Start/Stop Server, the db service instance will start, but the local instance won't connect.  

I opened the ports, try to reconfigure the server, but now my password doesn't work for the server.  I wrote it down, referred to it several times, but suddenly it works no more!

How to repeat:
I don't have an answer for this.  It starts sometimes and others it will not.

At times my dbs are missing, others they are they.  I cannot explain it, but all my snippets disappear.  However, today, I can see the snippets are there, but the local server will not connect.

ports are open as directed.

db server instance starts, local instances fails to connect

Attachment: sql_actions_Local_instance_MySQL80.log (application/octet-stream, text), 0 bytes.

snapshot of error codes and MYSQL workbench

Attachment: mysqlerror.PNG (image/png, text), 62.70 KiB.

wb_log file

Attachment: wb.log (application/octet-stream, text), 6.14 KiB.

Thank you for the bug report. I couldn't repeat this issue, please attach the server error log, which server version are you running?, when WorkBench fails to connect are you able to connect with mysql.exe with same user, password and port?.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".