Mysql57

From SME Server
Jump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Softwarecollections.png

Mysql.png

Important.png Note:
Mysql 5.7 support is up to 31 Oct 2023 so 8 months before SME10 EOL which is 30 June 2024.


Description

This contrib purpose is to help configuring mysql57 on SME9 and above using software collection.

This RPM will allow you to have 2 or more (if also using another contrib for another sclo version) versions of MySQL running side by side. You will have to select the one to use in the setup of the specific application - please see "usage" below. Please note that applications and contribs like phpmyadmin etc. will as standard use the original Mysql DBM for your OS unless you change the database connection to Mysql 5.7.

Most of configuration options are explained for mysql here : MySQL are also available for mysql57 ( except innoDB options). Only difference is to prefix mysqld and mysql.init db entry by "mysql57-".

Note that default behaviour will be socket only, and if you enable networking, it will listen on 3309 locally. You then will need to open port to 3309 to access remotely. Also if you want another port you need to define mysql57-mysqld property port to whatever you want. Also remember that default mysql port is reserved to original mysql server


See also for reference: Software_Collections:MySQL

For SME9 Software collection is only available for x64 architectures.

Version

Contrib 10:
Contrib 9:
smeserver-mysql57
The latest version of smeserver-mysql57 is available in the SME repository, click on the version number(s) for more information.


Maintainer

[1]Unnilennium

Installation

yum install smeserver-extrarepositories-centos-sclo -y 
yum install --enablerepo=smecontribs,centos-sclo-rh smeserver-mysql57
source /etc/profile.d/mysql57.sh

and enjoy mysql57, no more commands nor reboot required !

yum install smeserver-extrarepositories-centos-sclo -y 
signal-event yum-modify

Warning.png Warning:
You have to do the signal-event post-upgrade; signal-event reboot; or your mysql57 installation will remain in a definitive failed state. They are MANDATORY.

yum install --enablerepo=smecontribs,centos-sclo-rh smeserver-mysql57
signal-event post-upgrade ;  signal-event reboot


Warning.png Warning:
Again, If you do not issue the previous two commands and try to start the service on your own you will end with a non functional mysql server, failed in the middle of its initialization with no way to return back except by deinstalling it all and manually remove all (absolutely all) created files by the failed initialization

NB : starting from SME 9.2 and smeserver-yum-2.4.0-15.el6.sme.noarch.rpm installed you will be able to install this scl version of mysql57 simply doing the following, without enabling the rh scl repo :

yum install --enablerepo=smecontribs smeserver-mysql57
signal-event post-upgrade ;  signal-event reboot

Usage

By default mysql57 uses a socket for connections.

PHP applications that are aware of sockets are few, and most typically try to connect to a port. You will have to craft a way to define the one you want to use for your particular app. Some let you put it in a variable, some will just need you to add it after the hostname or ip (localhost:3309), some will just assume 3306 and just ignore anything else.

Possible host strings (localhost can be replaced with 127.0.0.1 if needed):

  • localhost:/var/lib/mysql/mysql57.sock
  • localhost;unix_socket=/var/lib/mysql/mysql57.sock

PHP applications that are aware of sockets are few, and most of them will try to connect to a port. To enable mysql57 to use a port you will need to do the following:

config setprop mysql57-mysqld port 3309 LocalNetworkingOnly no
signal-event post-upgrade;signal-event reboot

mysq57 should now be listening on port 3309. you can check this using netstat:

netstat -atn |grep 3309

Beware that some applications just assume the running port number, so to connect to mysql55 on 3307 instead of stock mysql on 3306 you will need to carefully investigate and modify your application accordingly e.g.

  • localhost:3309


Warning.png Warning:
Note that you may experience issues with PHP connecting to the correct port if you use localhost. There is an obscure bug in PHP which means you will need to use 127.0.0.1 instead of localhost. Please see See bug https://bugs.contribs.org/show_bug.cgi?id=10616 for more information


For Wordpress adjust the DB_HOST value in the wp-config.php file accordingly.

define( 'DB_HOST', 'localhost:/var/lib/mysql/mysql57.sock' );

command line

For your convenience, aliases have been added : mysql57, mysqlshow57, mysqladmin57, mysqldump57, mysqlimport57 and mysqlbinlog57

Assuming you have a wordpress database setup, the following will connect to database wordpress in mysql57 server, and present the mysql prompt so you can work with the database.

mysql57 wordpress

However the full command line to access, per instance to mysql55 server with the mysql client against its version would be :

mysql57

Alternatively:

The complete path to the specific version of mysql57 server with the mysql client would be:

# /opt/rh/rh-mysql57/root/usr/bin/mysql  --socket=/var/lib/mysql/mysql57.sock

or use TCP on port 3309:

PHP applications that are aware of sockets are few, and most of them will try to connect to a port. To enable mysql57 to use a port you will need to do the following



# config setprop mysql57-mysqld port 3309 LocalNetworkingOnly no
# config show mysql57-mysqld
# mysql57-mysqld=service
   LocalNetworkingOnly=no
   port=3309
   status=enabled
# signal-event post-upgrade; signal-event reboot
# /opt/rh/mysql57/root/usr/bin/mysql --protocol=TCP --port=3309

Note that using the regular 5.1 client may work, but can lead to unexpected results. Please avoid this type of command invocation:

# mysql  --socket=/var/lib/mysql/mysql57.sock

Resetting the MySQL root password

To reset the password for the MySQL root account. The MySQL root user on SME Server has a random generated password which is generated during installation. You do not need to know this password to login to MySQL with root privileges on SME Server. If you might have changed the MySQL root password you can reset it like this after getting command line access as root user.

#SME9
service mysql57-mysqld stop
expand-template /root/.my.cnf
expand-template /var/service/mysql57-mysqld/set.password
scl enable rh-mysql57 bash
/opt/rh/rh-mysql57/root/usr/libexec/mysqld --socket=/var/lib/mysql/mysql57.sock --bootstrap --user=mysql --skip-grant-tables < /var/service/mysql57-mysqld/set.password
exit
service mysql57-mysqld start
#SME10
systemctl stop mysql57-mysqld
expand-template /root/.my.cnf
expand-template /var/opt/rh/rh-mysql57/lib/misc/set.password
scl enable rh-mysql57 bash
/opt/rh/rh-mysql57/root/usr/libexec/mysqld --socket=/var/lib/mysql/mysql57.sock --bootstrap --user=mysql --skip-grant-tables < /var/opt/rh/rh-mysql57/lib/misc/set.password
exit
systemctl start mysql57-mysqld 

Bugs

Please raise bugs under the SME-Contribs section in bugzilla and select the smeserver-mysql57 component or use this link .


"No open bugs found."

Changelog

Only versions released in smecontrib are listed here:

smeserver-mysql57 Changelog: SME 10 (smecontribs)
2022/03/12 Jean-Philippe Pialasse 2.0.0-15.sme
- fix mysql.init and few other scripts [SME: 11896]
2022/02/24 Jean-Philippe Pialasse 2.0.0-14.sme
- expand phpmyadmin config file on install [SME: 11877]

2022/02/23 Jean-Philippe Pialasse 2.0.0-13.sme
- adapt for SME10 [SME: 11877]

 systemd service files
update event
changing paths
2019/11/21 Jean-Philipe Pialasse 2.0.0-12.sme
- fix reload dump when should not [SME: 10830]
2017/04/03 Jean-Philipe Pialasse 2.0.0-11.sme
- fix pre-backup failure [SME: 10202]