官网安装文档:
https://dev.mysql.com/doc/refman/5.6/en/binary-installation.html
基础环境:
CentOS Linux release 7.1.1503 (Core)
[root@localhost local]# groupadd MysqL
[root@localhost local]# useradd -r -g MysqL -s /bin/false MysqL
[root@localhost local]# cd /usr/local/
[root@localhost local]# tar -zxvf mysql-5.6.37-linux-glibc2.12-x86_64.tar.gz -C /home/software/
软件默认的启动程序中,读取的是/usr/local/中的地址,所以不管在哪里安装,都在/usr/local中建个软链接比较好。
[root@localhost local]# ln -s /home/software/mysql-5.6.37-linux-glibc2.12-x86_64 MysqL
三、添加环境变量
这是临时环境,如果多个窗口同时操作的话,需要都加上这个环境。
[root@localhost MysqL]# export PATH=$PATH:/usr/local/MysqL/bin
[root@localhost local]# cd MysqL
[root@localhost MysqL]# chown -R MysqL:MysqL .
这里全是root也可以的,看自己。
四、安装MysqL
[root@localhost MysqL]# scripts/MysqL_install_db --user=MysqL
Installing MysqL system tables...2017-09-21 09:30:16 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2017-09-21 09:30:16 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap. 2017-09-21 09:30:16 0 [Note] ./bin/MysqLd (MysqLd 5.6.37) starting as process 3271 ... 2017-09-21 09:30:16 3271 [Note] InnoDB: Using atomics to ref count buffer pool pages 2017-09-21 09:30:16 3271 [Note] InnoDB: The InnoDB memory heap is disabled 2017-09-21 09:30:16 3271 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2017-09-21 09:30:16 3271 [Note] InnoDB: Memory barrier is not used 2017-09-21 09:30:16 3271 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-09-21 09:30:16 3271 [Note] InnoDB: Using Linux native AIO 2017-09-21 09:30:16 3271 [Note] InnoDB: Using cpu crc32 instructions 2017-09-21 09:30:16 3271 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2017-09-21 09:30:16 3271 [Note] InnoDB: Completed initialization of buffer pool 2017-09-21 09:30:17 3271 [Note] InnoDB: Highest supported file format is Barracuda. 2017-09-21 09:30:17 3271 [Note] InnoDB: 128 rollback segment(s) are active. 2017-09-21 09:30:17 3271 [Note] InnoDB: Waiting for purge to start 2017-09-21 09:30:17 3271 [Note] InnoDB: 5.6.37 started; log sequence number 1625987 2017-09-21 09:30:17 3271 [Note] binlog end 2017-09-21 09:30:17 3271 [Note] InnoDB: FTS optimize thread exiting. 2017-09-21 09:30:17 3271 [Note] InnoDB: Starting shutdown... 2017-09-21 09:30:18 3271 [Note] InnoDB: Shutdown completed; log sequence number 1625997 OK Filling help tables...2017-09-21 09:30:19 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2017-09-21 09:30:19 0 [Note] Ignoring --secure-file-priv value as server is running with --bootstrap. 2017-09-21 09:30:19 0 [Note] ./bin/MysqLd (MysqLd 5.6.37) starting as process 3294 ... 2017-09-21 09:30:19 3294 [Note] InnoDB: Using atomics to ref count buffer pool pages 2017-09-21 09:30:19 3294 [Note] InnoDB: The InnoDB memory heap is disabled 2017-09-21 09:30:19 3294 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2017-09-21 09:30:19 3294 [Note] InnoDB: Memory barrier is not used 2017-09-21 09:30:19 3294 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-09-21 09:30:19 3294 [Note] InnoDB: Using Linux native AIO 2017-09-21 09:30:19 3294 [Note] InnoDB: Using cpu crc32 instructions 2017-09-21 09:30:19 3294 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2017-09-21 09:30:19 3294 [Note] InnoDB: Completed initialization of buffer pool 2017-09-21 09:30:19 3294 [Note] InnoDB: Highest supported file format is Barracuda. 2017-09-21 09:30:19 3294 [Note] InnoDB: 128 rollback segment(s) are active. 2017-09-21 09:30:19 3294 [Note] InnoDB: Waiting for purge to start 2017-09-21 09:30:19 3294 [Note] InnoDB: 5.6.37 started; log sequence number 1625997 2017-09-21 09:30:19 3294 [Note] binlog end 2017-09-21 09:30:19 3294 [Note] InnoDB: FTS optimize thread exiting. 2017-09-21 09:30:19 3294 [Note] InnoDB: Starting shutdown... 2017-09-21 09:30:21 3294 [Note] InnoDB: Shutdown completed; log sequence number 1626007 OK To start MysqLd at boot time you have to copy support-files/MysqL.server to the right place for your system PLEASE REMEMBER TO SET A PASSWORD FOR THE MysqL root USER ! To do so, start the server, then issue the following commands: ./bin/MysqLadmin -u root password 'new-password' ./bin/MysqLadmin -u root -h qkettle password 'new-password' Alternatively you can run: ./bin/MysqL_secure_installation which will also give you the option of removing the test databases and anonymous user created by default. This is strongly recommended for production servers. See the manual for more instructions. You can start the MysqL daemon with: cd . ; ./bin/MysqLd_safe & You can test the MysqL daemon with MysqL-test-run.pl cd MysqL-test ; perl MysqL-test-run.pl Please report any problems at http://bugs.MysqL.com/ The latest information about MysqL is available on the web at http://www.MysqL.com Support MysqL by buying support/licenses at http://shop.MysqL.com WARNING: Found existing config file ./my.cnf on the system. Because this file might be in use, it was not replaced, but was used in bootstrap (unless you used --defaults-file) and when you later start the server. The new default config file was created as ./my-new.cnf, please compare it with your file and take the changes you need. WARNING: Default config file /etc/my.cnf exists on the system This file will be read by default by the MysqL server If you do not want to use this, either remove it, or use the --defaults-file argument to MysqLd_safe when starting the server |
这里更改了一下用户名qkettle(可忽略)。
[root@qkettle MysqL]# chown -R root .
[root@qkettle MysqL]# chown -R MysqL data
五、复制启动程序:
[root@qkettle MysqL]# cp support-files/MysqL.server /etc/init.d/MysqL.server
在这里,如果/usr/local没有MysqL软链接的话,会报错,说找不到服务的。
六、启动MysqL服务,这里出来个错误:(没出错就直接查看下是否有MysqL进程,继续往下操作就好)
[root@qkettle MysqL]# /etc/init.d/MysqL.server start
Starting MysqL.170921 10:03:14 MysqLd_safe error: log-error set to '/var/log/mariadb/mariadb.log', however file don't exists. Create writable for user 'MysqL'.
ERROR! The server quit without updating PID file (/var/lib/MysqL/qkettle.pid).
解决:
[root@qkettle MysqL]# vim /etc/my.cnf
[MysqLd_safe]
log-error=/var/log/MysqL/mariadb.log
pid-file=/var/run/MysqL/mariadb.pid
再启动:成功
[root@qkettle MysqL]# /etc/init.d/MysqL.server start
Starting MysqL.Logging to '/var/log/MysqL/mariadb.log'.
. SUCCESS!
查看进程
[root@qkettle MysqL]# ps -ef |grep MysqL
root 4998 1 0 10:05 pts/1 00:00:00 /bin/sh /usr/local/MysqL/bin/MysqLd_safe --datadir=/var/lib/MysqL --pid-file=/var/lib/MysqL/qkettle.pid
MysqL 5159 4998 0 10:05 pts/1 00:00:00 /usr/local/MysqL/bin/MysqLd --basedir=/usr/local/MysqL --datadir=/var/lib/MysqL --plugin-dir=/usr/local/MysqL/lib/plugin --user=MysqL --log-error=/var/log/MysqL/mariadb.log --pid-file=/var/lib/MysqL/qkettle.pid --socket=/var/lib/MysqL/MysqL.sock
[root@qkettle MysqL]# ln -s /usr/local/MysqL/bin/MysqL /usr/local/bin/MysqL
这里出错:
[root@qkettle bin]# MysqL
ERROR 2002 (HY000): Can't connect to local MysqL server through socket '/tmp/MysqL.sock' (2)
解决方法:
[root@qkettle bin]# /etc/init.d/MysqL.server stop
Shutting down MysqL.. SUCCESS!
[root@qkettle MysqL]# vim /etc/my.cnf
八、再次启动服务、可以登录了
[root@qkettle bin]# /etc/init.d/MysqL.server start
初始登录
MysqL -u root
MysqL> update user set password=password("123456") where user='root';
MysqL> flush privileges;
MysqL> exit;
查看数据库的字符集情况
MysqL> show variables like 'char%';
MysqL> set character_set_database=utf8;
重启后,字符集并不好用。
character-set-server=utf8
因为我这里只有这么一个MysqLd段落,所以没有再添加别的。
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。