| Bug #73211 | dump restore fails on shard_split because password is not used | ||
|---|---|---|---|
| Submitted: | 6 Jul 2014 1:20 | Modified: | 13 Jan 2015 7:52 |
| Reporter: | Fernando Ipar (OCA) | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Fabric | Severity: | S4 (Feature request) |
| Version: | 1.4.3-1 | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[6 Jul 2014 1:24]
Fernando Ipar
If I remove the password for the server user so that shard_split can attempt to load the dump, it fails when it tries to connect to the node once the dump has been loaded:
[vagrant@store fabric]$ mysqlfabric sharding split_shard 1 salaries-3 --split_value=8000
Procedure :
{ uuid = 2ba0821e-df81-4258-8702-40a625face49,
finished = True,
success = False,
return = DatabaseError: ("Cannot connect to the server. Error 1045 (28000): Access denied for user 'fabric'@'store' (using password: YES)", 1045),
activities =
}
[9 Oct 2014 12:21]
Mats Kindahl
Hi Fernando! This is intentional and there are two sections "servers" and "client". The first section is used by Fabric internally when contacting managed servers, and the second section is used when client programs contact the managed servers. I interpret this bug as a feature request to merge the two sections into one and always use that for contacting the managed servers.
[9 Oct 2014 22:06]
Fernando Ipar
Hello Mats, It was a user error on my side then, but I agree that just merging the two sections would improve the tool's usability. Thanks!
Description: Given the same configuration as in report 73210, the following fails: [vagrant@store ~]$ mysqlfabric sharding split_shard 1 salaries-3 --split_value=8000 Procedure : { uuid = 0acc1bb4-8485-4fa6-ad61-7a61430ab2c9, finished = True, success = False, return = BackupError: ('Error while restoring the backup using the mysql client\n, %s', "ERROR 1045 (28000): Access denied for user 'fabric'@'store' (using password: NO)\n"), activities = } How to repeat: Attempt to split a shard in a setup where the mysql user used to connect to servers has a password. In order to make it past the problem reported on 73210, I removed the password from the user on the source server, so that the dump completes, but then the restore fails on the target server.