core_reputations_index and core_search_index crashes

[Steve Herschbach]

I am having these two tables repeatedly crash, with days or weeks between occurences. Usually they are repairable but in a couple cases were so corrupt they could not be repaired, I needed to use a backup.

I have my provider looking hard at it and they are saying the mysql server was up when this last happened. What I need to know is if there is anything, anything at all in the Invision software that could cause either of these tables to crash? The search index causes few problems and is easily rebuilt. The reputations_index going bad though immediately generates errors across the forum, so it is a big problem right away. I am running 4.7.17 IC with PHP Version 8.1.28 and mySQL Version 8.0.36

Let's say Invision says it can't be the software and the provider (Pair Networks) says it's not them. Typical in these situations at times, we get caught in the middle with no solution. If I shut off Reputations in the settings, will this index be cut out of the loop entirely? I really hate to do that but if I can't get any resolution to this it is my last ditch fallback solution.

Edited June 14 by Steve Herschbach

[Steve Herschbach]

06/14/2024 12:49 AM    template_error    IPS\Db\Exception (144) SELECT `app`, `type`, `type_id`, `member_id`, `rep_rating`, `reaction` FROM `core_reputation_index` ...    The log entry was triggered by a guest (Guest)
9 hours ago

The URL of page the error occurred on was deleted

IPS\Db\Exception::144

SELECT `app`, `type`, `type_id`, `member_id`, `rep_rating`, `reaction` FROM `core_reputation_index`  LEFT JOIN `core_reactions` ON reaction=reaction_id WHERE ( reaction_enabled=1 AND app='forums' AND type='pid' AND ( type_id IN(146373,146362,146327,146298,146292,146288,146271,146253,146208,146151,146135,146130,146121,146058,146054,146051,145963,145924,145905,145812,145779,145776,145758,145742,145489) ) )
Table './XXXXX_dpforum/core_reputation_index' is marked as crashed and last (automatic?) repair failed

[Jim M]

I'm sorry to hear that this is still happening, however, this is definitely the server rather than the software. This is something your hosting provider will need to continue to investigate to find the root cause. These things where it is repeatedly happen could be configuration, resource overload, backup malfunction, corrupt storage, etc... The fact that it is multiple tables is stating it is really something on the server side.

6 minutes ago, Steve Herschbach said:

SELECT `app`, `type`, `type_id`, `member_id`, `rep_rating`, `reaction` FROM `core_reputation_index`  LEFT JOIN `core_reactions` ON reaction=reaction_id WHERE ( reaction_enabled=1 AND app='forums' AND type='pid' AND ( type_id IN(146373,146362,146327,146298,146292,146288,146271,146253,146208,146151,146135,146130,146121,146058,146054,146051,145963,145924,145905,145812,145779,145776,145758,145742,145489) ) )
Table './XXXXX_dpforum/core_reputation_index' is marked as crashed and last (automatic?) repair failed

This is the resulting error of our software attempting to use the table after it crashed, not the cause of the crash.

[Steve Herschbach]

5 minutes ago, Jim M said:

This is the resulting error of our software attempting to use the table after it crashed, not the cause of the crash.

Yeah that's what I think also. Just trying hard here to do my due diligence to eliminate all possibilites with making assumptions about things I only am half knowledgeable in. Thanks Jim.

But since I have you on the horn and to clarify and beat it to death - there is no way a php script can inject something into a database table to cause it to crash?

[Jim M]

2 minutes ago, Steve Herschbach said:

there is no way a php script can inject something into a database table to cause it to crash?

PHP is a wide and vast language that can do many things. Our software though follows best practices. Crashed tables in general are caused more from server-side influences than software influences. With that said, if this was something in the software, you'd hear more complaints from our thousands and thousands of customers 🙂 .

[Steve Herschbach]

27 minutes ago, Jim M said:

PHP is a wide and vast language that can do many things. Our software though follows best practices. Crashed tables in general are caused more from server-side influences than software influences. With that said, if this was something in the software, you'd hear more complaints from our thousands and thousands of customers 🙂 .

And Jim, I am now a fan of your open support system for that exact reason!! 👍🏼

Edited June 14 by Steve Herschbach