Mysql – Install thesql-shell from apt repository

MySQLmysql-8.0

I want to install and configure a high availability cluster for Mysql 8. To automate that, I want to use use apt repository (via ansible).
My servers are debian jessy (8) distribution.

I succesfully installed mysql server with commands :

> sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 5072E1F5
> echo "deb http://repo.mysql.com/apt/debian jessie mysql-8.0" | \ sudo tee /etc/apt/sources.list.d/mysql80.list
> sudo apt update
> sudo apt install mysql-server

It works fine. Now I want to install Mysql shell to manage a InnoDB cluster. It seems that it is available via apt repository as mentioned in this page :
https://dev.mysql.com/downloads/repo/apt/
And installation is explained here :
https://dev.mysql.com/doc/refman/8.0/en/installing-mysql-shell-linux-quick.html

But when I execute a install via reposiory, I get an error :

> sudo apt-get install mysql-shell

with the message :

Reading package lists… Done Building dependency tree Reading state
information… Done E: Unable to locate package mysql-shell

I have same error with server running on debian stretch (9).

Best Answer

I solved the problem by adding the apt repository mysql-tools : deb http://repo.mysql.com/apt/debian/ stretch mysql-tools

It works for Debian 9 (stretch). Not tested for Debian 8 (jessie).

Related Solutions

Mysql – Can’t log into thesql shell

Please, review my.cnf files (see oficial documentation for file locations https://dev.mysql.com/doc/refman/5.7/en/option-files.html).

Search under the [client] section if exist an entry called socket, i.e:

[client]
port=3306
socket=/tmp/mysql.sock

Replace it with the right path to mysql.sock and try again. To get the mysql.sock, use ps -FU mysql -H | more and get the --socket value

Mysql – new Install and migrate from thesql to mariadb

So, for the after world.

I did it by following my idea and it worked out well.

A few minor things has to be taken into account.

After copying data over from one server to the other.

The *.pem and the auto.cnf files in /var/lib/mysql/ have to be deleted on the new machine. Deleting auto.cnf is really important because it holds the servers ID and you don't wanna end up running several servers with same server ID, what will cause you problems afterwards.

On a fresh installed machine, before installing mariadb, there isn't a user mysql nor group mysql on the system, so change the /var/lib/mysql and it's sub folders to be owned by root:root.

I copied the entire /etc/mysql folder from source machine to destination machine, to make the mariadb install script believe there was a running mysql installation before on that machine. In the config file /etc/mysql/mysql.conf.d/mysql.conf I changed the value of the server_id variable to be unique in the entire server landscape.

After that you are ready to fire the mariadb installation on the new machine using apt. While installing, mariadb install script detects the mysql stuff and tries to run the mysql-upgrade on it. That will probably fail, as in my case, but that's not a big deal.

It is because the install script tries to run mysql-upgrade as root user on your freshly installed mariadb server with old data in place. But there are differences between mysql and mariadb in system tables and in what root on a local machine can do and what not, and system tables needs to be upgraded by the upgrade script.

I never run things as root user on the database, so I have my own user with rights do do everything on each of my databases, and that user credentials come with the data from the old machine. So I run the update script just from the command line using my user credentials instead of the root credentials.

And it turned out to run well, complaining about some missing stuff, but that is what the update script is written for. To detect missing or changed stuff and correct it. Restart mysql and there we are. All my users and 230+GB of data right into access managed now by mariadb on a debian 9 machine.

Hope it helps someone.

Ju

Related Question