Andrew_Alison
New Pleskian
Good Evening/Day,
Running : 11.0.9-cos6.build110120608.16.x86_64
My server stopped responding so I restarted it. When I tried to access the panel I received the following error.
I have tried to restart Mysqld and it starts sometimes and other times fails. Still with the same error message. The mysqld.log is growing exponentially. I have renamed it and watched it grow to a silly size almost immediately.
the log file seems to be mainly the following entries :
Drew
Running : 11.0.9-cos6.build110120608.16.x86_64
My server stopped responding so I restarted it. When I tried to access the panel I received the following error.
ERROR: PleskFatalException
Unable to connect to database: mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: No such file or directory
0: common_func.php3:153
psaerror(string 'Unable to connect to database: mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: No such file or directory')
1: auth.php3:116
I checked the logs and noticed that there was a bruteforce attack going on through SSH - which I have now resolved by denying the hosts that were attempting access the server through SSH.Unable to connect to database: mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: No such file or directory
0: common_func.php3:153
psaerror(string 'Unable to connect to database: mysql_connect() [<a href='function.mysql-connect'>function.mysql-connect</a>]: No such file or directory')
1: auth.php3:116
I have tried to restart Mysqld and it starts sometimes and other times fails. Still with the same error message. The mysqld.log is growing exponentially. I have renamed it and watched it grow to a silly size almost immediately.
the log file seems to be mainly the following entries :
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
74 75 76 77 78 150130 10:44:45 InnoDB: Error: page 19361 log sequence number 17578060947
InnoDB: is in the future! Current system log sequence number 17577975669.
my.cnf is set to : (I added the force recovery = 1)InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
74 75 76 77 78 150130 10:44:45 InnoDB: Error: page 19361 log sequence number 17578060947
InnoDB: is in the future! Current system log sequence number 17577975669.
[mysqld]
innodb_force_recovery = 1
bind-address=127.0.0.1
local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
Lastly when mysqld does start and I try to a mysqldump I get a :innodb_force_recovery = 1
bind-address=127.0.0.1
local-infile=0
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect
Any help appreciated. Thank you in advance.
Drew