从官网下载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,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对网站的支持!
《魔兽世界》大逃杀!60人新游玩模式《强袭风暴》3月21日上线
暴雪近日发布了《魔兽世界》10.2.6 更新内容,新游玩模式《强袭风暴》即将于3月21 日在亚服上线,届时玩家将前往阿拉希高地展开一场 60 人大逃杀对战。
艾泽拉斯的冒险者已经征服了艾泽拉斯的大地及遥远的彼岸。他们在对抗世界上最致命的敌人时展现出过人的手腕,并且成功阻止终结宇宙等级的威胁。当他们在为即将于《魔兽世界》资料片《地心之战》中来袭的萨拉塔斯势力做战斗准备时,他们还需要在熟悉的阿拉希高地面对一个全新的敌人──那就是彼此。在《巨龙崛起》10.2.6 更新的《强袭风暴》中,玩家将会进入一个全新的海盗主题大逃杀式限时活动,其中包含极高的风险和史诗级的奖励。
《强袭风暴》不是普通的战场,作为一个独立于主游戏之外的活动,玩家可以用大逃杀的风格来体验《魔兽世界》,不分职业、不分装备(除了你在赛局中捡到的),光是技巧和战略的强弱之分就能决定出谁才是能坚持到最后的赢家。本次活动将会开放单人和双人模式,玩家在加入海盗主题的预赛大厅区域前,可以从强袭风暴角色画面新增好友。游玩游戏将可以累计名望轨迹,《巨龙崛起》和《魔兽世界:巫妖王之怒 经典版》的玩家都可以获得奖励。
更新动态
- DzintraErliha-Dreamscape(2024)[24Bit-96kHz]FLAC
- 群星.1999-上华世纪国语总冠军4CD【上华】【WAV+CUE】
- 叶丽仪.1992-仙鹤神针电视剧原声音乐专辑【星传真】【WAV+CUE】
- 陈柏宇.2011-QUINQUENNIUM【SONY】【WAV+CUE】
- 《51首热门当红歌曲 十大顶级发烧女声 3CD》[WAV+CUE][1.6GB]
- 《赵传 深受摇滚迷青睐的台湾音乐人 约定》[WAV+CUE][320MB]
- 《庄心妍 实力唱将 发烧音乐精选集》[WAV+CUE][380MB]
- [音展纪念碟]2006年《TAA台湾第十六届国际HI-ENDHI-FI音响展》2cd[WAV]
- 中国音乐地图之听见西藏山歌牧歌酒歌2020[WAV分轨]
- 王宏伟2017-永远的红飘带[太平洋影音][WAV+CUE]
- 费翔.1997-NOW现在【第一中国】【WAV+CUE】
- 新格合唱团.1981-我唱你和2辑(滚石新格民歌系列)【新格】【WAV+CUE】
- 陈柏宇.2011-QUINQUENNIUM【SONY】【WAV+CUE】
- 雨果唱片-《金唛系列-蔷薇依韵琼瑶》WAV
- 陈百强《凝望(2012华纳LPCD45限量版)[DMI]》[WAV整轨]