Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: MySQL Workbench 6.3.9

  1. #1
    Join Date
    Jan 2013
    Location
    Berkshire, UK
    Posts
    51

    Default MySQL Workbench 6.3.9

    I have installed the latest MySQL Workbench from the Tumbleweed repository using Yast. It starts OK, but then I'm prompted to enter a password using the gnome keyring. This doesn't accept either the root, database or user passwords, so prevents connection to MySQL.

    The MySQL Workbench installation instructions on the MySQL website indicates that users with KDE and not Gnome need to manually start the gnome-keystring daemon. I haven't, however, been able to find any such daemon on the system. It doesn't appear in services, even though it shows as being installed on the system in Yast and what I did find in /usr/bin didn't start anything. (I did de-install gnome-keystring and re-install it, but it made no difference.)

    Any suggestions on what needs to be done to get this working will be most appreciated. Thanks.

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,254
    Blog Entries
    2

    Default Re: MySQL Workbench 6.3.9

    How about that...
    For the longest time MySQL workbench was deprecated (given up, not maintained) but it looks like it's enjoying a resuscitation by Oracle.
    The "new" MySQL Workbench looks to have some really cool new features it didn't have before including enhanced data migration tools
    https://www.mysql.com/products/workbench/

    Been a long while since I used it a very long time ago, but IIRC you should enter the MySQL Administrator's password for that database.
    For that to work, of course you need to configure a password and enable remote root login, which isn't done by default. The remote login is required because MySQL Workbench is an "external application" even if it's running on the same machine.

    To configure your MySQL/Mariadb, you should run the security configuration script or if you either want a way to save your security configuration or support a large number of databases, you may want to create a here doc, which is described both specifically and generally in an article I wrote

    https://en.opensuse.org/User:Tsu2/MySQL_and_Mariadb

    HTH,
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  3. #3
    Join Date
    Jan 2013
    Location
    Berkshire, UK
    Posts
    51

    Default Re: MySQL Workbench 6.3.9

    Dear TSU,

    Apologies for the time it's taken to respond. I hadn't realised that anyone had done so - I hadn't selected the email notification option. Thank you also for the information and links regarding the Here documents.

    I have run the mysql_secure_connection script on the command line and have selected 'n' for the disallow remote login option. I have created a new user called 'workbench' with all privileges and have specified any (%) host, but still get the 'unsupported option provided to mysql_options()' message. This is also true if I use 'root'.

    You mention configure a password and enable remote root login in your post. Is this an additional password to the ones I'm using? Is there a way to check what I'm actually sending to the database? The mysqld log doesn't show anything nor does one that I created for general_log.

    I am attempting to connect via Standard TCP/IP to localhost:3306. I usually use a socket connection, but that doesn't work either.

    Any further ideas? Many thanks,

    Malcolm

  4. #4
    Join Date
    Jan 2013
    Location
    Berkshire, UK
    Posts
    51

    Default Re: MySQL Workbench 6.3.9

    Dear TSU,

    Further to my previous post, I have been able to connect remotely to the MySQL database from another computer using the new credentials from the command line, so the remote login aspect is working, but still no success with workbench.

    Best regards,

    Malcolm

  5. #5
    Join Date
    Jan 2013
    Location
    Berkshire, UK
    Posts
    51

    Default Re: MySQL Workbench 6.3.9

    Dear TSU,

    Here's some additional information from the Workbench logfile that may be useful. Though, I suppose one would need to be intimately familiar with the do_connect method to understand why there is an exception.

    "16:21:27 [INF][ WBContext UI]: Initializing workbench context UI with these values:
    base dir: /usr/share/mysql-workbench
    plugin path: /usr/lib64/mysql-workbench/plugins
    struct path: /usr/share/mysql-workbench/grt
    module path: /usr/lib64/mysql-workbench/modules
    library path: /usr/share/mysql-workbench/libraries
    user data dir: /home/mwhite/.mysql/workbench
    open at start:
    open type:
    run at startup:
    run type:
    Force SW rendering: No
    Force OpenGL: No
    quit when done: No
    16:21:27 [INF][ WBContext]: WbContext::init
    16:21:28 [WRN][ grt]: Could not load wb.model.grt.so: Could not open module /usr/lib64/mysql-workbench/modules/wb.model.grt.so (/usr/lib64/mysql-workbench/modules/wb.model.grt.so: undefined symbol: _ZN9Scintilla8WordListD1Ev)
    16:21:30 [INF][ WBA]: Looking for extension modules for WBA...
    16:21:30 [INF][ WBA]: 0 extension modules found
    16:21:30 [WRN][ grt]: Could not load db.mysql.diff.reporting.wbp.so: Could not open module /usr/lib64/mysql-workbench/plugins/db.mysql.diff.reporting.wbp.so (/usr/lib64/mysql-workbench/plugins/db.mysql.diff.reporting.wbp.so: undefined symbol: _Z17build_catalog_mapN3grt3RefI16db_mysql_CatalogEERSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS0_I14GrtNamedObjectEESt4lessIS9_ESaISt4pairIKS9_SB_EEE)
    16:21:30 [WRN][ grt]: /home/mwhite/.mysql/workbench/connections.xml:25: link 'b424bd52-e26e-11e7-a0cb-902b3441ed70' <object GrtObject> key=owner could not be resolved
    16:21:30 [INF][ WBContext]: System info:
    MySQL Workbench Community (GPL) for Linux/Unix version 6.3.10 CE build 12092614 (64 bit)
    Configuration Directory: /home/mwhite/.mysql/workbench
    Data Directory: /usr/share/mysql-workbench
    Cairo Version: 1.15.8
    OS: x86_64
    CPU: 2x Intel(R) Celeron(R) CPU G540 @ 2.50GHz (2494.159MHz) - 3.75GiB RAM
    No video adapter info available
    Distribution: openSUSE Tumbleweed

    Fips mode enabled: no

    16:21:31 [WRN][ WBModule]: OS not found on supported OS list. OS string: ' x86_64'
    16:28:35 [ERR][SQL Editor Form]: SqlEditorForm: exception in do_connect method: Exception: Unsupported option provided to mysql_options()
    16:28:35 [ERR][ GRTDispatcher]: exception in grt execute_task, continuing: Exception: Unsupported option provided to mysql_options()
    16:28:35 [ERR][ GRTDispatcher]: worker: task 'execute sql queries' has failed with error:.Unsupported option provided to mysql_options()
    16:28:35 [ERR][ WQE backend]: Got an exception during connection: Unsupported option provided to mysql_options()
    16:28:35 [ERR][SQL Editor Form]: SQL editor could not be connected: Unsupported option provided to mysql_options()
    16:28:35 [ERR][SQL Editor Form]: Your connection attempt failed for user 'workbench' from your host to server at localhost:3306:
    Unsupported option provided to mysql_options()

    Please:
    1 Check that mysql is running on server localhost
    2 Check that mysql is running on port 3306 (note: 3306 is the default, but this can be changed)
    3 Check the workbench has rights to connect to localhost from your address (mysql rights define what clients can connect to the server and from which machines)
    4 Make sure you are both providing a password if needed and using the correct password for localhost connecting from the host address you're connecting from "

    Best regards,

    Malcolm

  6. #6
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,254
    Blog Entries
    2

    Default Re: MySQL Workbench 6.3.9

    The following in your log may be relevant
    Code:
    16:21:30 [WRN][ grt]: Could not load db.mysql.diff.reporting.wbp.so: Could not open module /usr/lib64/mysql-workbench/plugins/db.mysql.diff.reporting.wbp.so (/usr/lib64/mysql-workbench/plugins/db.mysql.diff.reporting.wbp.so: undefined symbol: 16:21:30 [WRN][ grt]: /home/mwhite/.mysql/workbench/connections.xml:25: link 'b424bd52-e26e-11e7-a0cb-902b3441ed70' <object GrtObject> key=owner could not be resolved
    The first might be a non-critical error related to displaying detailed information,
    The second error is more likely the critical error for why you are unable to connect to your database.

    Suggests you should review your connection settings, if you are properly specifying the database owner.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  7. #7
    Join Date
    Jan 2013
    Location
    Berkshire, UK
    Posts
    51

    Default Re: MySQL Workbench 6.3.9

    Thank you for your response. I shall attempt to resolve the issue with that file.

    When you mention database, do you mean the application or the dbname? I had the impression from the WB connection screen that I could choose my database instance, once I'd connected. Please clarify what you mean by database owner.

    I have assumed that my linux username and password is the one to which the stored key is assigned, especially since I don't receive an error message when I enter that password to unlock the keychain.

    Many thanks,

    Malcolm

  8. #8
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,841
    Blog Entries
    14

    Default Re: MySQL Workbench 6.3.9

    Quote Originally Posted by wishbone42 View Post
    Thank you for your response. I shall attempt to resolve the issue with that file.

    When you mention database, do you mean the application or the dbname? I had the impression from the WB connection screen that I could choose my database instance, once I'd connected. Please clarify what you mean by database owner.

    I have assumed that my linux username and password is the one to which the stored key is assigned, especially since I don't receive an error message when I enter that password to unlock the keychain.

    Many thanks,

    Malcolm
    That could have been a coincedence of you using the same credentials for mysql that you've been using for your linux box. But .... mysql's users aren't the same as your linux users.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  9. #9
    Join Date
    Jan 2013
    Location
    Berkshire, UK
    Posts
    51

    Default Re: MySQL Workbench 6.3.9

    Dear Knurpht,

    The MySQL credentials are not the same as my linux server credentials.

    I have installed MySQL with half a dozen database instances on a local server on a private network. I have, therefore, generally used the MySQL root login for localhost applications. I have now, however, created a new MySQL user account 'workbench' and granted it all privileges, so that it can be used from a remote location. i.e. either from MySQL-Workbench or from somewhere else on the local network. I have checked that these credentials provide access to the database.

    My reference to linux username and password relates to the pop up which appears when I launch MWB and attempt to connect to the localhost database. "Enter password to unlock your login keyring". It appears that the keyring is directly associated with the linux login user, as the entry of anything other than the user account password results in an error.

    This is where it becomes difficult to debug (as a humble user). One enters the database account name 'workbench' and is forced to store the corresponding password in keyring. It's then a matter of pure faith that what gets stored and subsequently sent to the database is in fact correct. How does this relate to the error message "key=owner cannot be resolved"? Who is the owner and of what key? Where does that come from?

    Is anyone able to explain what is supposed to be going on, in words of not too many syllables?

    Many thanks for your help.

    Malcolm

  10. #10
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,254
    Blog Entries
    2

    Default Re: MySQL Workbench 6.3.9

    When you launch Workbench, you may be required to provide elevated credentials (Been a long while since I've used Workbench, and may not be relevant since Workbench appears to be re-written).

    But,
    When you set up a database connection to your database, then that database will have its own "database owner." Typically, I've personally made the database owner the same as the MySQL administrator for convenience(That's the default whenever I create a new database while logged in as the MySQL administrator) and haven't been motivated to explore configuring differently, but for all the other RDBMS I've dealt with the database owner is not the same as the RDBMS administrators.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •