Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Crash When Editing Users

forums forums SQLyog SQLyog: Bugs / Feature Requests Crash When Editing Users

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • #10015
      cgmchris
      Member

      When I navigate to Tools -> User Manager -> Edit user… in version 5.2 Beta 11 SQLyog crashes and creates a dump file. Please see the attached dump file.

    • #22910
      peterlaursen
      Participant

      reproduced ..

      .. but only on serververs where the mysql.user table does not have the correct fields corresponding to the MySQL version.

      Please execute those statements:

      1) SELECT version():

      2) SHOW columns FROM mysql.user;

      and paste the returns in here.

      Am I correct in assuming that you uprgraded the current MySQL version from a previous version. If so you will have to upgrade the mysql.user table by EITHER running the 'mysql_upgrade' program (only available in recent versions) OR executing the 'mysql_fix_privilege_tables.sql' script. Refer to paragraph 2 in the MySQL documentation. For instance: http://dev.mysql.com/doc/refman/5.0/en/upgrade.html

      However SQLyog should not crash, and we will fix in next release of course.

    • #22911
      cgmchris
      Member

      I recently became the admin for this server. I have been informed that the mysql database files themselves were copied into /var/lib/mysql from backups, so if the old server had an older version of mysql that would explain the version change. However, in the last stable release, v5.19, SQLyog does NOT crash. This is a new problem with the beta release only.

      Here is the information you requested:

      SELECT version();

      5.0.16-standard-log

      SHOW columns FROM mysql.user;

      Host char(60) NO PRI

      User char(16) NO PRI

      Password char(16) NO

      Select_priv enum('N','Y') NO N

      Insert_priv enum('N','Y') NO N

      Update_priv enum('N','Y') NO N

      Delete_priv enum('N','Y') NO N

      Create_priv enum('N','Y') NO N

      Drop_priv enum('N','Y') NO N

      Reload_priv enum('N','Y') NO N

      Shutdown_priv enum('N','Y') NO N

      Process_priv enum('N','Y') NO N

      File_priv enum('N','Y') NO N

      Grant_priv enum('N','Y') NO N

      References_priv enum('N','Y') NO N

      Index_priv enum('N','Y') NO N

      Alter_priv enum('N','Y') NO N

    • #22912
      peterlaursen
      Participant

      And this is what it should look like with 5.0.x

      Code:
      SHOW columns FROM mysql.user;

      Field Type Null Key Default Extra
      ——————— ——————————— —— —— ——- ——
      Host char(60) NO PRI
      User char(16) NO PRI
      Password char(41) NO
      Select_priv enum('N','Y') NO N
      Insert_priv enum('N','Y') NO N
      Update_priv enum('N','Y') NO N
      Delete_priv enum('N','Y') NO N
      Create_priv enum('N','Y') NO N
      Drop_priv enum('N','Y') NO N
      Reload_priv enum('N','Y') NO N
      Shutdown_priv enum('N','Y') NO N
      Process_priv enum('N','Y') NO N
      File_priv enum('N','Y') NO N
      Grant_priv enum('N','Y') NO N
      References_priv enum('N','Y') NO N
      Index_priv enum('N','Y') NO N
      Alter_priv enum('N','Y') NO N
      Show_db_priv enum('N','Y') NO N
      Super_priv enum('N','Y') NO N
      Create_tmp_table_priv enum('N','Y') NO N
      Lock_tables_priv enum('N','Y') NO N
      Execute_priv enum('N','Y') NO N
      Repl_slave_priv enum('N','Y') NO N
      Repl_client_priv enum('N','Y') NO N
      Create_view_priv enum('N','Y') NO N
      Show_view_priv enum('N','Y') NO N
      Create_routine_priv enum('N','Y') NO N
      Alter_routine_priv enum('N','Y') NO N
      Create_user_priv enum('N','Y') NO N
      ssl_type enum('','ANY','X509','SPECIFIED') NO
      ssl_cipher blob NO
      x509_issuer blob NO
      x509_subject blob NO
      max_questions int(11) unsigned NO 0
      max_updates int(11) unsigned NO 0
      max_connections int(11) unsigned NO 0
      max_user_connections int(11) unsigned NO 0

      It looks like MySQL 5.0 was installed over 3.23 without following the correct upgrade procedure (executing the 'mysql_fix_privilege_tables.sql' script).

      However in next release SQLyog will not crash, but we cannot guarantee that user management will be possible if the mysql.user table does not have the columns that it should have with the MySQL version.

Viewing 3 reply threads
  • You must be logged in to reply to this topic.