Percona Xtrdb host crashed while running common_schema.duplicate_grantee

Bug #1422348 reported by Jaakko Pesonen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Expired
Undecided
Unassigned
5.5
Expired
Undecided
Unassigned
5.6
Expired
Undecided
Unassigned

Bug Description

MySQL crashed while running on mysql command line tool this (ip addresses changed):

call common_schema.duplicate_grantee('maxscale@192.168.2.%', 'maxscale@192.168.1.%');

MySQL log from the time of the crash as an attachment. Hos name of the node changed from original.

Tags: xtradb
Revision history for this message
Jaakko Pesonen (jaakko-pesonen) wrote :
Revision history for this message
Jaakko Pesonen (jaakko-pesonen) wrote :

And MySQL version as reported by MySQL 5.5.37-35.0-55-log.

Revision history for this message
Muhammad Irfan (muhammad-irfan) wrote :

I am not able to reproduce the problem you described. I tried this on latest Percona Server 5.5/5.6 and Percona XtraDB Cluster 5.6

mysql [localhost] {root} ((none)) > SELECT * FROM common_schema.status\G
*************************** 1. row ***************************
                       project_name: common_schema
                            version: 2.2
                           revision: 523
                       install_time: 2015-03-12 03:38:16
                    install_success: 1
          base_components_installed: 1
 innodb_plugin_components_installed: 1
percona_server_components_installed: 1
              install_mysql_version: 5.5.38-35.2-log
                   install_sql_mode: ONLY_FULL_GROUP_BY,NO_AUTO_VALUE_ON_ZERO,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
1 row in set (0.03 sec)

mysql [localhost] {root} ((none)) > GRANT SELECT ON *.* TO 'irfan'@'192.168.0.%' IDENTIFIED BY 'xxxxxx';
Query OK, 0 rows affected (0.08 sec)

mysql [localhost] {root} ((none)) > call common_schema.duplicate_grantee('irfan@192.168.0.%', 'irfan@localhost');
Query OK, 0 rows affected (0.04 sec)

mysql [localhost] {root} ((none)) > SELECT user,host FROM mysql.user WHERE user='irfan';
+-------+---------------+
| user | host |
+-------+---------------+
| irfan | 192.168.0.% |
| irfan | localhost |
+-------+---------------+

mysql [localhost] {root} ((none)) > SHOW GRANTS FOR 'irfan'@'192.168.0.%';
+-------------------------------------------------------------------------------------------------------------------+
| Grants for irfan@192.168.0.% |
+-------------------------------------------------------------------------------------------------------------------+
| GRANT SELECT ON *.* TO 'irfan'@'192.168.0.%' IDENTIFIED BY PASSWORD '*A0927C41A900C56A5D035EF05ED250A252A5421B' |
+-------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql [localhost] {root} ((none)) > SHOW GRANTS FOR 'irfan'@'localhost';
+---------------------------------------------------------------------------------------------------------------+
| Grants for irfan@localhost |
+---------------------------------------------------------------------------------------------------------------+
| GRANT SELECT ON *.* TO 'irfan'@'localhost' IDENTIFIED BY PASSWORD '*A0927C41A900C56A5D035EF05ED250A252A5421B' |
+---------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

can you please provide output as below:
mysql> SHOW VARIABLES LIKE '%version%';

And my.cnf file from crashed server to check it further.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona Server 5.5 because there has been no activity for 60 days.]

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona Server 5.6 because there has been no activity for 60 days.]

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3264

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.