Configuration > Notifications = Error

[shawnb61]

I think you're dealing with a set of db corruption issues.

I'd repair all tables.

[a10]

^^^ Will do and report back. Thanks for your time.

[mcmuroni]

I hope there's somehow an easy fix for these issue because I have the same problem. Updated some days ago from 2.019 to 2.1.3. with no error's. That's when the first error logs appears. I'd hope that the 2.1.4 would help but sadly no change. I try to understand your postings put I don't have any experience with databases. But the form seems to work fine expect of these error messages.

[a10]

I hope there's somehow an easy fix for these issue because I have the same problem.

Hi, so as to not confuse (even more :O) this topic, are you having exactly the same errors ("Database Error: The SELECT would examine more than MAX_JOIN_SIZE rows" from the exact same actions (clicking notifications, pm send)?
If not, better to start own topic.

[a10]

I'd repair all tables.

Done, all tables showing ok. Forum works fine, except PM send still producing same errors. And emails still stuck in queue.

As mentionned, this is on my testforum. Situation ftm makes me reluctant towards doing the real update.

Unless some clear solution appears, maybe best to make a new, fresh clone and see how things behave.

[shawnb61]

What happens when you run this query:

Code Select Expand

SELECT id_member, real_name
FROM smf_members
WHERE real_name LIKE 'a%'
AND is_activated IN (1, 11)


[mcmuroni]

Sorry for my post. Its of course not the same error. I will make up a new threat.

[a10]

What happens when you run this query:

Code Select Expand

SELECT id_member, real_name
FROM smf_members
WHERE real_name LIKE 'a%'
AND is_activated IN (1, 11)

SQL query: Copy Documentation

SELECT id_member, real_name
FROM smf_members
WHERE real_name LIKE 'a%'
AND is_activated IN (1, 11) LIMIT 0, 25

MySQL said: Documentation
#1104 - The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay

[shawnb61]

That is a very simple query against your smf_members table.  If you cannot run a simple query like that, SMF has no chance of operating.

Either you have more than 67108864 members, or, your smf_members table is corrupted.

Almost certainly the latter.  Which means that both issues you have had are due to database corruption.  You can try repairing/optimizing the table again.

Database corruption cannot really be caused by SMF.  There is something wrong with your environment, or, something very bad happened during restore.

You can try rebuilding from scratch again.  That would resolve issues if they were related to the restore.  If the errors persist, however, you need to look very closely at your db install & configuration.

[a10]

Seems like.... any member with the name starting with a10, A10 (there are several) produces the PM send error !   Any & all other names tested so far, no errors.

All PM emails are produced, but all ends up stuck in queue.
Only emails that I saw leave the queue was when testing new registrations.

Anyway. Yes, time to pull the plug. Some things were resolved, but it's time to make a new, fresh test environment, as things may have happened during the 2.0.19 to 2.1.3\4 conversions. As a last info, the test forum was on php 8.2, which I think should not matter. The host's setup is trusted, 100% troublefree 2.0.* there for like 12 years.

Thanks for your help, I've learned new stuff along the way so not wasted time.

edit: tested the "SELECT id_member, real_name etc"  on my original 2.0.19 setup, worked fine there so assuming my production forum is in good shape (forum behaves 100% excellent in every detail).

[shawnb61]

If you have host support, have them look into the corruption.

Provide the query above & the results.

This is not an SMF issue.  That simple query fails outside of SMF.