Resolved error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)'

[tonyo]

I i'v tried every procedor found in google but i cannot restart mysql in centos. any suggestion. here is my tail -100 /var/log/mysql.log

# tail -100 /var/log/mysqld.log
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

170313 17:19:03 [ERROR] Cannot find or open table iscrizioni/wp_options from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

170313 17:19:03 [ERROR] Cannot find or open table iscrizioni/wp_options from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

170313 17:19:03 [ERROR] Cannot find or open table iscrizioni/wp_options from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

170313 17:19:03 [ERROR] Cannot find or open table iscrizioni/wp_options from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

170313 17:19:03 [ERROR] Cannot find or open table iscrizioni/wp_options from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

170313 17:19:03 [ERROR] Cannot find or open table iscrizioni/wp_options from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

170313 17:19:03 [ERROR] Cannot find or open table iscrizioni/wp_options from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

170313 18:00:23 [Warning] IP address '49.4.135.123' could not be resolved: Name or service not known
170313 19:23:02 [Warning] IP address '171.92.208.127' could not be resolved: Name or service not known
170313 21:10:19 [Warning] IP address '182.18.72.63' could not be resolved: Name or service not known
170314 3:18:25 [Note] /usr/libexec/mysqld: Normal shutdown

170314 3:18:25 [Note] Event Scheduler: Purging the queue. 0 events
170314 3:18:27 [Warning] /usr/libexec/mysqld: Forcing close of thread 2395059 user: 'admin'

170314 3:18:27 [Warning] /usr/libexec/mysqld: Forcing close of thread 2395058 user: 'admin'

170314 3:18:27 [Warning] /usr/libexec/mysqld: Forcing close of thread 2395007 user: 'admin'

170314 3:18:27 [Warning] /usr/libexec/mysqld: Forcing close of thread 2395006 user: 'admin'

170314 3:18:27 [Warning] /usr/libexec/mysqld: Forcing close of thread 793695 user: 'admin'

170314 3:18:27 InnoDB: Starting shutdown...
170314 3:19:03 InnoDB: Shutdown completed; log sequence number 26219376777
170314 3:19:03 [Note] /usr/libexec/mysqld: Shutdown complete

170314 03:19:04 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

 

[UFHH01]

Hi tonyo,

even that you don't provide informations about your operating system, or the used MySQL - version, I assume, that you hit the very same bug as other CentOS - users, which use the Atomicorp - repo. Pls. have a look at:

=> MySQL does not start after an update [14-March, 2017] ( KB - article 115001906725 )

Possible solutions can as well being found here:

=> #24
=> #35​

​

 

[tonyo]

Thanks
UFHH01

i solved!

 

[Bobbbb]

This appears to me my problem as well, however, I do not have Yum configured to automatically update. Did the Plesk built-in update system initiate this mysql update?

 

[UFHH01]

Hi Bobbbb,

this depends on YOUR UNIQUE settings at: => Home > Tools & Settings > Update and Upgrade Settings