UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After the one or the other update the package
mysql-common
has become version 5.8 +1.0.4
The rest like mysql-server and mysql-client are still 5.7.27
Making mysql as a whole dysfunktional.
There are some databases that I would like to keep.
So a new install of mysql is not the desired option.
What is the best way to repair this, anyone an idea?
[edit]
I just restarted mysql with "service mysql restart" and checked with "service mysql status" and the server is running.
I could even start workbench, before workbench crashed with a dependency-problem. This is strange.
[edit]
I just restarted mysql with "service mysql restart" and checked with "service mysql status" and the server is running.
I could even start workbench, before workbench crashed with a dependency-problem. This is strange.
So all is good now?
Please mark your thread SOLVED.
I am trying to figure out how it is possible that packages of 2 mysql versions mix up.
My question is how to get a consistent system again, the way to restart through the console is nice,
but i would like to know if any of us have the same problem, or solved it.
with apt-cache policy mysql-common
I get 5.8
with apt-cache policy mysql-server
I get 5.7
On my 16.04 Kubuntu both have 5.7.
I do not have problems on the 16.04 machine.
Since downgrading (mysql-common) is not an option (loss of databases)
an update to 5.8 for server and client could be a solution but how, when common already says it is 5.8?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.