Erro migração servidor mysql (mariadb)

[brekler 0]

Bom dia pessoal.

Seguinte, tenho um servidor Centos 7 com zabbix nele. Ele estava em um Hyper-V.

Estamos migrando nossa estrutura toda para VMWare, e estava tudo ocorrendo normal. Consegui migrar meu OCS, entre outros.

Mas quando cheguei nesse server ele não sobe o banco de dados.

Ocorre o seguinte erro quando vou conectar no BD: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

Fui verificar e esse arquivo não existe.

Mas no servidor que esta no Hyper-V ainda esta normal. O servidor só foi migrado literalmente. Foi passado do Hyper-V para VMWare.

Quando tento subir o serviço ocorre o seguinte erro:

[root@localhost ~]# systemctl start mariadb
Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.

Segue o detalhe do serviço:

[root@localhost ~]# systemctl status mariadb.service -l
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Qua 2016-05-11 08:27:54 BRT; 23s ago
Process: 19430 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
Process: 19428 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
Process: 19396 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 19428 (code=exited, status=0/SUCCESS)

Mai 11 08:27:53 localhost.localdomain mariadb-prepare-db-dir[19396]: Failed to determine peer security context: Protocolo não disponível
Mai 11 08:27:53 localhost.localdomain mariadb-prepare-db-dir[19396]: Showing one /org/freedesktop/systemd1/unit/mariadb_2eservice
Mai 11 08:27:53 localhost.localdomain mariadb-prepare-db-dir[19396]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 error=n/a
Mai 11 08:27:53 localhost.localdomain mariadb-prepare-db-dir[19396]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.334 object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a
Mai 11 08:27:53 localhost.localdomain mariadb-prepare-db-dir[19396]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/mariadb_2eservice interface=org.freedesktop.DBus.Properties member=GetAll cookie=2 reply_cookie=0 error=n/a
Mai 11 08:27:53 localhost.localdomain mariadb-wait-ready[19430]: Executing: /usr/libexec/mariadb-wait-ready 19428
Mai 11 08:27:53 localhost.localdomain mysqld_safe[19428]: Executing: /usr/bin/mysqld_safe --basedir=/usr
Mai 11 08:27:53 localhost.localdomain mysqld_safe[19428]: 160511 08:27:53 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Mai 11 08:27:53 localhost.localdomain mysqld_safe[19428]: 160511 08:27:53 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Mai 11 08:27:54 localhost.localdomain mysqld_safe[19428]: 160511 08:27:54 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended

E segue o log do serviço:

Server version: 5.5.47-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466712 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7f0f4725809d]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7f0f46e6c175]
/lib64/libpthread.so.0(+0xf100)[0x7f0f4659b100]
/usr/libexec/mysqld(+0x730ebd)[0x7f0f470fcebd]
/usr/libexec/mysqld(+0x732366)[0x7f0f470fe366]
/usr/libexec/mysqld(+0x7157cc)[0x7f0f470e17cc]
/usr/libexec/mysqld(+0x717886)[0x7f0f470e3886]
/usr/libexec/mysqld(+0x697e86)[0x7f0f47063e86]
/usr/libexec/mysqld(+0x6da363)[0x7f0f470a6363]
/usr/libexec/mysqld(+0x641488)[0x7f0f4700d488]
/lib64/libpthread.so.0(+0x7dc5)[0x7f0f46593dc5]
/lib64/libc.so.6(clone+0x6d)[0x7f0f44e0f28d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
160511 08:27:54 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended

Alguém tem alguma ideia de como arrumar ?