Laden Sie mysql-5.6.12-linux-glibc2.5-x86_64.tar.gz von der offiziellen Website herunter
MySQL-Benutzer erstellen
[root@Master home]# useradd mysql [root@Master data]# echo 'mysql'|passwd --stdin mysql
Ändern Sie das Passwort des Benutzers MySQL.
passwd: Alle Authentifizierungstoken wurden erfolgreich aktualisiert.
Grund für die Erstellung eines MySQL-Benutzers
Wenn Sie MySQL nicht verwenden, tritt ein Fehler auf. Nach mehrmaligem Versuch wurde der MySQL-Benutzer erfolgreich installiert
* Natürlich haben wir oft bereits andere Benutzer erstellt, um den täglichen Betrieb abzuschließen. Wenn Sie keinen MySQL-Benutzer erstellen, ändern Sie die Datei mysqld_safe im Verzeichnis mysql/bin. //Persönlicher Test erfolgreich
Spezifische Schritte:
[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
Erstellen Sie das Datenverzeichnis unter dem MySQL-Benutzer und entpacken Sie es
[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 //重命名
Berechtigungen festlegen
[root@Master data]# chown -R mysql:mysql mysql
Benutzer wechseln und das Verzeichnis mysql/scripts aufrufen
[root@Master data]# su mysql [mysql@Master data]$ cd mysql/scripts/ [mysql@Master scripts]$
Installation (das Verzeichnis wird entsprechend Ihrem eigenen MySQL-Dekomprimierungsverzeichnis festgelegt)
[mysql@Master scripts]$ ./mysql_install_db --user=mysql --basedir=/home/mysql/data/mysql --datadir=/home/mysql/data/mysql/data
Ausgabeinformationen
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
Konfigurationsdatei
[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文件
Fügen Sie die folgenden zwei Zeilen hinzu
basedir=/home/mysql/data/mysql datadir=/home/mysql/data/mysql/data
Umgebungsvariablen konfigurieren
[root@Master support-files]# vim /etc/profile #set mysql environment export MYSQL_HOME=/home/mysql/data/mysql export PATH=$MYSQL_HOME/bin:$PATH
Konfigurieren Sie den MySQL-Dienst so, dass er beim Booten automatisch gestartet wird
[root@Master bin]# chkconfig --add mysql //添加mysql [root@Master bin]# chkconfig mysql on //设置开机启动
MySQL starten
[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-Login-Passwort festlegen
[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>
Das Obige ist die Einführung des Herausgebers zur Installation von mysql-5.6.12-linux-glibc2.5-x86_64.tar.gz unter Linux. Wenn Sie Fragen haben, hinterlassen Sie mir bitte eine Nachricht, der Herausgeber wird allen rechtzeitig antworten. Vielen Dank für Ihre Unterstützung der Website!