[MCOL-3706] A running mysqld process causes postConfigure to exit prematurely Created: 2020-01-01 Updated: 2020-01-02 Resolved: 2020-01-02 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | installation |
| Affects Version/s: | 1.4.2 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Critical |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Build tested: 1.4.2-1 (Azure build 20191224.6) In this release, ColumnStore engine becomes part of the MariaDB server (Instead of ColumnStore use the server code to build its own distribution package). When server RPM or DEB package is installed, mysqld starts automatically. The running mysqld process causes postConfigure to exit prematurely. A work around is to use the OAM command "mcsadmin shutdownsystem y" to shutdown any ColumnStore processes, including mysqld, before running postConfigure. There are couple options to fix this issue: 1) Add the work around above to the installation instruction |
| Comments |
| Comment by Andrew Hutchings (Inactive) [ 2020-01-02 ] |
|
When the exit happens an error message states that you need to shut down mysqld first. This is intentional. It is due to the need to install things into MariaDB which is not possible on an existing system without starting MariaDB using --skip-grant-tables. postConfigure shutting down MariaDB prematurely would be unexpected behaviour for the user. The only extra thing we could do would be to add a question about shutting down MariaDB (using kill). This would break scripts that throw answers straight into postConfigure. |