XF 2.2 xf_news_feed

[Alexander.]

Keep getting this error in my serverlog on Bizdustry.
Any ideas on how to debug this one?

• XF\Db\Exception: MySQL query error [1712]: Index xf_news_feed is corrupted
• src/XF/Db/AbstractStatement.php:228
• Generated by: Unknown account
• May 22, 2021 at 5:10 PM

Stack trace​

DELETE FROM xf_news_feed WHERE event_date < ?
------------

#0 src/XF/Db/Mysqli/Statement.php(196): XF\Db\AbstractStatement->getException('MySQL query err...', 1712, 'HY000')
#1 src/XF/Db/Mysqli/Statement.php(77): XF\Db\Mysqli\Statement->getException('MySQL query err...', 1712, 'HY000')
#2 src/XF/Db/AbstractAdapter.php(94): XF\Db\Mysqli\Statement->execute()
#3 src/XF/Db/AbstractAdapter.php(289): XF\Db\AbstractAdapter->query('DELETE FROM `x...', 1613923841)
#4 src/XF/Repository/NewsFeed.php(163): XF\Db\AbstractAdapter->delete('xf_news_feed', 'event_date < ?', 1613923841)
#5 src/XF/Cron/CleanUp.php(173): XF\Repository\NewsFeed->cleanUpNewsFeedItems()
#6 [internal function]: XF\Cron\CleanUp::runHourlyCleanUp(Object(XF\Entity\CronEntry))
#7 src/XF/Job/Cron.php(34): call_user_func(Array, Object(XF\Entity\CronEntry))
#8 src/XF/Job/Manager.php(258): XF\Job\Cron->run(8)
#9 src/XF/Job/Manager.php(200): XF\Job\Manager->runJobInternal(Array, 8)
#10 src/XF/Job/Manager.php(84): XF\Job\Manager->runJobEntry(Array, 8)
#11 job.php(43): XF\Job\Manager->runQueue(false, 8)
#12 {main}

Request state​

array(4) {
["url"] => string(8) "/job.php"
["referrer"] => string(107) "https://bizdustry.com/threads/will-...le-listing-crypto-payment-option.12464/page-4"
["_GET"] => array(0) {
}
["_POST"] => array(0) {
}
}

 

[Mike]

This is database corruption. There is more in depth discussion here:

Finding and fixing InnoDB index corruption

I encountered a new issue yesterday with one of my MySQL 5.5 slave DBs that runs on EC2 in AWS. The DB was created from a snapshot of another slave. The data is correct, but for at least one table a

dba.stackexchange.com

However, you may be able to run the following query to resolve it:

OPTIMIZE TABLE xf_news_feed;

Generally, this sort of DB corruption indicates something happened on the server such as it losing power/being hard restarted or MySQL being terminated without going through it's shutdown routines. If this is a shared server, then you may want to bring this to your host's attention. (If it's a VPS/dedicated server, then it's important to follow expected server management procedures when possible otherwise there are data corruption risks.)

 

[Alexander.]

This is database corruption. There is more in depth discussion here:

Finding and fixing InnoDB index corruption

I encountered a new issue yesterday with one of my MySQL 5.5 slave DBs that runs on EC2 in AWS. The DB was created from a snapshot of another slave. The data is correct, but for at least one table a

dba.stackexchange.com

However, you may be able to run the following query to resolve it:

OPTIMIZE TABLE xf_news_feed;

Generally, this sort of DB corruption indicates something happened on the server such as it losing power/being hard restarted or MySQL being terminated without going through it's shutdown routines. If this is a shared server, then you may want to bring this to your host's attention. (If it's a VPS/dedicated server, then it's important to follow expected server management procedures when possible otherwise there are data corruption risks.)

Thank you Mike.
I’ve paid for a custom installation to have this issue fixed, along with the board url misconfigration.
please let me know in the ticket if further information is required.
We’re running on a vps

 

[Alexander.]

This is database corruption. There is more in depth discussion here:

Finding and fixing InnoDB index corruption

I encountered a new issue yesterday with one of my MySQL 5.5 slave DBs that runs on EC2 in AWS. The DB was created from a snapshot of another slave. The data is correct, but for at least one table a

dba.stackexchange.com

However, you may be able to run the following query to resolve it:

OPTIMIZE TABLE xf_news_feed;

Generally, this sort of DB corruption indicates something happened on the server such as it losing power/being hard restarted or MySQL being terminated without going through it's shutdown routines. If this is a shared server, then you may want to bring this to your host's attention. (If it's a VPS/dedicated server, then it's important to follow expected server management procedures when possible otherwise there are data corruption risks.)

I'll let Brogan or one of the other developers handle this in the custom installation request.

 

[Paul B]

Just to clarify, resolving database corruption is outside the scope of support.

That's something you, your sysadmin, or host will have to resolve.

 

[Alexander.]

Just to clarify, resolving database corruption is outside the scope of support.

That's something you, your sysadmin, or host will have to resolve.

Ok, but you can fix the board URL problem by re uploading the files with the custom installation?