[MCOL-1014] Replication setup failed when using ssh key and schema sync enabled Created: 2017-11-06  Updated: 2017-11-09  Resolved: 2017-11-09

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 1.1.1
Fix Version/s: 1.1.2

Type: Bug Priority: Critical
Reporter: Daniel Lee (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2017-22

 Description   

Build tested: 1.1.1-1 CS

I am tried to install a 1um2pm stack using ovh physical servers. When postConfigure prompted about "ColumnStore Schema Sync", I answered with y. postConfigure failed with replication setup. The servers used have ssh key setup between pm1 and other nodes.

[root@cs-tst-03 tmp]# cat master-dist_pm1.log
rsync -vopgr -e ssh --exclude=mysql/ --exclude=test/ --exclude=infinidb_vtable/ --exclude=infinidb_querystats/ --exclude=calpontsys/ --include=/ --include=/* --exclude=* /usr/local/mariadb/columnstore/mysql/db/ root@192.99.232.190:/usr/local/mariadb/columnstore/mysql/db/
<ot@192.99.232.190:/usr/local/mariadb/columnstore/mysql/db/
root@192.99.232.190's password:
Permission denied, please try again.
root@192.99.232.190's password: FAILED: Invalid password

 Comments   
Comment by Ben Thompson (Inactive) [ 2017-11-07 ]

Reviewed and Merged

Comment by David Hill (Inactive) [ 2017-11-07 ]

To test:
on um1/pm2 system without local query, make sure it installs complete and from the um log files, it doesn't do anything toward setting up pm1 and pm2 related to mysql replication.

Comment by Daniel Lee (Inactive) [ 2017-11-08 ]

Build verified: 1.1.2 Git source
/root/columnstore/mariadb-columnstore-server
commit ed21e674cfd70db421957d0212ff7fc1835d06d5
Author: david hill <david.hill@mariadb.com>
Date: Mon Nov 6 08:41:53 2017 -0600
Update README.md
updated version
/root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
commit 1603ce925f4cbffef8754663ae0a3058bafc4c65
Author: david hill <david.hill@mariadb.com>
Date: Wed Nov 8 13:06:45 2017 -0600
rechecking back in version of calpontsystemcatalog, accidental commit old versions

Tested with a 1um4pm configuration

Installation worked for non-localquery, but failed for localquery.

[root@cs-tst-05 tmp]# cat master-dist_pm1.log
rsync -vopgr -e ssh --exclude=mysql/ --exclude=test/ --exclude=infinidb_vtable/ --exclude=infinidb_querystats/ --exclude=calpontsys/ --include=/ --include=/* --exclude=* /usr/local/mariadb/columnstore/mysql/db/ root@192.99.232.190:/usr/local/mariadb/columnstore/mysql/db/
<ot@192.99.232.190:/usr/local/mariadb/columnstore/mysql/db/
root@192.99.232.190's password:
Permission denied, please try again.
root@192.99.232.190's password: FAILED: Invalid password
[root@cs-tst-05 tmp]#

Comment by David Hill (Inactive) [ 2017-11-09 ]

I was able to do a 1um / 2pm install with local query setup correct, I have my pms as slaves.

I then did a 1um / 2pm with mysql rep enabled and no local query, and no messages were sent to the pms for replication setup, so the bug fix work in my testing again..

Comment by David Hill (Inactive) [ 2017-11-09 ]

This test case needs ssh-keys setup on the um because rsync is done from um to other nodes, so there is a need to have ssh-keys on um1.

https://mariadb.com/kb/en/library/preparing-for-columnstore-installation-11x/#system-administration-information

Comment by David Hill (Inactive) [ 2017-11-09 ]

test by Dh Hill, requires ssh keys be setup from um1

Generated at Thu Feb 08 02:25:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.