• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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 Broken after reboot

BrinsleyP

Regular Pleskian
Hello to every

In my server DEBIAN 10 after reboot the server crash the MariaDB 10.3 and i cant repair.

when i try plesk repair db the console return

DB query failed: SQLSTATE[HY000] [2002] No such file or directory
exit status 1

in prints i see some error but cant repair.


01.png

02.png

03.png

04.png

05.png

So how to fix this ?
 
Supose that you can't use plesk repair db if your database server is down, you need to review why your db server is down, can you give us information about your mariadb log?
 
Supose that you can't use plesk repair db if your database server is down, you need to review why your db server is down, can you give us information about your mariadb log?
2021-06-29 10:13:59 0 [Note] InnoDB: Using Linux native AIO 2021-06-29 10:13:59 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2021-06-29 10:13:59 0 [Note] InnoDB: Uses event mutexes 2021-06-29 10:13:59 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-06-29 10:13:59 0 [Note] InnoDB: Number of pools: 1 2021-06-29 10:13:59 0 [Note] InnoDB: Using SSE2 crc32 instructions 2021-06-29 10:13:59 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2021-06-29 10:13:59 0 [Note] InnoDB: Completed initialization of buffer pool 2021-06-29 10:13:59 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2021-06-29 10:13:59 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2021-06-29 10:13:59 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2021-06-29 10:13:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2021-06-29 10:13:59 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2021-06-29 10:13:59 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2021-06-29 10:13:59 0 [Note] InnoDB: 10.3.29 started; log sequence number 215420064140; transaction id 72275874 2021-06-29 10:13:59 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2021-06-29 10:13:59 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-06-29 10:13:59 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded 2021-06-29 10:13:59 0 [Note] Recovering after a crash using tc.log 2021-06-29 10:13:59 0 [Note] Starting crash recovery... 2021-06-29 10:13:59 0 [Note] Crash recovery finished. 2021-06-29 10:13:59 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 2021-06-29 10:13:59 0 [Note] Server socket created on IP: '127.0.0.1'. 2021-06-29 10:13:59 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist

These lines repeat in a loop on log...
 
What kind of reboot did you run? This behavior looks more like someone pulled the power on the instance lol.
 
Back
Top