Linux下安装mysql-5.6.12-linux-glibc2.5-x86_64.tar.gz

 更新时间:2016年09月07日 11:43:38   投稿:mrr  
这篇文章主要介绍了Linux下安装mysql-5.6.12-linux-glibc2.5-x86_64.tar.gz的相关资料,非常不错,具有参考借鉴价值,需要的朋友可以参考下

从官网下载mysql-5.6.12-linux-glibc2.5-x86_64.tar.gz

创建mysql用户

[root@Master home]# useradd mysql
[root@Master data]# echo 'mysql'|passwd --stdin mysql

更改用户 mysql 的密码 。

passwd: 所有的身份验证令牌已经成功更新。

创建mysql用户的原因

不用mysql用户会出现一下错误,尝试了很多次,添加mysql用户安装成功

*当然很多时候我们已经创建好别的用户,来完成日常的操作如果不创建mysql用户,修改mysql/bin目录下的mysqld_safe文件; //亲测成功

具体步骤:

[root@Master bin]# vim mysqld_safe
user='mysql' 修改为 user='hadoop' //自己的用户 后边步骤基本相同*
[root@Slave1 data]# service mysql start
Starting MySQL...... ERROR! The server quit without updating PID file (/home/hadoop/ruanJian/mysql/data/Slave1.Hadoop.pid).
[root@Master data]#vim Slave1.Hadoop.err //查看日志文件
160830 15:56:44 mysqld_safe Starting mysqld daemon with databases from /home/hadoop/ruanJian/mysql/data
2016-08-30 15:56:49 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-08-30 15:56:49 1990 [ERROR] Fatal error: Can't change to run as user 'mysql' ; Please check that the user exists!
2016-08-30 15:56:49 1990 [ERROR] Aborting
2016-08-30 15:56:49 1990 [Note] Binlog end
2016-08-30 15:56:49 1990 [Note] /home/hadoop/ruanJian/mysql/bin/mysqld: Shutdown complete
160830 15:56:49 mysqld_safe mysqld from pid file /home/hadoop/ruanJian/mysql/data/Slave1.Hadoop.pid ended

在mysql用户下创建data目录并解压

[root@Master data]# tar -zxvf mysql-5.6.12-linux-glibc2.5-x86_64.tar.gz
[root@Master data]# mv mysql-5.6.12-linux-glibc2.5-x86_64 mysql //重命名

设置权限

[root@Master data]# chown -R mysql:mysql mysql

切换用户并进入mysql/scripts 目录

[root@Master data]# su mysql
[mysql@Master data]$ cd mysql/scripts/
[mysql@Master scripts]$

安装(目录根据自己的mysql解压目录自行设置)

[mysql@Master scripts]$ ./mysql_install_db --user=mysql --basedir=/home/mysql/data/mysql --datadir=/home/mysql/data/mysql/data

输出信息

Installing MySQL system tables...2016-08-30 19:55:41 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-08-30 19:55:42 1354 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
2016-08-30 19:55:42 1354 [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)
2016-08-30 19:55:42 1354 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-30 19:55:42 1354 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-30 19:55:42 1354 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-08-30 19:55:42 1354 [Note] InnoDB: Using Linux native AIO
2016-08-30 19:55:42 1354 [Note] InnoDB: Not using CPU crc32 instructions
2016-08-30 19:55:42 1354 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-08-30 19:55:42 1354 [Note] InnoDB: Completed initialization of buffer pool
2016-08-30 19:55:42 1354 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2016-08-30 19:55:42 1354 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2016-08-30 19:55:42 1354 [Note] InnoDB: Database physically writes the file full: wait...
2016-08-30 19:55:42 1354 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2016-08-30 19:55:43 1354 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2016-08-30 19:55:44 1354 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2016-08-30 19:55:44 1354 [Warning] InnoDB: New log files created, LSN=45781
2016-08-30 19:55:44 1354 [Note] InnoDB: Doublewrite buffer not found: creating new
2016-08-30 19:55:44 1354 [Note] InnoDB: Doublewrite buffer created
2016-08-30 19:55:44 1354 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-30 19:55:44 1354 [Warning] InnoDB: Creating foreign key constraint system tables.
2016-08-30 19:55:44 1354 [Note] InnoDB: Foreign key constraint system tables created
2016-08-30 19:55:44 1354 [Note] InnoDB: Creating tablespace and datafile system tables.
2016-08-30 19:55:44 1354 [Note] InnoDB: Tablespace and datafile system tables created.
2016-08-30 19:55:44 1354 [Note] InnoDB: Waiting for purge to start
2016-08-30 19:55:44 1354 [Note] InnoDB: 5.6.12 started; log sequence number 0
2016-08-30 19:55:44 1354 [Note] Binlog end
2016-08-30 19:55:44 1354 [Note] InnoDB: FTS optimize thread exiting.
2016-08-30 19:55:44 1354 [Note] InnoDB: Starting shutdown...
2016-08-30 19:55:46 1354 [Note] InnoDB: Shutdown completed; log sequence number 1625977
OK
Filling help tables...2016-08-30 19:55:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-08-30 19:55:46 1377 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
2016-08-30 19:55:46 1377 [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)
2016-08-30 19:55:46 1377 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-30 19:55:46 1377 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-30 19:55:46 1377 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-08-30 19:55:46 1377 [Note] InnoDB: Using Linux native AIO
2016-08-30 19:55:46 1377 [Note] InnoDB: Not using CPU crc32 instructions
2016-08-30 19:55:46 1377 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-08-30 19:55:46 1377 [Note] InnoDB: Completed initialization of buffer pool
2016-08-30 19:55:46 1377 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-30 19:55:46 1377 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-30 19:55:46 1377 [Note] InnoDB: Waiting for purge to start
2016-08-30 19:55:46 1377 [Note] InnoDB: 5.6.12 started; log sequence number 1625977
2016-08-30 19:55:46 1377 [Note] Binlog end
2016-08-30 19:55:46 1377 [Note] InnoDB: FTS optimize thread exiting.
2016-08-30 19:55:46 1377 [Note] InnoDB: Starting shutdown...
2016-08-30 19:55:48 1377 [Note] InnoDB: Shutdown completed; log sequence number 1625987
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:

/home/mysql/data/mysql/bin/mysqladmin -u root password 'new-password'
/home/mysql/data/mysql/bin/mysqladmin -u root -h Master.Hadoop password 'new-password'

Alternatively you can run:

/home/mysql/data/mysql/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 . ; /home/mysql/data/mysql/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 with the ./bin/mysqlbug script!
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
New default config file was created as /home/mysql/data/mysql/my.cnf and
will be used by default by the server when you start it.
You may edit this file to change server settings
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

配置文件

[mysql@Master scripts]$ cd ../support-files/
[root@Master support-files]# cp my-default.cnf /etc/my.cnf
[root@Master support-files]# cp mysql.server /etc/init.d/mysql
[root@Master support-files]# vim /etc/init.d/mysql //修改mysql文件

添加以下两行

basedir=/home/mysql/data/mysql
datadir=/home/mysql/data/mysql/data

配置环境变量

[root@Master support-files]# vim /etc/profile
#set mysql environment
export MYSQL_HOME=/home/mysql/data/mysql
export PATH=$MYSQL_HOME/bin:$PATH

配置mysql服务开机自动启动

[root@Master bin]# chkconfig --add mysql //添加mysql
[root@Master bin]# chkconfig mysql on //设置开机启动

启动mysql

[root@Master support-files]# service mysql start
env: /etc/init.d/mysql: 权限不够 //如果出现这个提示 执行以下命令重新启动
[root@Master support-files]# chmod a+wrx /etc/init.d/mysql
[root@Master support-files]# service mysql start
Starting MySQL.. SUCCESS! //启动成功

设置root登录密码

[root@Master ~]# cd /home/mysql/data/mysql/bin/ //进去mysql的bin目录
[root@Master bin]# ./mysqladmin -u root password 'password' //'password' 为自己设置的密码引号非必须
[root@Master bin]# ./mysqladmin -u root password mysql
[root@Master bin]# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 4
Server version: 5.6.12 MySQL Community Server (GPL)
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql>

以上所述是小编给大家介绍的Linux下安装mysql-5.6.12-linux-glibc2.5-x86_64.tar.gz,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对脚本之家网站的支持!

相关文章

  • 详解Mysql中的视图

    详解Mysql中的视图

    mysql中的视图,视图与表有很多相似的地方,视图也是由若干个字段以及若干条记录构成,视图也可以作为select语句的数据源
    2017-04-04
  • mysql启用skip-name-resolve模式时出现Warning的处理办法

    mysql启用skip-name-resolve模式时出现Warning的处理办法

    在优化MYSQL配置时,加入 skip-name-resolve ,在重新启动MYSQL时检查启动日志,发现有警告信息
    2012-07-07
  • MySQL中批量删除指定前缀表的sql语句

    MySQL中批量删除指定前缀表的sql语句

    有时候我们在安装一些cms的时候,这些cms都是带表前缀的方便区分数据,但有时候我们测试完需要删除的时候又有别的前缀表就可以参考下面的方法
    2013-06-06
  • 安装mysql noinstall zip版

    安装mysql noinstall zip版

    没用过mysql, 这几天折腾django ,发现连接mssql好像还是有些小bug,为了防止日后项目有些莫名的db故障,故选择django推荐之一的mysql
    2011-12-12
  • MySQL配置文件my.cnf参数优化和中文详解

    MySQL配置文件my.cnf参数优化和中文详解

    这篇文章主要介绍了MySQL配置文件my.cnf参数优化和中文详解,非常详细的用中文注释了各个参数的作用以及建议值,需要的朋友可以参考下
    2014-03-03
  • 教你如何恢复使用MEB备份的MySQL数据库

    教你如何恢复使用MEB备份的MySQL数据库

    这篇文章主要介绍了教你如何恢复使用MEB备份的MySQL数据库的具体方法,需要的朋友可以参考下
    2016-09-09
  • mysql分页时offset过大的Sql优化经验分享

    mysql分页时offset过大的Sql优化经验分享

    mysql分页是我们在开发经常遇到的一个功能,最近在实现该功能的时候遇到一个问题,所以这篇文章主要给大家介绍了关于mysql分页时offset过大的Sql优化经验,文中介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友们下面跟着小编来一起看看吧。
    2017-08-08
  • MySQL无法存储emoji表情解决方案分析

    MySQL无法存储emoji表情解决方案分析

    这篇文章主要介绍了MySQL无法存储emoji表情解决方案,结合实例形式分析了Python爬虫爬取文章中emoji表情存入数据库的实现方法,涉及mysql utf8mb4编码的修改相关操作技巧,需要的朋友可以参考下
    2018-07-07
  • MySQL Where 条件语句介绍和运算符小结

    MySQL Where 条件语句介绍和运算符小结

    这篇文章主要介绍了MySQL Where 条件语句介绍和运算符小结,本文同时还给出了一些用法示例,需要的朋友可以参考下
    2014-11-11
  • MySQL中配置文件my.cnf因权限问题导致无法启动的解决方法

    MySQL中配置文件my.cnf因权限问题导致无法启动的解决方法

    这篇文章主要给大家介绍了关于MySQL中配置文件my.cnf因权限问题导致无法启动的解决方法,该无法启动的错误提示代码是:World-writable config file '/etc/my.cnf' is ignored,文中给出了详细的解决方法,需要的朋友们下面来一起看看吧。
    2017-06-06

最新评论