There are problems getting mysqld to start, shows with errors like:
[root@mapin-cp-01 ~]# service mysqld start Another MySQL daemon already running with the same unix socket. Starting mysqld: [FAILED] [root@mapin-cp-01 ~]# [root@mapin-cp-01 ~]# tail /var/log/mysqld.log 140129 11:19:26 [Note] /usr/libexec/mysqld: Shutdown complete 140129 11:19:26 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 140129 11:23:31 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 140129 11:23:31 InnoDB: Initializing buffer pool, size = 8.0M 140129 11:23:31 InnoDB: Completed initialization of buffer pool 140129 11:23:31 InnoDB: Started; log sequence number 0 3236114 140129 11:23:31 [Note] Event Scheduler: Loaded 0 events 140129 11:23:31 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.71' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
All OnApp versions
Restarting the control server should resolve this.
If not, then you can do the following:
mv /var/lib/mysql/mysql.sock /var/lib/mysql/mysql.sock.bak service mysqld start
Restarting the service creates a new entry called mqsql.sock and allow mysqld to start normally after.
This is caused by a previous mysql socket not getting properly terminated on the server preventing a new one from being created for the mysqld startup.