• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 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