2. 程式人生 > >如何在centos中完全徹底解除安裝mysql

如何在centos中完全徹底解除安裝mysql

阿新 • • 發佈：2018-11-28



CentOS 下如何完全解除安裝MySQL？解決解除安裝不乾淨的問題

系統：CentOS 6.5，MySQL：MySql 5.6

這裡主要解決使用rpm安裝的解除安裝問題，安裝方法見：CentOS安裝MySQL*.rpm提示conflicts with file from package的解決辦法 見 http://www.linuxidc.com/Linux/2016-12/137940.htm

雖然說這裡的是使用rpm安裝的解除安裝問題，我覺得使用yum方式安裝的如果遇到相同的問題也一樣適用。 

檢視已經安裝的服務 
rpm –qa|grep -i mysql 
-i 作用是不區分大小寫

yum remove mysql mysql-server mysql-libs compat-mysql51
rm -rf /var/lib/mysql
rm /etc/my.cnf
檢視是否還有mysql軟體：
rpm -qa|grep mysql
有的話繼續刪除

可以看到有兩個安裝包 
MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
MySQL-client-5.6.19-1.linux_glibc2.5.x86_64.rpm

刪除這兩個服務(去掉字尾) 
rpm –e MySQL-client-5.6.19-1.linux_glibc2.5.x86_64
rpm -e MySQL-server-5.6.19-1.linux_glibc2.5.x86_64  
檢視殘留的目錄：

whereis mysql 

然後刪除mysql目錄：

rm –rf /usr/lib64/mysql 

刪除相關檔案： 
rm –rf /usr/my.cnf
rm -rf /root/.mysql_sercret  
最關鍵的：

rm -rf /var/lib/mysql

如果這個目錄如果不刪除，再重新安裝之後，密碼還是之前的密碼，不會重新初始化！

網上查了很久都沒有文章提到這個，最後還是自己摸索找出來的。


解除安裝完成！怎麼確定是不是真的解除安裝乾淨了呢？

一是看安裝輸出：

如果沒有解除安裝乾淨，安裝server時輸入只有兩行：

[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm

 
Preparing...                ########################################### [100%] 
1:MySQL-server          ########################################### [100%]

解除安裝乾淨了安裝輸入如下：

[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm 
Preparing...                ########################################### [100%] 
1:MySQL-server          ########################################### [100%]

2014-09-23 07:22:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 
2014-09-23 07:22:43 26041 [Note] InnoDB: Using atomics to ref count buffer pool pages 
2014-09-23 07:22:43 26041 [Note] InnoDB: The InnoDB memory heap is disabled 
2014-09-23 07:22:43 26041 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 
2014-09-23 07:22:43 26041 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2014-09-23 07:22:43 26041 [Note] InnoDB: Using Linux native AIO 
2014-09-23 07:22:43 26041 [Note] InnoDB: Using CPU crc32 instructions 
2014-09-23 07:22:43 26041 [Note] InnoDB: Initializing buffer pool, size = 128.0M 
2014-09-23 07:22:43 26041 [Note] InnoDB: Completed initialization of buffer pool 
2014-09-23 07:22:43 26041 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created! 
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB 
2014-09-23 07:22:43 26041 [Note] InnoDB: Database physically writes the file full: wait... 
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB 
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB 
2014-09-23 07:22:45 26041 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 
2014-09-23 07:22:45 26041 [Warning] InnoDB: New log files created, LSN=45781 
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer not found: creating new 
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer created 
2014-09-23 07:22:45 26041 [Note] InnoDB: 128 rollback segment(s) are active. 
2014-09-23 07:22:45 26041 [Warning] InnoDB: Creating foreign key constraint system tables. 
2014-09-23 07:22:45 26041 [Note] InnoDB: Foreign key constraint system tables created 
2014-09-23 07:22:45 26041 [Note] InnoDB: Creating tablespace and datafile system tables. 
2014-09-23 07:22:45 26041 [Note] InnoDB: Tablespace and datafile system tables created. 
2014-09-23 07:22:45 26041 [Note] InnoDB: Waiting for purge to start 
2014-09-23 07:22:45 26041 [Note] InnoDB: 5.6.19 started; log sequence number 0 
A random root password has been set. You will find it in '/root/.mysql_secret'. 
2014-09-23 07:22:46 26041 [Note] Binlog end 
2014-09-23 07:22:46 26041 [Note] InnoDB: FTS optimize thread exiting. 
2014-09-23 07:22:46 26041 [Note] InnoDB: Starting shutdown... 
2014-09-23 07:22:48 26041 [Note] InnoDB: Shutdown completed; log sequence number 1625977

2014-09-23 07:22:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 
2014-09-23 07:22:48 26065 [Note] InnoDB: Using atomics to ref count buffer pool pages 
2014-09-23 07:22:48 26065 [Note] InnoDB: The InnoDB memory heap is disabled 
2014-09-23 07:22:48 26065 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 
2014-09-23 07:22:48 26065 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2014-09-23 07:22:48 26065 [Note] InnoDB: Using Linux native AIO 
2014-09-23 07:22:48 26065 [Note] InnoDB: Using CPU crc32 instructions 
2014-09-23 07:22:48 26065 [Note] InnoDB: Initializing buffer pool, size = 128.0M 
2014-09-23 07:22:48 26065 [Note] InnoDB: Completed initialization of buffer pool 
2014-09-23 07:22:48 26065 [Note] InnoDB: Highest supported file format is Barracuda. 
2014-09-23 07:22:48 26065 [Note] InnoDB: 128 rollback segment(s) are active. 
2014-09-23 07:22:48 26065 [Note] InnoDB: Waiting for purge to start 
2014-09-23 07:22:48 26065 [Note] InnoDB: 5.6.19 started; log sequence number 1625977 
2014-09-23 07:22:48 26065 [Note] Binlog end 
2014-09-23 07:22:48 26065 [Note] InnoDB: FTS optimize thread exiting. 
2014-09-23 07:22:48 26065 [Note] InnoDB: Starting shutdown... 
2014-09-23 07:22:50 26065 [Note] InnoDB: Shutdown completed; log sequence number 1625987

A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER ! 
You will find that password in '/root/.mysql_secret'.

You must change that password on your first connect, 
no other statement but 'SET PASSWORD' will be accepted. 
See the manual for the semantics of the 'password expired' flag.

 Also, the account for the anonymous user has been removed.

 In addition, you can run:

  /usr/bin/mysql_secure_installation

 which will also give you the option of removing the test database. 
This is strongly recommended for production servers.

 See the manual for more instructions.

 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

 New default config file was created as /usr/my.cnf and 
will be used by default by the server when you start it. 
You may edit this file to change server settings

最後一段中提示了重要資訊，很多人因為不喜歡讀英文，導致接下來不知道怎麼操作！

二就是安裝完成，啟動服務之後

CentOS下如何完全乾淨解除安裝MySQL

使用命令：“mysql -uroot -p”輸入你之前安裝後設置的密碼，看能不能登入，如果還可以登入，說明沒有解除安裝乾淨！

CentOS下如何完全解除安裝MySQL？解決解除安裝不乾淨的問題

系統：CentOS 6.5，MySQL：MySql 5.6

這裡主要解決使用rpm安裝的解除安裝問題，安裝方法見：CentOS安裝MySQL*.rpm提示conflicts with file from package的解決辦法 見 http://www.linuxidc.com/Linux/2016-12/137940.htm

雖然說這裡的是使用rpm安裝的解除安裝問題，我覺得使用yum方式安裝的如果遇到相同的問題也一樣適用。 

檢視已經安裝的服務 
rpm –qa|grep -i mysql 
-i 作用是不區分大小寫

yum remove mysql mysql-server mysql-libs compat-mysql51
rm -rf /var/lib/mysql
rm /etc/my.cnf
檢視是否還有mysql軟體：
rpm -qa|grep mysql
有的話繼續刪除

可以看到有兩個安裝包 
MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
MySQL-client-5.6.19-1.linux_glibc2.5.x86_64.rpm

刪除這兩個服務(去掉字尾) 
rpm –e MySQL-client-5.6.19-1.linux_glibc2.5.x86_64
rpm -e MySQL-server-5.6.19-1.linux_glibc2.5.x86_64  
檢視殘留的目錄：

whereis mysql 

然後刪除mysql目錄：

rm –rf /usr/lib64/mysql 

刪除相關檔案： 
rm –rf /usr/my.cnf
rm -rf /root/.mysql_sercret  
最關鍵的：

rm -rf /var/lib/mysql

如果這個目錄如果不刪除，再重新安裝之後，密碼還是之前的密碼，不會重新初始化！

網上查了很久都沒有文章提到這個，最後還是自己摸索找出來的。


解除安裝完成！怎麼確定是不是真的解除安裝乾淨了呢？

一是看安裝輸出：

如果沒有解除安裝乾淨，安裝server時輸入只有兩行：

[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm 
Preparing...                ########################################### [100%] 
1:MySQL-server          ########################################### [100%]

解除安裝乾淨了安裝輸入如下：

[root @localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm 
Preparing...                ########################################### [100%] 
1:MySQL-server          ########################################### [100%]

2014-09-23 07:22:43 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 
2014-09-23 07:22:43 26041 [Note] InnoDB: Using atomics to ref count buffer pool pages 
2014-09-23 07:22:43 26041 [Note] InnoDB: The InnoDB memory heap is disabled 
2014-09-23 07:22:43 26041 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 
2014-09-23 07:22:43 26041 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2014-09-23 07:22:43 26041 [Note] InnoDB: Using Linux native AIO 
2014-09-23 07:22:43 26041 [Note] InnoDB: Using CPU crc32 instructions 
2014-09-23 07:22:43 26041 [Note] InnoDB: Initializing buffer pool, size = 128.0M 
2014-09-23 07:22:43 26041 [Note] InnoDB: Completed initialization of buffer pool 
2014-09-23 07:22:43 26041 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created! 
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB 
2014-09-23 07:22:43 26041 [Note] InnoDB: Database physically writes the file full: wait... 
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB 
2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB 
2014-09-23 07:22:45 26041 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 
2014-09-23 07:22:45 26041 [Warning] InnoDB: New log files created, LSN=45781 
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer not found: creating new 
2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer created 
2014-09-23 07:22:45 26041 [Note] InnoDB: 128 rollback segment(s) are active. 
2014-09-23 07:22:45 26041 [Warning] InnoDB: Creating foreign key constraint system tables. 
2014-09-23 07:22:45 26041 [Note] InnoDB: Foreign key constraint system tables created 
2014-09-23 07:22:45 26041 [Note] InnoDB: Creating tablespace and datafile system tables. 
2014-09-23 07:22:45 26041 [Note] InnoDB: Tablespace and datafile system tables created. 
2014-09-23 07:22:45 26041 [Note] InnoDB: Waiting for purge to start 
2014-09-23 07:22:45 26041 [Note] InnoDB: 5.6.19 started; log sequence number 0 
A random root password has been set. You will find it in '/root/.mysql_secret'. 
2014-09-23 07:22:46 26041 [Note] Binlog end 
2014-09-23 07:22:46 26041 [Note] InnoDB: FTS optimize thread exiting. 
2014-09-23 07:22:46 26041 [Note] InnoDB: Starting shutdown... 
2014-09-23 07:22:48 26041 [Note] InnoDB: Shutdown completed; log sequence number 1625977

2014-09-23 07:22:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 
2014-09-23 07:22:48 26065 [Note] InnoDB: Using atomics to ref count buffer pool pages 
2014-09-23 07:22:48 26065 [Note] InnoDB: The InnoDB memory heap is disabled 
2014-09-23 07:22:48 26065 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 
2014-09-23 07:22:48 26065 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2014-09-23 07:22:48 26065 [Note] InnoDB: Using Linux native AIO 
2014-09-23 07:22:48 26065 [Note] InnoDB: Using CPU crc32 instructions 
2014-09-23 07:22:48 26065 [Note] InnoDB: Initializing buffer pool, size = 128.0M 
2014-09-23 07:22:48 26065 [Note] InnoDB: Completed initialization of buffer pool 
2014-09-23 07:22:48 26065 [Note] InnoDB: Highest supported file format is Barracuda. 
2014-09-23 07:22:48 26065 [Note] InnoDB: 128 rollback segment(s) are active. 
2014-09-23 07:22:48 26065 [Note] InnoDB: Waiting for purge to start 
2014-09-23 07:22:48 26065 [Note] InnoDB: 5.6.19 started; log sequence number 1625977 
2014-09-23 07:22:48 26065 [Note] Binlog end 
2014-09-23 07:22:48 26065 [Note] InnoDB: FTS optimize thread exiting. 
2014-09-23 07:22:48 26065 [Note] InnoDB: Starting shutdown... 
2014-09-23 07:22:50 26065 [Note] InnoDB: Shutdown completed; log sequence number 1625987

A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER ! 
You will find that password in '/root/.mysql_secret'.

You must change that password on your first connect, 
no other statement but 'SET PASSWORD' will be accepted. 
See the manual for the semantics of the 'password expired' flag.

 Also, the account for the anonymous user has been removed.

 In addition, you can run:

  /usr/bin/mysql_secure_installation

 which will also give you the option of removing the test database. 
This is strongly recommended for production servers.

 See the manual for more instructions.

 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

 New default config file was created as /usr/my.cnf and 
will be used by default by the server when you start it. 
You may edit this file to change server settings

最後一段中提示了重要資訊，很多人因為不喜歡讀英文，導致接下來不知道怎麼操作！

二就是安裝完成，啟動服務之後

CentOS下如何完全乾淨解除安裝MySQL

使用命令：“mysql -uroot -p”輸入你之前安裝後設置的密碼，看能不能登入，如果還可以登入，說明沒有解除安裝乾淨！

相關推薦

如何在centos中完全徹底解除安裝mysql

CentOS 下如何完全解除安裝MySQL？解決解除安裝不乾淨的問題 系統：CentOS 6.5，MySQL：MySql 5.6 這裡主要解決使用rpm安裝的解除安裝問題，安裝方法見：CentOS安裝MySQL*.rpm提示confli

windows中徹底解除安裝mysql

1）停止MySQL服務 開啟控制面板→管理工具→服務（找到MySQL） 2）卸掉mysql server 開啟控制面板→程式與功能→找到mysql server然後解除安裝 3）將mysql目錄下的安裝資料夾刪除，例如我的：C:\Program Files (x86)\MySQL 4）刪除mysql

MySQL之——CentOS下徹底解除安裝MySQL

1、檢視MySQL是否安裝  方式1: [[email protected] usr]# yum list installed mysql* Loaded plugins: fastestmirror Loading mirror speeds from ca

Linux 下徹底解除安裝Mysql

1、使用以下命令檢視當前安裝mysql情況，查詢以前是否裝有mysql 1 rpm -qa|

win10系統下如何徹底解除安裝MySQL

1. 先做好資料庫備份 2. 用360或是控制檯解除安裝MySql, 並把相關資料夾刪除 3清除登錄檔.  開始->執行-> regedit 看看登錄檔裡這幾個地方刪除沒有 　　HKEY_LOCAL_MACHINE\SYSTEM\ControlS

ubuntu mysql | 徹底解除安裝mysql並且重新安裝[親自實踐，絕對有效]

轉自：http://www.jianshu.com/p/c76b31df5d09 首先刪除mysql: sudo apt-get remove mysql-* 然後清理殘留的資料 dpkg -l |grep ^rc|awk '{print $2}' |sudo xargs dpkg -P

MySQL解除安裝後重新安裝失敗：The security settings could not be applied to the database bacause the ……（徹底解除安裝MySQL）

MySQL解除安裝後重新安裝失敗 錯誤提示： the security setting could not be applied to the database because the connection has failed with the following error. Err

ubuntu下apt-get安裝和徹底解除安裝mysql

1、安裝mysql： sudo apt-get install mysql-server sudo apt-get install mysql-client sudo apt-get install php5-mysql(用於連線php和mysql) 檢視mysql是否執行 ps aux |

Linux下徹底解除安裝MySQL

一、使用以下命令檢視當前安裝mysql情況，查詢以前是否裝有mysql rpm -qa|grep -i mysql 可以看到如下圖的所示： 顯示之前安裝了： MySQL-client-5.5.25a-1.rhel5 MySQL-server-5.5.25a-1.rhel5

ubuntu徹底解除安裝mysql並且重新安裝

sudo apt-get remove mysql-* 1 然後清理殘留的資料 dpkg -l |grep ^rc|awk '{print $2}' |sudo xargs dpkg -P 1 它會跳出一個對話方塊，你選擇yes就好了  然後安裝mysql sud

徹底解除安裝mysql和開放mysql資料庫的外部連線

解除安裝mysql 1.先停止MySQL服務 2.程式中解除安裝MySQL 3.到安裝目錄刪除MySQL 4.刪除：C:\Documents and Settings\All Users\Application Data\MySQL C:\ProgramData\MySQL 5.檢

mac下徹底解除安裝mysql方法

sudo rm /usr/local/mysql sudo rm -rf /usr/local/mysql* sudo rm -rf /Library/StartupItems/MySQLCOM sudo rm -rf /Library/PreferencePanes/My

Mac os徹底解除安裝MySQL 方法

終端裡輸入： sudo rm /usr/local/mysql sudo rm -rf /usr/local/mysql* sudo rm -rf /Library/StartupItems/MySQLCOM sudo rm -rf /Library/PreferencePanes/My

ubuntu16.04 徹底解除安裝mysql並重新安裝

首先刪除mysql sudo apt-get remove mysql-* dpkg -l |grep ^rc|awk ‘{print $2}’ |sudo xargs dpkg -P 然後安裝mysql 可以直接預設安裝 sudo apt-get install mysql-clien

MySql全套攻略——如何徹底解除安裝MySql篇

二、如何徹底解除安裝MySql導讀:當我們不需要MySql時如何將MySql徹底從我們的計算機清除呢？或者當我們初次安裝MySql不成功，下次再安裝MySql時顯示安裝路徑已存在，該如何辦呢？1.首先，在控制面板中解除安裝MySql，找到MySql相關軟體，逐個解除安裝2.刪

Ubuntu下徹底解除安裝mysql並重新安裝

1、刪除 mysql 1 sudo apt-get autoremove --purge mysql-server-5.02 sudo apt-get remove mysql-server3 sudo apt-get autoremove mysql-server4 su

如何徹底解除安裝mysql及其服務

第一步，執行regedit.exe，找到HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\MySQL 資料夾，將其刪除；第二步，還是在修改登錄檔介面，找到HKEY_LOCAL_MACHINE\SYSTEM\CurrentCont

centos7徹底解除安裝mysql和通過yum安裝mysql

徹底解除安裝mysql 檢視是否有安裝的mysql rpm -qa | grep -i mysql // 檢視命令1 yum list install mysql* // 檢視命令2 解除安裝mysql安裝包 yum remove my

ubuntu下apt-get安裝和徹底解除安裝mysql(其實kail debian都行）

/etc/init.d/mysql start 直接啟動可能出現下列錯誤，啟動命令可以解決這個問題 ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2

Linux下徹底解除安裝mysql詳解

一、使用以下命令檢視當前安裝mysql情況，查詢以前是否裝有mysql 1 rpm -qa|grep -i mysql 可以看到如下圖的所示： 顯示之前安裝了：      MySQL-client-5.5.25a-1.rhel5