In CentOS, how does one completely uninstall MySQL? Solve the Problem of uninstallation being unclean

In CentOS, how does one completely uninstall MySQL? Solve the Problem of uninstallation being unclean

In CentOS, how does one completely uninstall MySQL? Solve the Problem of uninstallation being unclean

System: CentOS 6.5, MySQL: MySql 5.6

Here we mainly solve the problem.RpmFor installation and uninstallation issues, see: how to install mysql in CentOS *. The rpm prompts conflicts with file from package.

Although here is the problem of installing and uninstalling with rpm, I think yum installation is also applicable if the same problem occurs.

View installed servicesRpm-qa | grep-I mysql

-I is case insensitive.
Two installation packages are available.

MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpm
Delete these two services (remove the suffix)

Rpm e MySQL-client-5.6.19-1.linux_glibc2.5.x86_64

View the residual directory:

Whereis mysql

Then delete the mysql directory:

Rm-rf/usr/lib64/mysql

Delete Related Files: rm-rf/usr/my. cnf:

Rm-rf/var/lib/mysql

If this directory is not deleted, after re-installation, the password is still the previous password and will not be reinitialized!

I haven't mentioned this on the internet for a long time. I finally found it myself.
Uninstalled successfully! Are you sure you want to uninstall it?

First, check the installation output:

If the server is not uninstalled, only two lines are entered during server installation:

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

Enter the following command to uninstall the installation:

[root@localhost opt]# rpm -ivh MySQL-server-5.6.19-1.linux_glibc2.5.x86_64.rpmPreparing...                ########################################### [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 pages2014-09-23 07:22:43 26041 [Note] InnoDB: The InnoDB memory heap is disabled2014-09-23 07:22:43 26041 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins2014-09-23 07:22:43 26041 [Note] InnoDB: Compressed tables use zlib 1.2.32014-09-23 07:22:43 26041 [Note] InnoDB: Using Linux native AIO2014-09-23 07:22:43 26041 [Note] InnoDB: Using CPU crc32 instructions2014-09-23 07:22:43 26041 [Note] InnoDB: Initializing buffer pool, size = 128.0M2014-09-23 07:22:43 26041 [Note] InnoDB: Completed initialization of buffer pool2014-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 MB2014-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 MB2014-09-23 07:22:43 26041 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB2014-09-23 07:22:45 26041 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile02014-09-23 07:22:45 26041 [Warning] InnoDB: New log files created, LSN=457812014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer not found: creating new2014-09-23 07:22:45 26041 [Note] InnoDB: Doublewrite buffer created2014-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 created2014-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 start2014-09-23 07:22:45 26041 [Note] InnoDB: 5.6.19 started; log sequence number 0A random root password has been set. You will find it in '/root/.mysql_secret'.2014-09-23 07:22:46 26041 [Note] Binlog end2014-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 16259772014-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 pages2014-09-23 07:22:48 26065 [Note] InnoDB: The InnoDB memory heap is disabled2014-09-23 07:22:48 26065 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins2014-09-23 07:22:48 26065 [Note] InnoDB: Compressed tables use zlib 1.2.32014-09-23 07:22:48 26065 [Note] InnoDB: Using Linux native AIO2014-09-23 07:22:48 26065 [Note] InnoDB: Using CPU crc32 instructions2014-09-23 07:22:48 26065 [Note] InnoDB: Initializing buffer pool, size = 128.0M2014-09-23 07:22:48 26065 [Note] InnoDB: Completed initialization of buffer pool2014-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 start2014-09-23 07:22:48 26065 [Note] InnoDB: 5.6.19 started; log sequence number 16259772014-09-23 07:22:48 26065 [Note] Binlog end2014-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 1625987A 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_installationwhich 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.comSupport MySQL by buying support/licenses at http://shop.mysql.comNew default config file was created as /usr/my.cnf andwill be used by default by the server when you start it.You may edit this file to change server settings

Important information is prompted in the last section. Many people do not know how to perform this operation because they do not like to read English!

Second, the installation is complete. After the service is started

Run the command: "mysql-uroot-p" and enter the password you set after installation to check whether you can log on. If you can log on again, it indicates that it has not been uninstalled!