[MCOL-1584] columnstoreBackup/Restore should not default to root user for remote login Created: 2018-07-23 Updated: 2023-10-26 Resolved: 2020-03-30 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 1.1.5 |
| Fix Version/s: | 1.1.7 |
| Type: | Bug | Priority: | Major |
| Reporter: | Ben Thompson (Inactive) | Assignee: | Ben Thompson (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | 2019-02, 2019-03, 2019-04, 2019-05, 2019-06, 2020-1, 2020-2, 2020-3, 2020-4, 2020-5 | ||||||||
| Description |
|
Change the default user to match the current user instead of root |
| Comments |
| Comment by Ben Thompson (Inactive) [ 2018-07-26 ] |
|
In fixing this to not default to root the script should no longer require user to run as root |
| Comment by Ben Thompson (Inactive) [ 2018-10-01 ] |
|
https://github.com/mariadb-corporation/mariadb-columnstore-tools/pull/13 |
| Comment by Andrew Hutchings (Inactive) [ 2018-11-14 ] |
|
This ticket is marked as "IN TESTING" but has no sprint or fixed version. Please update |
| Comment by Daniel Lee (Inactive) [ 2019-04-01 ] |
|
Build tested: 1.1.7-1 With a non-root (user guest) Columnstore installation and a guest user in the backup server, I did ./columnstoreBackup -zv 10.0.0.15 /home/guest/backukp The backup tools no longer output the following and stopped: [2019-04-01 22:24:34] ERROR: This script must be run as root or with sudo But the backup failed because it still try to connect to the ColumnStore using root: tee: /dev/fd/3: Permission denied I tried using the --user and --install-dir parameters and it did work. ./columnstoreBackup -zv --user=guest --install-dir=/home/guest/mariadb/columnstore 10.0.0.15 ~/backup If tried using only the --user parameter and the backup failed because it is still default to the /usr/local/mariadb/columnstore directory [2019-04-01 22:26:14] [guest] ./columnstoreBackup -zv --user=guest 10.0.0.15 /home/guest/backup |
| Comment by Ben Thompson (Inactive) [ 2020-03-30 ] |
|
Closing this as it should be fixed. looking through history. No idea how it ended up "stalled" |