搜尋
首頁資料庫mysql教程Linux下方安裝mysql-5.6.12-linux-glibc2.5-x86_64.tar.gz_MySQL

從官網下載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,希望對大家有幫助,如果大家有任何疑問請給我留言,小編會及時回覆大家的。在此也非常感謝大家對網站的支持!

陳述
本文內容由網友自願投稿,版權歸原作者所有。本站不承擔相應的法律責任。如發現涉嫌抄襲或侵權的內容,請聯絡admin@php.cn
您什麼時候應該使用複合索引與多個單列索引?您什麼時候應該使用複合索引與多個單列索引?Apr 11, 2025 am 12:06 AM

在數據庫優化中,應根據查詢需求選擇索引策略:1.當查詢涉及多個列且條件順序固定時,使用複合索引;2.當查詢涉及多個列但條件順序不固定時,使用多個單列索引。複合索引適用於優化多列查詢,單列索引則適合單列查詢。

如何識別和優化MySQL中的慢速查詢? (慢查詢日誌,performance_schema)如何識別和優化MySQL中的慢速查詢? (慢查詢日誌,performance_schema)Apr 10, 2025 am 09:36 AM

要優化MySQL慢查詢,需使用slowquerylog和performance_schema:1.啟用slowquerylog並設置閾值,記錄慢查詢;2.利用performance_schema分析查詢執行細節,找出性能瓶頸並優化。

MySQL和SQL:開發人員的基本技能MySQL和SQL:開發人員的基本技能Apr 10, 2025 am 09:30 AM

MySQL和SQL是開發者必備技能。 1.MySQL是開源的關係型數據庫管理系統,SQL是用於管理和操作數據庫的標準語言。 2.MySQL通過高效的數據存儲和檢索功能支持多種存儲引擎,SQL通過簡單語句完成複雜數據操作。 3.使用示例包括基本查詢和高級查詢,如按條件過濾和排序。 4.常見錯誤包括語法錯誤和性能問題,可通過檢查SQL語句和使用EXPLAIN命令優化。 5.性能優化技巧包括使用索引、避免全表掃描、優化JOIN操作和提升代碼可讀性。

描述MySQL異步主奴隸複製過程。描述MySQL異步主奴隸複製過程。Apr 10, 2025 am 09:30 AM

MySQL異步主從復制通過binlog實現數據同步,提升讀性能和高可用性。 1)主服務器記錄變更到binlog;2)從服務器通過I/O線程讀取binlog;3)從服務器的SQL線程應用binlog同步數據。

mysql:簡單的概念,用於輕鬆學習mysql:簡單的概念,用於輕鬆學習Apr 10, 2025 am 09:29 AM

MySQL是一個開源的關係型數據庫管理系統。 1)創建數據庫和表:使用CREATEDATABASE和CREATETABLE命令。 2)基本操作:INSERT、UPDATE、DELETE和SELECT。 3)高級操作:JOIN、子查詢和事務處理。 4)調試技巧:檢查語法、數據類型和權限。 5)優化建議:使用索引、避免SELECT*和使用事務。

MySQL:數據庫的用戶友好介紹MySQL:數據庫的用戶友好介紹Apr 10, 2025 am 09:27 AM

MySQL的安裝和基本操作包括:1.下載並安裝MySQL,設置根用戶密碼;2.使用SQL命令創建數據庫和表,如CREATEDATABASE和CREATETABLE;3.執行CRUD操作,使用INSERT,SELECT,UPDATE,DELETE命令;4.創建索引和存儲過程以優化性能和實現複雜邏輯。通過這些步驟,你可以從零開始構建和管理MySQL數據庫。

InnoDB緩衝池如何工作,為什麼對性能至關重要?InnoDB緩衝池如何工作,為什麼對性能至關重要?Apr 09, 2025 am 12:12 AM

InnoDBBufferPool通過將數據和索引頁加載到內存中來提升MySQL數據庫的性能。 1)數據頁加載到BufferPool中,減少磁盤I/O。 2)臟頁被標記並定期刷新到磁盤。 3)LRU算法管理數據頁淘汰。 4)預讀機制提前加載可能需要的數據頁。

MySQL:初學者的數據管理易用性MySQL:初學者的數據管理易用性Apr 09, 2025 am 12:07 AM

MySQL適合初學者使用,因為它安裝簡單、功能強大且易於管理數據。 1.安裝和配置簡單,適用於多種操作系統。 2.支持基本操作如創建數據庫和表、插入、查詢、更新和刪除數據。 3.提供高級功能如JOIN操作和子查詢。 4.可以通過索引、查詢優化和分錶分區來提升性能。 5.支持備份、恢復和安全措施,確保數據的安全和一致性。

See all articles

熱AI工具

Undresser.AI Undress

Undresser.AI Undress

人工智慧驅動的應用程序,用於創建逼真的裸體照片

AI Clothes Remover

AI Clothes Remover

用於從照片中去除衣服的線上人工智慧工具。

Undress AI Tool

Undress AI Tool

免費脫衣圖片

Clothoff.io

Clothoff.io

AI脫衣器

AI Hentai Generator

AI Hentai Generator

免費產生 AI 無盡。

熱門文章

R.E.P.O.能量晶體解釋及其做什麼(黃色晶體)
3 週前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.最佳圖形設置
3 週前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.如果您聽不到任何人,如何修復音頻
3 週前By尊渡假赌尊渡假赌尊渡假赌
WWE 2K25:如何解鎖Myrise中的所有內容
3 週前By尊渡假赌尊渡假赌尊渡假赌

熱工具

禪工作室 13.0.1

禪工作室 13.0.1

強大的PHP整合開發環境

Atom編輯器mac版下載

Atom編輯器mac版下載

最受歡迎的的開源編輯器

Dreamweaver CS6

Dreamweaver CS6

視覺化網頁開發工具

ZendStudio 13.5.1 Mac

ZendStudio 13.5.1 Mac

強大的PHP整合開發環境

EditPlus 中文破解版

EditPlus 中文破解版

體積小,語法高亮,不支援程式碼提示功能