Ask Your Question
0

mariadb wont start after dnf update

asked 2018-01-25 02:54:37 -0600

ceres2009 gravatar image

updated 2018-01-25 02:57:33 -0600

i have a mariadb for owncloud installed on a F26 server. After yesterdays dnf update mariadb wont start with following log:

mariadb.service: Failed with result 'protocol'. Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.

Jan 25 09:28:27 oc.server.com systemd[1]: Starting MariaDB 10.1 database server...
Jan 25 09:28:27 oc.server.com mysql-check-socket[3547]: Socket file /var/lib/mysql/mysql.sock exists.
Jan 25 09:28:27 oc.server.com mysql-check-socket[3547]: No process is using /var/lib/mysql/mysql.sock, which means it is a garbage, so it will be removed automatically.
Jan 25 09:28:27 oc.server.com mysql-prepare-db-dir[3570]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Jan 25 09:28:27 oc.server.com mysql-prepare-db-dir[3570]: If this is not the case, make sure the /var/lib/mysql is empty before running mysql-prepare-db-dir.
Jan 25 09:28:28 oc.server.com mysqld[3605]: 2018-01-25  9:28:28 139930537759936 [Note] /usr/libexec/mysqld (mysqld 10.1.30-MariaDB) starting as process 3605 ...
Jan 25 09:28:28 oc.server.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jan 25 09:28:28 oc.server.com systemd[1]: Failed to start MariaDB 10.1 database server.
Jan 25 09:28:28 oc.server.com systemd[1]: mariadb.service: Unit entered failed state.
Jan 25 09:28:28 oc.server.com systemd[1]: mariadb.service: Failed with result 'exit-code'.

From the error messages it looks exactly like https://bugzilla.redhat.com/show_bug.... but that bug is for F27 only.

I tried backing up /var/lib/mysql and emptying it => same error

I tried changing SELinux, as suggested in the comments.=> same error

I tried reverting the update with dnf => this fails because it couldn't find a package?!

No package GeoIP-GeoLite-data-0:2017.10-1.fc26.noarch available.
Error: An operation cannot be undone

I tried reinstalling mariadb => same error

I'm out of ideas. Anybody has an hint how to get it running again?

edit retag flag offensive close merge delete

Comments

If it broke after an update, please fill a bug into bugzilla. https://bugzilla.redhat.com . Package maintainers are rarely reading it here.

Petr Menšík gravatar imagePetr Menšík ( 2018-01-29 09:27:11 -0600 )edit

5 Answers

Sort by » oldest newest most voted
0

answered 2018-01-25 17:02:08 -0600

wigoe gravatar image

I bitterly complain to Maridb on this very same issue. Spent all day getting nowhere. Guy asked me for $5-7k for a solution. What a load of nonsense.

Right now I have 38 GB of data in tables. Totally unusable. Now researching on using postsql.

edit flag offensive delete link more

Comments

Learn how to efficiently use MariaDB before you switch to another database. It will not help you changing to posgresql unless you know, what are advantages to it. If you have done it wrong with MariaDB without learning what went wrong, you would make it wrong with Postgresql as well.

Petr Menšík gravatar imagePetr Menšík ( 2018-01-29 09:25:08 -0600 )edit
0

answered 2018-01-27 21:13:40 -0600

RVTim gravatar image

Hey thanks! Glad I ran across this so quickly in my google search. Just did updates tonight...3 days after original poster, and my Mariadb didn't start either. Same fix.

edit flag offensive delete link more
0

answered 2018-01-27 11:48:05 -0600

c3iq gravatar image

updated 2018-01-28 05:23:39 -0600

I was surprised by this too. This seems to have been missed:

mkdir /run/mariadb
chown mysql /run/mariadb
edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2018-01-25 02:54:37 -0600

Seen: 951 times

Last updated: Jan 28 '18