MySQL Bugs: #68956: Mysql 5.6.10.1 on Windows 8 Pro stops with basic use...

Bug #68956	Mysql 5.6.10.1 on Windows 8 Pro stops with basic use...
Submitted:	14 Apr 2013 19:12	Modified:	24 Jan 2014 15:24
Reporter:	André verwijs	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.6.10.1, 5.6.11	OS:	Windows (Windows 8 pro)
Assigned to:		CPU Architecture:	Any
Tags:	Instance, Mysql 5.6.10.1, windows 8

Description:
Mysql 5.6.10.1 on Windows 8 Pro stops with basic use...

Installation goes fine, only mysql is being installed within a 
subdirectoy, witch is different from what I entered at the beginning
of the installation. 

With workbench 5.2.47

I also added the bin folder to the windows "PATH" string, to make sure
all binarie files can be found. 

the problems start with adding a new user. The Service just stops
and connection is lost to mysql. When I start the servive again and
try again, I'm getting the same. 

I also installed Mysql 5.5.29 with workbench 5.2.45. 
This one works perfectly, no problems with adding a new user.
 

How to repeat:
- install Mysql 5.6.10.1 on windows 8 pro (with all updates installed)
- Try to add new user
- create database and read/write to/from it. 

Suggested fix:
?

Same as Bug# 68955 (you may remove that one)
This is the correct one..

UPDATE: mysqldump also gives error
"mysqldump: unknown option '--no-beep'"

witch I didn't set as parameter. 

I use:

mysqldump --lock-tables=FALSE --add-locks=FALSE --flush-privileges=FALSE --disable-keys=FALSE --compress=TRUE --quote-names=TRUE --triggers=TRUE --default-character-set=utf8 --comments --max_allowed_packet=1G --host=localhost --user=root --password=AndreVerwijs --complete-insert=TRUE --create-options=TRUE --events --extended-insert=TRUE --port=3306 --single-transaction=TRUE --databases "standalone" "mysql" > C:\Users\André\Downloads\OPENSIM_config_local_latest_trunk\Backups\standalone-new.sql

its a lot but ideal for big databases...

André

Thank you for the report.

Which user do you add? MySQL's user or Windows user?

Please also send us full MySQL error log file and Windows Event viewer log for MySQL service.

Regarding to --no-beep error this is, most likely, not a bug, but options, specified in your my.ini file.

thank you for replying..

a bit of a disaster, my cable modem died two day ago, 
I'm getting a new one on thirsty.  

but i will try to collect all log files concerning MYSQL
and post them here. 

thanks for the tip with mysqldump error, I will check this. 

André

thank you for replying..

a bit of a disaster, my cable modem died two day ago, 
I'm getting a new one on thirsty.  

but i will try to collect all log files concerning MYSQL
and post them here. 

thanks for the tip with mysqldump error, I will check this. 
I added a mysql user for "opensimulator(.org)" 

André

Thank you for the update.

We will wait log files from you.

mysql-crash_bug-68956.rtf

Attachment: mysql-crash_bug-68956.rtf (text/richtext), 2.15 KiB.

I think i found why MySQL Instance is crashing.  

When i try to add a user WITHOUT setting administrative rols first, MySQL Instance is crashing.
I've set the service on autostart on crash, so it does restart again...  

see here:
~~~~~~~~~~

WMI LOG

Naam van toepassing met fout: mysqld.exe, versie: 5.6.10.0, tijdstempel: 0x510bcc9d
Naam van module met fout: mysqld.exe, versie: 5.6.10.0, tijdstempel: 0x510bcc9d
Uitzonderingscode: 0xc0000005
Foutmarge: 0x00000000000c9161
Id van proces met fout: 0x5c4
Starttijd van toepassing met fout: 0x01ce3d6866d91cc2
Pad naar toepassing met fout: C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe
Pad naar module met fout: C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe
Rapport-id: 0551605e-a95d-11e2-be6c-c860006e412e
Volledige pakketnaam met fout: 
Relatieve toepassings-id van pakket met fout: 

Name of application with error: mysqld.exe, version 5.6.10.0, time stamp: 0x510bcc9d
Name of module with error: mysqld.exe, version 5.6.10.0, time stamp: 0x510bcc9d
Exception code: 0xc0000005
Margin of error: 0x00000000000c9161
Id process with error: 0x5c4
Start time of application with error: 0x01ce3d6866d91cc2
Path to application with error: C: \ Program Files \ MySQL \ MySQL Server 5.6 \ bin \ mysqld.exe
Path to module with error: C: \ Program Files \ MySQL \ MySQL Server 5.6 \ bin \ mysqld.exe
Report Id: 0551605e-11e2-a95d-be6c-c860006e412e
Full package name with error:
Relative application ID of package with error:

workbench log

03:53:04 [WRN][wb_admin_control.pyc]: Error executing SQL CREATE USER 'newuser'@'localhost' IDENTIFIED BY 'newuser': Error executing 'CREATE USER 'newuser'@'localhost' IDENTIFIED BY 'newuser''
Lost connection to MySQL server during query.
SQL Error: 2013
03:53:04 [WRN][wb_admin_control.pyc]: exec_sql: Loss of connection to mysql server was detected.
03:53:04 [WRN][wb_admin_control.pyc]: Error is recoverable. Reconnecting to MySQL server.

(also added a file with same log output) 

i guess i'm not allowed to skip that step.... 

André

Are you trying to startup 5.6.10 with a datadir imported from 5.5?
That will lead to crashes when managing users, due to a missing column " password_expired" in the mysql.user table, http://bugs.mysql.com/bug.php?id=68385

no, but i'm using MySQL Workbench 5.2.47 and this is totally not compatible with Mysql 5.6.10.1 especially with mysqldump.

Please clarify some doubts I have: 1.- What kind of install you did with 5.6.10 upgrade or full fresh install. 2.- If upgrade which was the older version?. 3.- Using the task manager are you able to check if the service is running?. Thanks.

full fresh install, but it doesn't matter how you install, with adding new mysql user, if you don't set administrative roles first, the MYSQL56 service will crash.

Andre, we need the mysql server error log.

I couldn't repeat with 5.6.11 on Windows 8 following your instructions (add new user without administrative roles). Please try 5.11.6. Thanks.

I've added all log files i could find (mysql and workbench) and also log from windows error logs about mysql.

not sure if they tell you much...
also look at image, this is a warning i got with the instance crash.
http://is.gd/GqzAqV 

- added file: Bug_68956-Mysql.zip

Bug_68956-Mysql

Attachment: Bug_68956-Mysql.zip (application/zip, text), 7.33 KiB.

Thank you for the feedback.

Please send us output of SHOW CREATE TABLE mysql.user

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".