Server Error (500) cannot access admin panel and WordPress Error establishing database connection

Support and Discussion General Discussion
, ,
1

please help

image
image1440×900 143 KB

2

Welcome and Happy New Year @mugi

You need to check if mariadb service is running

service mariadb status || systemctl status mariadb

Which server os are you running ?

3

image
image1440×900 166 KB

4

Show us the results of command nano /var/logs/mysql

Kindly copy paste as some details might be left off your small window.

5

no file directory

6

Check this post How to check database logs - #2 by josephgodwinke

7

2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
2023-02-22 10:51:38 1 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace wbno_wbnovel/wpwa_actionscheduler_claims page [page id: space=238, page number=3]. You may have to recover from a backup.
Warning: Memory not freed: 136833352