前提・実現したいこと
レンタルVPS(conoha VPS)でサイト(kusanagi wordpress)を立ち上げています。
OS:CentOS 8.1(64bit)
本日の5時ごろにサイトを開いてみると「データベースの接続エラー」が出るようになりました。
コンソールで systemctl status mariadb を実行してみると下記のように立ち上げに失敗しております。
/var/log/mysql より mysqld.log を見てみると下記のようになっております。
2020-02-19 14:51:17 140432116258560 [Warning] InnoDB: Difficult to find free blocks in the buffer pool (21 search iterations)! 0 failed attempts to flush a page! 2020-02-19 14:51:17 140432116258560 [Note] InnoDB: Consider increasing the buffer pool size. 2020-02-19 14:51:17 140432116258560 [Note] InnoDB: Pending flushes (fsync) log: 0 buffer pool: 0 OS file reads: 65618 OS file writes: 224618 OS fsyncs: 42428 2020-02-23 5:22:23 140432050747136 [Note] /usr/sbin/mysqld: Normal shutdown 2020-02-23 5:22:23 140432050747136 [Note] Event Scheduler: Purging the queue. 0 events 2020-02-23 5:22:23 140432390461184 [Note] InnoDB: FTS optimize thread exiting. 2020-02-23 5:22:23 140432050747136 [Note] InnoDB: Starting shutdown... 2020-02-23 5:22:24 140432050747136 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool 2020-02-23 5:22:25 140432050747136 [Note] InnoDB: Shutdown completed; log sequence number 27004123939 2020-02-23 5:22:25 140432050747136 [Note] /usr/sbin/mysqld: Shutdown complete 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: The InnoDB memory heap is disabled 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Compressed tables use zlib 1.2.7 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Using Linux native AIO 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Using SSE crc32 instructions 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Initializing buffer pool, size = 768.0M 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Completed initialization of buffer pool 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Highest supported file format is Barracuda. 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: 128 rollback segment(s) are active. 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Waiting for purge to start 2020-02-23 5:22:36 139862322874624 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.45-86.1 started; log sequence number 27004123939 2020-02-23 5:22:36 139862322874624 [Note] Plugin 'FEEDBACK' is disabled. 2020-02-23 5:22:36 139860715239168 [Note] InnoDB: Dumping buffer pool(s) not yet started 2020-02-23 5:22:36 139862322874624 [ERROR] mysqld: Can't change size of file (Errcode: 28 "No space left on device") 2020-02-23 5:22:36 139862322874624 [ERROR] Can't init tc log 2020-02-23 5:22:36 139862322874624 [ERROR] Aborting 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: The InnoDB memory heap is disabled 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Compressed tables use zlib 1.2.7 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Using Linux native AIO 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Using SSE crc32 instructions 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Initializing buffer pool, size = 768.0M 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Completed initialization of buffer pool 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Highest supported file format is Barracuda. 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: 128 rollback segment(s) are active. 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Waiting for purge to start 2020-02-23 5:29:09 140687387695360 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.45-86.1 started; log sequence number 27004123949 2020-02-23 5:29:09 140685776779008 [Note] InnoDB: Dumping buffer pool(s) not yet started 2020-02-23 5:29:09 140687387695360 [Note] Plugin 'FEEDBACK' is disabled. 2020-02-23 5:29:09 140687387695360 [Note] Recovering after a cras2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: The InnoDB memory heap is disabled 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Compressed tables use zlib 1.2.7 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Using Linux native AIO 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Using SSE crc32 instructions 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Initializing buffer pool, size = 768.0M 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Completed initialization of buffer pool 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Highest supported file format is Barracuda. 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: 128 rollback segment(s) are active. 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Waiting for purge to start 2020-02-23 8:13:47 140388475193600 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.45-86.1 started; log sequence number 27004124029 2020-02-23 8:13:47 140388475193600 [Note] Plugin 'FEEDBACK' is disabled. 2020-02-23 8:13:47 140388475193600 [Note] Recovering after a crash using tc.log 2020-02-23 8:13:47 140386869704448 [Note] InnoDB: Dumping buffer pool(s) not yet started 2020-02-23 8:13:47 140388475193600 [ERROR] Can't init tc log 2020-02-23 8:13:47 140388475193600 [ERROR] Aborting
データ容量不足かと思い運営サイトを2サイトほど削除しましたが、解決しません。
どなたか分かる方はいらっしゃいますでしょうか?

回答1件
あなたの回答
tips
プレビュー