[MCOL-2138] Upgrade failed when .my.cnf exist and no password is setup Created: 2019-02-04 Updated: 2020-08-25 Resolved: 2019-03-06 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | MariaDB Server |
| Affects Version/s: | None |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | Andrew Hutchings (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Environment: |
2pm 2um system |
||
| Issue Links: |
|
||||||||
| Description |
|
Customer was doing a 1.2.2 upgrade install and it failed in postConfigure. MariaDB ColumnStore Database Platform Starting, please wait ........................ TIMEOUT: ProcMon not responding to getSystemStatus FAILED IMPORTANT: There was a system startup failed, once issue has been resolved, rerun postConfigure MariaDB ColumnStore System failed to start, check log files in /var/log/mariadb/columnstore Problem turned out to be that the MariaDB user passsword file of /root/.my.cnf existed on UM1, but the customer didnt have a MariaDB root user password set. They fixed the issue when they deleted/moved the /root/.my.cnf file. And they request that we investigate the issue to see if there needs to be a coding change to handle this setup. Ignore the .my.cnf when the password is configured. |
| Comments |
| Comment by Andrew Hutchings (Inactive) [ 2019-03-06 ] |
|
This is by design with the MariaDB server. We cannot change this behaviour. |