Percona shuts down and gives error regarding china IPs

My perconal server shuts down frequently. this was not happening before installing percona on centos, cpanel server i followed official documentation of cpanel.

140729 4:45:27 [Note] /usr/sbin/mysqld: ready [COLOR=#00008B]for connections. Version: ‘5.5.37-cll’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 MySQL Community Server (GPL) 140729 5:10:42 [Warning] IP address ‘’ could [COLOR=#00008B]not be resolved: Name [COLOR=#00008B]or service [COLOR=#00008B]not known 140729 6:39:48 [Warning] IP address ‘’ has been resolved [COLOR=#00008B]to the host name ‘’, which resembles IPv4-address itself. 140729 08:01:44 mysqld_safe Starting mysqld daemon [COLOR=#00008B]with databases [COLOR=#00008B]from /var/lib/mysql 140729 8:01:45 [Note] Plugin ‘FEDERATED’ [COLOR=#00008B]is disabled. 140729 8:01:45 InnoDB: The InnoDB memory heap [COLOR=#00008B]is disabled 140729 8:01:45 InnoDB: Mutexes [COLOR=#00008B]and rw_locks [COLOR=#00008B]use GCC atomic builtins 140729 8:01:45 InnoDB: Compressed tables [COLOR=#00008B]use zlib 1.2.3 140729 8:01:45 InnoDB: [COLOR=#00008B]Using Linux native AIO 140729 8:01:45 InnoDB: Initializing buffer pool, size = 128.0M 140729 8:01:45 InnoDB: Completed initialization [COLOR=#00008B]of buffer pool 140729 8:01:45 InnoDB: highest supported [COLOR=#00008B]file format [COLOR=#00008B]is Barracuda. InnoDB: The log sequence number [COLOR=#00008B]in ibdata files does [COLOR=#00008B]not [COLOR=#00008B]match InnoDB: the log sequence number [COLOR=#00008B]in the ib_logfiles! 140729 8:01:45 InnoDB: [COLOR=#00008B]Database was [COLOR=#00008B]not shut down normally!

The messages on IP addresses were just warnings, in the first case, the DNS lookup couldn’t resolve the ip, in the second case, the host name looks like an IP address. Neither of these warnings would cause mysqld to shutdown.

There is no error message around the timestamp of this restart. Either something was seriously wrong and mysqld didn’t get a chance to leave any hint, or the mysqld process was killed abruptly.

Can you please check error log for each restart and see if there was always no error logged before each restart? And please check if there could be any chance that some process kills mysqld.