Shulou(Shulou.com)06/01 Report--

This article mainly introduces how SuSE11 installs MySQL5.6.41 through single instance binary, the contents of the article are carefully selected and edited by the author, with a certain pertinence, and is of great significance to everyone's reference, the following is to understand with the author how SuSE11 installs MySQL5.6.41 through single instance binary.

I. Environmental preparation

Operating system: SuSE version 11sp3re64-bit

Kingtry:~ # uname-aLinux kingtry 3.0.76-0.11-default # 1 SMP Fri Jun 14 08:21:43 UTC 2013 (ccab990) x86 "64 x 86" 64 x86 "64 GNU/Linuxkingtry:~ # cat / etc/SuSE-release SUSE Linux Enterprise Server 11 (x86" 64) VERSION = 11PATCHLEVEL = 3

2. Dependent package

Tack-5.6-90.55.x86_64.rpm

Ncurses-devel-5.6-90.55.x86_64.rpm

After installing the above two dependency packages, create a connection file:

Kingtry:~ # ln-s / usr/lib64/libncurses.so / usr/lib64/libtinfo.so.5

Note: if the above connection file is not created, the client will report the following exception message when connecting to the mysql service:

Error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

III. Software preparation

Mysql-5.6.41-linux-glibc2.12-x86_64.tar.gz

IV. Installation process

1. Create groups and users

Kingtry:~ # groupadd mysqlkingtry:~ # useradd-g mysql mysql

2. Create related directories

Kingtry:~ # mkdir-p / data/mysql/ {data,tmp} # create a directory to store data files. There cannot be a space between data and tmp, kingtry:~ # chown-R mysql.mysql / data/mysql

3. Extract the file and modify the name of the decompressed folder

Kingtry:~ # tar-xf mysql-5.6.41-linux-glibc2.12-x86_64.tar.gzkingtry:~ # mv mysql-5.6.41-linux-glibc2.12-x86_64 mysql-5.6.41

4. Configure environment variables

Kingtry:~ # echo 'PATH=/root/mysql-5.6.41/bin:$PATH' > > / etc/profilekingtry:~ # source / etc/profile

5. Initialize the database

Kingtry:~ #. / mysql-5.6.41/scripts/mysql_install_db-basedir=/root/mysql-5.6.41-datadir=/data/mysql/data-user=mysql

Create a configuration file / data/mysql/my.cnf

The reference for my.cnf content is as follows:

# For advice on how to change settings please see# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html [client] # password = your_passwordport = 3306socket = / data/mysql/mysql.sockdefault-character-set=utf8# Here follows entries for some specific programs# The MySQL server [mysqld] port = 3306datadir = / data/mysql/datatmpdir = / data/mysql/tmpsocket = / data/mysql/mysql.sockcharacter-set-server = utf8collation-server = utf8_general_cipid-file = / data/mysql/mysql.piduser = mysql explicit_defaults_for_timestamplower_case_table_names = 1max_connections = 1000back_log = 1024open_files_limit = 10240table_open_cache = 5120 # bind-address = 127.0.0.1 # skip-name-resolveskip-external-lockinglocal-infile = 1 key_buffer_size = 32Mmax_allowed_packet = 1Mtable_open_cache = 64sort_buffer_size = 512Knet_buffer_length = 8Kread_buffer_size = 256Kread_rnd_buffer_size = 512Kmyisam_sort _ buffer_size = 8m # Don't listen on a TCP/IP port at all. This can be a security enhancement # if all processes that need to connect to mysqld run on the same host.# All interaction with mysqld must be made via Unix sockets or named pipes.# Note that using this option without enabling named pipes on Windows# (via the "enable-named-pipe" option) will render mysqld uselessages # # skip-networking # Replication Master Server (default) # binary logging is required for replicationlog-bin = / data/mysql/mysql-bin # binary logging format-mixed recommendedbinlog_format = mixed # required unique id between 1 and 2 ^ 32-floor defaults to 1 if Master-host is not set# but will not function as a master if omittedserver-id = 1 # Replication Slave (comment out master section to use this) # # To configure this host as a replication slave You can choose between# two methods: # # 1) Use the CHANGE MASTER TO command (fully described in our manual)-# the syntax is:## CHANGE MASTER TO MASTER_HOST=, MASTER_PORT=,# MASTER_USER=, MASTER_PASSWORD= # # where you replace, by quoted strings and# by the master's port number (3306 by default). # # Example:## CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,# MASTER_USER='joe', MASTER_PASSWORD='secret';## OR## 2) Set the variables below. However, in case you choose this method, then# start replication for the first time (even unsuccessfully, for example# if you mistyped the password in master-password and the slave fails to# connect), the slave will create a master.info file, and any later# change in this file to the variables' values below will be ignored and# overridden by the content of the master.info file, unless you shutdown# the slave server, delete master.info and restart the slaver server.# For that reason You may want to leave the lines below untouched# (commented) and instead use CHANGE MASTER TO (see above) # # required unique id between 2 and 2 ^ 32-and different from the master) # defaults to 2 if master-host is set# but will not function as a slave if omitted#server-id = 2percent # The replication master for this slave-required#master-host = # # The username the slave will use for authentication when connecting# to the master- required#master-user = # # The password the slave will authenticate with when connecting to# the master- required#master-password = # # The port the master is listening on.# optional-defaults to 3306#master-port = # # binary logging-not required for slaves But recommended#log-bin=mysql-bin # Uncomment the following if you are using InnoDB tables#innodb_data_home_dir = / var/lib/mysqlinnodb_data_file_path = ibdata1:10M:autoextend#innodb_log_group_home_dir = / var/lib/mysql# You can set.. _ buffer_pool_size up to 50-80% # of RAM but beware of setting memory usage too highinnodb_buffer_pool_size = 256M#innodb_additional_mem_pool_size = 2M# Set.. _ log_file _ size to 25% of buffer pool size#innodb_log_file_size = 5M#innodb_log_buffer_size = 8M#innodb_flush_log_at_trx_commit = 1#innodb_lock_wait_timeout = 50innodb_buffer_pool_instances = 2innodb_read_io_threads = 8innodb_write_io_threads = 8innodb_purge_threads = 1 slow_query_log = 1long_query_time = 10log-queries-not-using-indexes log-error = / data/mysql/mysql.err expire-logs- Days = 10 [mysqldump] quickmax_allowed_packet = 512Mnet_buffer_length = 16384 [mysql] auto-rehash# Remove the next comment character if you are not familiar with SQL#safe-updates [myisamchk] key_buffer_size = 20Msort_buffer_size = 20Mread_buffer = 2Mwrite_buffer = 2m [mysqlhotcopy] interactive-timeout

Start the MySQL service

Kingtry:~ # mysqld_safe-defaults-file=/data/mysql/my.cnf-user=mysql &

7. Modification of root password configured after installation

The root password is empty by default, which certainly won't work in a production environment. There are two ways to change the root password, either of which is fine:

1. Command method (Note: the password is changed for the first time, but the password is empty before modification)

Kingtry:~ # mysqladmin-u root password 'root123'

Note that if the root password is no longer empty after performing the above steps, if you want to change the root password again, the above command will not work. You need to use the following command:

Kingtry:~ # mysqladmin-u root-p password 'root1234' Enter password:

This is the current password that you enter interactively. The password parameter is followed by the password you want to change.

The client connects to the MySQL service

Kingtry:~ # mysql-uroot-p-S / data/mysql/mysql.sock

Note: the-S parameter needs to be specified

The firewall allows port 3306.

Kingtry:~ # vi / etc/sysconfig/SuSEfirewall2

Add 3306 ports to FW_SERVICES_EXT_TCP. If there are other ports, spaces are separated, such as:

FW_SERVICES_EXT_TCP= "21 22 3306"

Restart the firewall:

# rcSuSEfirewall2 restart

10. Set up remote access

Log in to mysql CVM first, and authorized root users can log in remotely.

Mysql > grant all PRIVILEGES on *. * to root@'%' identified by 'root123'; Query OK, 0 rows affected (0.00 sec) mysql > flush privileges;Query OK, 0 rows affected (0.00 sec) mysql >

Note: it is best for a production environment to allow root remote access only on machines with a specific IP.

After reading the above about how SuSE11 installs MySQL5.6.41 through single instance binary, many readers must have some understanding. If you need more industry knowledge and information, you can continue to follow our industry information column.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.