Derek Zeanah
Member
Last week I was out of town.
The power company replaced my power pole, bringing my servers down for longer than my UPS could endure.
When starting back up, I discovered my MariaDB version was one of three that had a bug reading the (forget what it's called) intent log to prune the database of unclean transactions.
Rather than reverting to the previous night's backup and losing a day's worth of posts, I deleted the ib_logfile1 and ib_logfile2. This required recreating some tables as indexes were off, but all seemed well.
Now I have three problems:
1) Elasticsearch is throwing errors about "text field is not optimized...". That's another thread.
2) I have a user who can log in, but gets "An unexpected database error occurred. Please try again later." whenever he tries to enter a subforum or search new posts.
3) I turned on the MySQL error log while diagnosing the second problem, and it's full of these ugly lines:
At this point I'm wishing I'd taken the backup option and given up on a day's worth of posts, but we are where we are.
Is there a simple solution to this problem? Or is it simplest to just perform a mysqldump, drop the database, and recreate it?
The power company replaced my power pole, bringing my servers down for longer than my UPS could endure.
When starting back up, I discovered my MariaDB version was one of three that had a bug reading the (forget what it's called) intent log to prune the database of unclean transactions.
Rather than reverting to the previous night's backup and losing a day's worth of posts, I deleted the ib_logfile1 and ib_logfile2. This required recreating some tables as indexes were off, but all seemed well.
Now I have three problems:
1) Elasticsearch is throwing errors about "text field is not optimized...". That's another thread.
2) I have a user who can log in, but gets "An unexpected database error occurred. Please try again later." whenever he tries to enter a subforum or search new posts.
3) I turned on the MySQL error log while diagnosing the second problem, and it's full of these ugly lines:
2021-08-13 17:51:55 1746 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-13 17:51:58 1759 [ERROR] InnoDB: Page [page id: space=151, page number=590147] log sequence number 360763163706 is in the future! Current system log sequence number 351420383549.
2021-08-13 17:51:58 1759 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-13 17:51:58 1759 [ERROR] InnoDB: Page [page id: space=151, page number=590552] log sequence number 369413922496 is in the future! Current system log sequence number 351420383549.
2021-08-13 17:51:58 1759 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-13 17:51:58 1759 [ERROR] InnoDB: Page [page id: space=151, page number=590568] log sequence number 369413922496 is in the future! Current system log sequence number 351420383549.
2021-08-13 17:51:58 1759 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-13 17:52:00 1765 [ERROR] InnoDB: Page [page id: space=55, page number=3134] log sequence number 371107525247 is in the future! Current system log sequence number 351420396581.
2021-08-13 17:52:00 1765 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
At this point I'm wishing I'd taken the backup option and given up on a day's worth of posts, but we are where we are.
Is there a simple solution to this problem? Or is it simplest to just perform a mysqldump, drop the database, and recreate it?
