Christophe56
New Pleskian
Hello,
I had a crash with my Plesk 12.5, definitely due to the latest update!
I would like a little help please!
The mysql service did not start on the machine.http://imgur.com/a/VMlwA
http://imgur.com/a/VMlwA
I tested a Plesk repair with the command:
I had errors:
I opened the log: /var/log/mysqld.log
Voici les derniers résultats :
I did not find a solution, so I reinstalled Mysql (version 5.6) and I restored the last backup of Plesk [13/03]!
I have access to my Plesk again, but my websites can not find their database!
The databases on Internet sites appear correctly in Plesk, when I enter one of the databases, the tables appear, but when I try to access, error # 1146 indicates that the table does not exist.
I think I have a link problem between the existing databases and Plesk.
Would you have an idea to deal with that?
I do not want to reinstall everything!
I have tested several commands to repair the tables, but it does not work.
I looked in the mysqld.log file
Here are some of the recurring errors displayed:
Version of Plesk: 12.5.30 Update n ° 61, last updated at 15 Mar 2017 21:54
I had a crash with my Plesk 12.5, definitely due to the latest update!
I would like a little help please!
The mysql service did not start on the machine.http://imgur.com/a/VMlwA
http://imgur.com/a/VMlwA
I tested a Plesk repair with the command:
Code:
plesk installer --select-release-current --reinstall-patch --install-component panel
I had errors:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
failed
***** problem report *****
ERROR while trying to establish test connection
Check the error reason(see log file: /dev/stderr), fix and try again
I opened the log: /var/log/mysqld.log
Voici les derniers résultats :
170313 15:38:41 [Warning] IP address '221.194.44.221' could not be resolved: Temporary failure in name resolution
170313 15:38:51 [Warning] IP address '221.194.44.221' could not be resolved: Temporary failure in name resolution
170313 15:38:59 [Warning] IP address '221.194.44.221' could not be resolved: Temporary failure in name resolution
170313 15:39:11 [Warning] IP address '221.194.44.221' could not be resolved: Temporary failure in name resolution
170313 15:39:20 [Warning] IP address '221.194.44.221' could not be resolved: Temporary failure in name resolution
170313 15:39:31 [Warning] IP address '221.194.44.221' could not be resolved: Temporary failure in name resolution
170313 15:39:41 [Warning] IP address '221.194.44.221' could not be resolved: Temporary failure in name resolution
170313 15:39:52 [Warning] IP address '221.194.44.221' could not be resolved: Temporary failure in name resolution
170313 15:40:02 [Warning] IP address '221.194.44.221' could not be resolved: Temporary failure in name resolution
170314 3:32:34 [Note] /usr/libexec/mysqld: Normal shutdown
170314 3:32:34 [Note] Event Scheduler: Purging the queue. 0 events
170314 3:32:36 [Warning] /usr/libexec/mysqld: Forcing close of thread 362017 user: 'admin'
170314 3:32:36 [Warning] /usr/libexec/mysqld: Forcing close of thread 362016 user: 'admin'
170314 3:32:36 [Warning] /usr/libexec/mysqld: Forcing close of thread 362013 user: 'admin'
170314 3:32:36 [Warning] /usr/libexec/mysqld: Forcing close of thread 362012 user: 'admin'
170314 3:32:36 InnoDB: Starting shutdown...
170314 3:32:38 InnoDB: Shutdown completed; log sequence number 1242839078
170314 3:32:38 [Note] /usr/libexec/mysqld: Shutdown complete
I did not find a solution, so I reinstalled Mysql (version 5.6) and I restored the last backup of Plesk [13/03]!
I have access to my Plesk again, but my websites can not find their database!
The databases on Internet sites appear correctly in Plesk, when I enter one of the databases, the tables appear, but when I try to access, error # 1146 indicates that the table does not exist.
I think I have a link problem between the existing databases and Plesk.
Would you have an idea to deal with that?
I do not want to reinstall everything!
I have tested several commands to repair the tables, but it does not work.
I looked in the mysqld.log file
Here are some of the recurring errors displayed:
2017-03-15 22:01:20 1620 [Warning] InnoDB: Cannot open table c1democe/sq71x_admintools_redirects from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2017-03-15 22:01:20 1620 [Warning] InnoDB: Cannot open table c1democe/sq71x_admintools_scanalerts from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2017-03-15 22:01:20 1620 [Warning] InnoDB: Cannot open table c1democe/sq71x_admintools_scans from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2017-03-15 22:01:20 1620 [Warning] InnoDB: Cannot open table c1democe/sq71x_admintools_storage from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2017-03-15 22:01:20 1620 [Warning] InnoDB: Cannot open table c1democe/sq71x_admintools_wafblacklists from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2017-03-15 22:01:20 1620 [Warning] InnoDB: Cannot open table c1democe/sq71x_admintools_wafexceptions from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
Version of Plesk: 12.5.30 Update n ° 61, last updated at 15 Mar 2017 21:54
Last edited: