• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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