SOLVED Reinstall MySQL on cPanel?

navhost

Registered
Aug 16, 2018
3
1
1
Bucharest
cPanel Access Level
DataCenter Provider
I've a question. I guess it's a stupid question, but I really need help.

I have a little problem with mysql. So, with innodb_force_recovery=3 in /etc/my.cnf is working in recovery mode.
If I put innodb_force_recovery=0 I get many errors like mysqli_real_connect(): (HY000/2002): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111), sometimes mysql doesn't start.

There is a way to give a reinstall to mysql without losing databases and users? I've got many databases and users.

Please, help! Thank you!
 

navhost

Registered
Aug 16, 2018
3
1
1
Bucharest
cPanel Access Level
DataCenter Provider
I've got a problem after MariaDB upgrade:

[email protected] [~]# systemctl status mariadb.service
● mariadb.service - MariaDB 10.2.17 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: activating (auto-restart) (Result: signal) since Fri 2018-08-17 11:10:22 EEST; 854ms ago
Docs: man:mysqld(8)
systemd
Process: 4590 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 18449 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
Process: 18395 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 18393 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 18449 (code=killed, signal=ABRT)
Aug 17 11:10:22 cp.xtremehost.ro systemd[1]: Failed to start MariaDB 10.2.17 database server.
Aug 17 11:10:22 cp.xtremehost.ro systemd[1]: Unit mariadb.service entered failed state.
Aug 17 11:10:22 cp.xtremehost.ro systemd[1]: mariadb.service failed.

[email protected][~]# service mysql status
ERROR! MariaDB is not running



Setting I have in /etc/my.cnf

[mysqld]
log-error=/var/lib/mysql/logitex.net.err
performance-schema=off
default-storage-engine=MyISAM
max_allowed_packet=268435456
open_files_limit=11000
innodb_force_recovery=6
#i put v. 6 beacouse database won't start normally.
innodb_file_per_table=1
read_only =0
datadir=/var/lib/mysql



Errors I have in /var/lib/mysql/logitex.net.err

2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Started in read only mode
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Uses event mutexes
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Compressed tables use zlib 1.2.7
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Using Linux native AIO
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Number of pools: 1
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Using generic crc32 instructions
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Disabling background log and ibuf IO write threads.
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Completed initialization of buffer pool
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Highest supported file format is Barracuda.
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: innodb_force_recovery=6 skips redo log apply
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: Highest supported file format is Barracuda.
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: innodb_force_recovery=6 skips redo log apply
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: 5.7.23 started; log sequence number 0
2018-08-17 11:12:39 140121457760448 [Note] InnoDB: !!! innodb_force_recovery is set to 6 !!!
2018-08-17 11:12:39 140121457760448 [Note] Plugin 'FEEDBACK' is disabled.
2018-08-17 11:12:39 140121457760448 [Note] Server socket created on IP: '::'.
2018-08-17 11:12:39 140120983725824 [ERROR] InnoDB: Failed to find tablespace for table `mysql`.`gtid_slave_pos` in the cache. Attempting to load the tablespace with space id 63217
2018-08-17 11:12:39 140120983725824 [Warning] InnoDB: Allocated tablespace ID 63217 for mysql/gtid_slave_pos, old maximum was 0
2018-08-17 11:12:39 140121457760448 [Note] Reading of all Master_info entries succeded
2018-08-17 11:12:39 140121457760448 [Note] Added new Master_info '' to hash table
2018-08-17 11:12:39 140121457760448 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.2.17-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
2018-08-17 11:15:32 140120983418624 [ERROR] InnoDB: Failed to find tablespace for table `tripleh_whmcs`.`tblapplinks` in the cache. Attempting to load the tablespace with space id 62853
2018-08-17 11:15:32 140120983111424 [ERROR] InnoDB: Failed to find tablespace for table `tripleh_whmcs`.`tblknowledgebasetags` in the cache. Attempting to load the tablespace with space id 62858


I putted also bind-address 127.0.0.1 & port 3306. If I start in normal mode with innodb_force recovery setted to 0 I get:

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'

Also, I've checked where socket is, and I found it. I've putted in my.cnf the socket location, but nothing.. Same problem.

Please help!
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,203
363
Hello @navhost,

It looks like InnoDB is corrupted and it's preventing MySQL from starting. Here's a resource regarding InnoDB repair that you may find helpful:

InnoDB Corruption Repair Guide

It includes information beyond just using the "innodb_force_recovery" option. Let us know if this helps.

Thank you.