• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question ERROR Plesk Exception Database

PatriceA

New Pleskian
Server operating system version
Centos 7
Plesk version and microupdate number
18.0.68
Hi,
Impossible to login to plesk from login_up.php

Internal errorError: ERROR: Plesk\Exception\Database: DB query failed: SQLSTATE[HY000]: General error: 1030 Got error -1 from storage engine, query was: INSERT INTO `sessions` (`sess_id`, `type`, `login`, `ip_address`, `login_time`, `modified`, `lifetime`) VALUES (?, ?, ?, ?, ?, ?, ?) (Mysql.php:79)

Do you have a solution or a procedure?
 
Hi, @PatriceA . The first thing I would recommend checking is whether there's available space left on the server. Through Plesk UI > Tools & Settings > Info and Statistics. Through the command line:

Code:
df -h
 
Hi @Sebahat.hadzhi , thanks you, I have this response to df -h

Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 74M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/md3 1.9T 297G 1.6T 16% /
/dev/md2 1019M 185M 834M 19% /boot
tmpfs 3.2G 0 3.2G 0% /run/user/0
 
Thank you for the confirmation. Another reason for the issue might be InnoDB corruption - could you please check what's been logged at /var/log/mariadb/mariadb.log?
 
Back
Top