After the MySQL service is initialized, use/etc/init.d/mysqld to start the MySQL service, error, and view its bug log error.log:
150413 21:26:54 mysqld_safe mysqld from PID File/data/mysqldata/mysql.pid ended
150413 21:30:19 Mysqld_safe starting mysqld daemon with databases From/data/mysqldata
2015-04-13 21:30:21 27464 [Note] Plugin ' federated ' is disabled.
2015-04-13 21:30:21 27464 [Note] innodb:using Atomics to ref count buffer pool pages
2015-04-13 21:30:21 27464 [Note] innodb:the InnoDB memory heap is disabled
2015-04-13 21:30:21 27464 [Note] innodb:mutexes and rw_locks use GCC atomic builtins
2015-04-13 21:30:21 27464 [Note] innodb:compressed tables use zlib 1.2.3
2015-04-13 21:30:21 27464 [Note] innodb:using Linux native AIO
2015-04-13 21:30:21 27464 [Note] innodb:using CPU CRC32 Instructions
2015-04-13 21:30:21 27464 [Note] innodb:initializing buffer pool, size = 24.0G
2015-04-13 21:30:23 27464 [Note] innodb:completed initialization of buffer pool
2015-04-13 21:30:24 27464 [Note] innodb:highest supported file format is Barracuda.
2015-04-13 21:30:25 27464 [Note] innodb:128 rollback segment (s) is active.
2015-04-13 21:30:25 27464 [Note] innodb:waiting for purge to start
2015-04-13 21:30:25 27464 [Note] innodb:5.6.19 started; Log sequence Number 1626134
2015-04-13 21:30:25 27464 [Note] Server hostname (bind-address): ' * '; port:3306
2015-04-13 21:30:25 27464 [Note] IPv6 is available.
2015-04-13 21:30:25 27464 [note]-':: ' resolves to ':: ';
2015-04-13 21:30:25 27464 [Note] Server socket created on IP: ':: '.
2015-04-13 21:30:25 27464 [ERROR] Can ' t start server:bind on TCP/IP port:address already in use
2015-04-13 21:30:25 27464 [ERROR] Do you already has another MYSQLD server running on port:3306?
2015-04-13 21:30:25 27464 [ERROR] Aborting
With its error message, we can clearly see that port 3306 is already occupied
Cause: The use of initializing MySQL does not stop the MySQL service
Netstat-nputl|grep 3306 results found that there is already a MySQL service in the boot
150413 21:30:29 mysqld_safe mysqld from PID File/data/mysqldata/mysql.pid ended
Stop the MySQL service by/etc/init.d/mysqld stop, and if not, kill it using the kill-9 PID
Start the MySQL service again:/etc/init.d/mysqld start
[[email protected] ~]#/etc/init.d/mysqld start
Starting MySQL ... success!
Remember: When initializing MySQL, you must first stop the database service
Service Mysqld Stop
This article is from the Nagios failure blog, so be sure to keep this source http://5250070.blog.51cto.com/5240070/1636316
Service does not start properly after initializing MySQL