Bug #96212 Mismatch Version on Mysql 8 Ubuntu
Submitted: 16 Jul 2019 4:53 Modified: 17 Aug 2019 12:34
Reporter: Ryan Winata Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0.16 OS:Ubuntu
Assigned to: CPU Architecture:x86
Tags: mismatch

[16 Jul 2019 4:53] Ryan Winata
Description:
I tried to export a tables from mysql server which runs on mysql version 8++.
Previously i was at Mysql 5 which can export but its says warning that some commands would probably wont imported or something like that . Then i update to 8 now I cant export at all . This was produced because I updated to 8 when i check Log its says like this.

get_mysqldump_version:117]: Could not parse version number from /usr/bin/mysqldump:
mysqldump  Ver 8.0.16 for Linux on x86_64 (MySQL Community Server - GPL)

when i check mysql -v and mysqldump -v its says like this 

mysqldump -V
mysqldump  Ver 8.0.16 for Linux on x86_64 (MySQL Community Server - GPL)

mysql -V
mysql  Ver 8.0.16 for Linux on x86_64 (MySQL Community Server - GPL)

This is mysqldump tools path /usr/bin/mysqldump
This is mysql tool paths : mysql
and Export Directory Path : ~/dumps

How to repeat:
Having a Mysql version of 8 and tried to export from other database in my server
[16 Jul 2019 4:55] Ryan Winata
Forgot to mention this

11:48:46 [ERR][wb_admin_control.py:server_polling_thread:578]: Error in monitoring thread: Traceback (most recent call last):
  File "/usr/lib/mysql-workbench/modules/wb_admin_control.py", line 570, in server_polling_thread
    result = self.poll_connection.executeQuery("SHOW GLOBAL STATUS")
  File "/usr/share/mysql-workbench/libraries/workbench/db_utils.py", line 341, in executeQuery
    raise QueryError("Error executing '%s'\n%s"%(query, error), code, error)
QueryError: Error executing 'SHOW GLOBAL STATUS'
Lost connection to MySQL server during query.
SQL Error: 2013

11:48:46 [INF][wb_admin_control.py:server_polling_thread:580]: Monitoring thread done.
11:54:22 [ERR][wb_admin_export.py:get_mysqldump_version:117]: Could not parse version number from /usr/bin/mysqldump:
mysqldump  Ver 8.0.16 for Linux on x86_64 (MySQL Community Server - GPL)
[17 Jul 2019 6:54] Terje Røsten
This seems like a MySQL Workbench problem.
[17 Jul 2019 10:27] MySQL Verification Team
Hello Ryan Winata!

Thank you for the report.
Could you please provide unaltered workbench log, screenshot of "Administration Preferences" from preferences,  Ubuntu version details to investigate this issue at our end? Thank you.

To locate Wb log file, please see https://dev.mysql.com/doc/workbench/en/wb-configuring-files.html

To navigate to Administration Preferences , please see- https://dev.mysql.com/doc/workbench/en/wb-preferences-administration.html

regards,
Umesh
[17 Jul 2019 10:53] Ryan Winata
Here's the preference from workbench administration

Attachment: Screenshot from 2019-07-17 17-52-10.png (image/png, text), 52.52 KiB.

[17 Jul 2019 10:53] Ryan Winata
Dear Umesh Shastry Thankyou for the reply 

here is the wb.log

13:20:28 [INF][      WBContext]: Parsing application arguments.
13:20:28 [INF][      WBContext]:     /usr/lib/mysql-workbench/mysql-workbench-bin
13:20:28 [INF][   WBContext UI]: Initializing workbench context UI with these values:
	base dir: /usr/share/mysql-workbench
	plugin path: /usr/lib/mysql-workbench/plugins
	struct path: /usr/share/mysql-workbench/grt
	module path: /usr/lib/mysql-workbench/modules
	library path: /usr/share/mysql-workbench/libraries
	user data dir: /home/ryukyu/.mysql/workbench
	open at start: 
	open type: 
	run at startup: 
	run type: 
	Force SW rendering: No
	Force OpenGL: No
	quit when done: No
13:20:28 [INF][      WBContext]: WbContext::init
13:20:33 [INF][            WBA]: Looking for extension modules for WBA...
13:20:33 [INF][            WBA]: 0 extension modules found
13:20:33 [WRN][            grt]: /usr/share/mysql-workbench/data/table_templates.xml:21: link 'com.mysql.rdbms.mysql.datatype.timestamp' <object db.SimpleDatatype> key=simpleType could not be resolved
13:20:33 [WRN][            grt]: /usr/share/mysql-workbench/data/table_templates.xml:106: link 'com.mysql.rdbms.mysql.datatype.varchar' <object db.SimpleDatatype> key=simpleType could not be resolved
13:20:33 [WRN][            grt]: /usr/share/mysql-workbench/data/table_templates.xml:229: link 'com.mysql.rdbms.mysql.datatype.int' <object db.SimpleDatatype> key=simpleType could not be resolved
13:20:34 [WRN][            grt]: /home/ryukyu/.mysql/workbench/connections.xml:26: link 'b226d4bd-a83e-11e9-8132-302432fc4d6a' <object GrtObject> key=owner could not be resolved
13:20:34 [INF][      WBContext]: System info:
 	MySQL Workbench Community (GPL) for Linux/Unix version 6.3.8 CE build 1228 (64 bit)
	Configuration Directory: /home/ryukyu/.mysql/workbench
	Data Directory: /usr/share/mysql-workbench
	Cairo Version: 1.15.10
	OS: Linux 5.1.6-050106-generic
	CPU: 8x Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz (1071.365MHz) - 7.65GiB RAM
	Distribution: Ubuntu 18.04.2 LTS

	Fips mode enabled: no

13:20:36 [INF][      SqlEditor]: Opened connection 'Local instance 3306' to MySQL Community Server - GPL version 8.0.16
13:20:37 [INF][     AutoCCache]: Initializing autocompletion cache for Local_instance_3306
13:20:40 [ERR][SqlEditorSchemaTree]: Exception querying metadata from mysql.proc, will fallback to SHOW PROCEDURE: Exception: Table 'mysql.proc' doesn't exist
13:20:42 [ERR][     AutoCCache]: Exception while running refresh task: View 'tokdis_trx.view_order_summaries' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[17 Jul 2019 12:34] MySQL Verification Team
I see you are currently using "MySQL Workbench Community (GPL) for Linux/Unix version 6.3.8 CE build 1228 (64 bit)" - Please upgrade MySQL Workbench to MySQL Workbench 8.0.16 and let us know if you are still experiencing this issue. Thank you!

regards,
Umesh
[18 Aug 2019 1:00] Bugs System
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".