[MDEV-9791] Installation issue: There is a MySQL server running, but we failed in our attempts to stop it. Created: 2016-03-25 Updated: 2016-04-28 Resolved: 2016-04-28 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Platform Debian |
| Affects Version/s: | 10.1.13 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Gijs van der Velden | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | need_feedback | ||
| Environment: |
Ubuntu 15.10 |
||
| Description |
|
There is a nasty bug when upgrading to the latest MariaDB 10.1.13 server or reinstalling it on Ubuntu 15.10 X64. I think it's an issue with the installation script. The error is:
Obviously the script thinks mysqld is running, but this is not the case since I even completely removed it after running into this error. |
| Comments |
| Comment by Elena Stepanova [ 2016-03-27 ] | |||
|
Hi, What exactly do you run to install MariaDB server – is it apt-get, or dpkg, or anything else, and with which parameters? Please paste the exact command line, and, even better, the full unabridged output till the moment of failure. Please also run dpkg -l | grep -iE 'mysql|maria' and paste its output. | |||
| Comment by Gijs van der Velden [ 2016-03-29 ] | |||
|
I'm using apt-get with the command: sudo apt-get install mariadb-server The output of dpkg -l | grep -iE 'mysql|maria' is: | |||
| Comment by Elena Stepanova [ 2016-03-30 ] | |||
|
Did you try apt-get install -f? If the previous installation crashed in the process, there might have been some inconsistency left.
– what does it say? Also, in order to try to reproduce the problem, I would like to know more about this:
First, what do you mean by MariaDB installation in Galera mode? In 10.1, Galera and regular server are same packages. You could have had a Galera-specific configuration if it was already installed, but since it crashed upon installation, you didn't have a chance to configure it as a Galera mode. So, what was it? Thanks. | |||
| Comment by Gijs van der Velden [ 2016-03-30 ] | |||
|
I've previously tried the -f command but it wouldn't help. The output of those commands is:
I've tried the suggested systemctl daemon-reload (as root), but the output remains the same.
I mean that I had 3 servers in a Galera cluster (I enabled the configuration) when I tried updating this server (from 10.1.12 > 10.1.13) it wouldn't startup again. (Unfortunately I don't have the error message or log from that problem) I decided to try a reinstall to fix it, but it wouldn't install any more. Because it keeps giving the above error message about MySQL running (which it isn't). Looks to me like it's stuck somewhere in a limbo state between being uninstalled and not. I later found out that temporarily removing the gcomm.addresses for the cluster config (effectively disabling the cluster) allowed the other servers to upgrade. Not sure why this was needed, because if I recall correctly, when I upgraded from 10.1.11 > 10.1.12 I didn't make any configuration changes and was able to upgrade without taking the cluster offline. | |||
| Comment by Elena Stepanova [ 2016-03-30 ] | |||
|
Yes, the culprit here is the /etc/init.d/mysql script, which should have been removed when you uninstalled the server, but somehow survived (normally it does not happen, I've checked). Please try to remove it manually and install the server again. | |||
| Comment by Gijs van der Velden [ 2016-03-30 ] | |||
|
Works fine now, thank you for the assistance I did notice a small bug, when setting up the server and using a password that contains the " character there will be an error:
The part ABCDE is the part of the password after the " character, I assume the script has the " character in it when making the SQL query, but hasn't been designed to have passwords that contain it. Hence why it's cut off to early and an error shows. I've seen this bug before, it's reproducible. Should I open a bug report for this one or is it a known issue? | |||
| Comment by Elena Stepanova [ 2016-03-30 ] | |||
|
Please open a bug report about the password issue, I don't remember it being reported before. For the initial problem, it would be useful to find out why it happened, most likely there is a bug in there. | |||
| Comment by Gijs van der Velden [ 2016-03-31 ] | |||
|
I think I ran sudo apt-get remove mariadb-server --purge first. | |||
| Comment by Elena Stepanova [ 2016-03-31 ] | |||
|
Did you have any MySQL installation prior to MariaDB which you were removing? | |||
| Comment by Elena Stepanova [ 2016-04-28 ] | |||
|
Please comment to re-open if you have more information on the issue |