CentOS下如何完全卸载MySQL？解决卸载不干净的问题

系统：CentOS 6.5，MySQL：MySql 5.6

这里主要解决使用rpm安装的卸载问题，安装方法见：CentOS安装mysql*.rpm提示conflicts with file from package的解决办法

虽然说这里的是使用rpm安装的卸载问题，我觉得使用yum方式安装的如果遇到相同的问题也一样适用。

查看已经安装的服务

rpm –qa|grep -i mysql

-i 作用是不区分大小写

可以看到有两个安装包

MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm

删除这两个服务(去掉后缀)

rpm –e MySQL-client-5.6.19-1.linux_glibc2.5.x86_64

查看残留的目录：

whereis mysql

然后删除mysql目录：

rm –rf /usr/lib64/mysql

删除相关文件：

rm –rf /usr/my.cnf

最关键的：

rm -rf /var/lib/mysql

如果这个目录如果不删除，再重新安装之后，密码还是之前的密码，不会重新初始化！

网上查了很久都没有文章提到这个，最后还是自己摸索找出来的。

卸载完成！怎么确定是不是真的卸载干净了呢？

一是看安装输出：

如果没有卸载干净，安装server时输入只有两行：

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

卸载干净了安装输入如下：

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
[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
 
 
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

最后一段中提示了重要信息，很多人因为不喜欢读英文，导致接下来不知道怎么操作！

二就是安装完成，启动服务之后

使用命令：“mysql -uroot -p”输入你之前安装后设置的密码，看能不能登录，如果还可以登录，说明没有卸载干净！

CentOS下如何完全卸载MySQL？卸载自带的mysql的更多相关文章

  1. CentOS下php使用127.0.0.1不能连接mysql的解决方法

    这篇文章主要介绍了CentOS下php使用127.0.0.1不能连接mysql的解决方法,本文原因是SELINUX导致的连接失败,需要的朋友可以参考下 php代码很简单: 复制代码代码如下: $ser ...

  2. Linux Centos下软件的安装与卸载方法

    转载于: http://blog.csdn.net/zolalad/article/details/11368879 Linux下软件的安装与卸载   第一章   linux下安装软件,如何知道软件安 ...

  3. Linux for CentOS 下的 keepalived 安装与卸载以及相关命令操作之详细教程

    百度百科解释: keepalived 是一个类似于 layer3, 4 & 7 交换机制的软件,也就是我们平时说的第 3 层.第 4 层和第 7 层交换.Keepalived 的作用是检测 w ...

  4. CentOS下Apache的停止和卸载

    昨晚搞到一台全球性价比最高的服务器,折腾一晚上,好不容易把node服务开启了,结果访问不了我的网站!!! 访问我的网站,显示的是一个Apache欢迎页面.我想,是不是像之前那样,80端口没有开放,然后 ...

  5. centos下yum安装mysql5.6后，无法启动 MySQL Daemon failed to start

    如果是全新安装应该就不会出现这个问题,升级安装的话,要运行 mysql_upgrade ,但是启动MYSQL就报错MySQL Daemon failed to start 如此就没办法运行mysql_ ...

  6. CentOS下zabbix监控mysql5.6版本主从

    目录 CentOS下zabbix监控mysql5.6版本主从 1. Zabbix添加自定义监控流程 2. 具体步骤 1. 编写监控mysql主从脚本 2. mysql赋权 3. 查看脚本执行效果 4. ...

  7. CentOS下MySQL的彻底卸载

      #################CentOS7下MySQL的卸载#################### 1:查看MySQL是否安装: 方式1: [root@localhost usr]# yu ...

  8. centos下完全卸载mysql

    版权声明:本文为博主原创文章,未经博主允许不得转载. yum方式安装的MySQL 1.yum remove mysql mysql-server mysql-libs compat-mysql51 2 ...

  9. centos下完全卸载mysql（别人写的，我仅仅为了学习记录）

    yum方式安装的mysql 1.yum remove mysql mysql-server mysql-libs compat-mysql51 2.rm -rf /var/lib/mysql 3.rm ...

随机推荐

  1. LeetCode-95. Unique Binary Search Trees II

    Description: Given n, generate all structurally unique BST's (binary search trees) that store values ...

  2. LeetCode—— Median of Two Sorted Arrays

    Description: There are two sorted arrays nums1 and nums2 of size m and n respectively. Find the medi ...

  3. Fiddler进行手机抓包

    测试设备:Windows8.1,Android 4.0.4山寨Android手机 网络环境:电信校园网,Wifi环境 测试工具:Fiddler4 完全参考了:http://www.jb51.net/s ...

  4. 更加优雅地搭建SSH框架（使用java配置）

    时代在不断进步,大量基于xml的配置所带来的弊端也显而易见,在XML配置和直接注解式配置之外还有一种有趣的选择方式-JavaConfig,它是在Spring 3.0开始从一个独立的项目并入到Sprin ...

  5. 移动端手势库Hammer.js学习

    感觉移动端原生支持的 touch.tap.swipe 几个事件好像还不够用,某些时候还会用到诸如缩放.长按等其他功能. 近日学习了一个手势库 Hammer.js,它是一个轻量级的触屏设备手势库,能识别 ...

  6. 基于android平台的斗地主AI

    本软件是基于android平台的斗地主AI,我们在源代码的基础之上,旨在改进AI的算法,使玩家具有更丰富的体验感,让NPC可以更为智能. (一)玩法解析: (1)发牌和叫牌:一副扑克54张,先为每个人 ...

  7. How to Convert Subversion Repo to Git

    用了比较长时间的 SVN,但现在新的项目都采用Git.之前的项目又不得不维护,那么能不能将项目从SVN迁移到Git呢.答案是肯定的,网上的方案是 git-svn,或者更高级的封装 svn2git. 方 ...

  8. linq之let子句

    在Linq查询中Let子句可以创建一个新的范围变量,并使用该变量保存表达式的结果. 看下面的例子: private void LetQuery() { List<UserBaseInfo> ...

  9. [CLR via C#]21. 自动内存管理(垃圾回收机制)

    目录 理解垃圾回收平台的基本工作原理 垃圾回收算法 垃圾回收与调试 使用终结操作来释放本地资源 对托管资源使用终结操作 是什么导致Finalize方法被调用 终结操作揭秘 Dispose模式:强制对象 ...

  10. spring中的DisposableBean和InitializingBean，ApplicationContextAware的用法

    在spring容器初始化bean和销毁bean的以前的操作有很多种, 目前我知道的有:在xml中定义的时候用init-method和destory-method,还有一种就是定义bean的时候实现Di ...