• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Cant login after VPS crash - SQLSTATE[HY000]: General error: 1030

Steve Pheriche

New Pleskian
Hi, Our VPS fell victim to a bunch of RAID arrays dying. The supplier restored from disaster backups and I've got most things (such as mail, serving http / ssh / ftp, etc.) working via CLI.

But Plesk login is not functioning.

$ df -h /var/tmp reports seems ok
Filesystem Size Used Avail Use% Mounted on
/dev/vda3 147G 77G 63G 55% /


But on attempting login I see this. Any ideas?
lAGfw40.png
 
Make sure that mysql service is up and running. Try to start it and check mysql log for error messages.
 
MySQL is up and running and serving sites.

the SQL log shows an very large number of entries like this

180131 1:52:37 InnoDB: Error: page 15181 log sequence number 5212736526
InnoDB: is in the future! Current system log sequence number 5212619092.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: MySQL :: MySQL 5.5 Reference Manual :: 14.23.2 Forcing InnoDB Recovery
InnoDB: for more information.

I can see that in my.cnf innodb_force_recovery = 5
which is too harsh, and so I'll attempt that =1 (SRV_FORCE_IGNORE_CORRUPT)

Hopefully SQL actually starts again after attempting that. I think it's in a sickly state.
 
Back
Top