Elasticsearch errors in System Logs / on fronted, default setup doesn't work?!

[Miso]

Ok, here's what's happening on our setup (Elasticsearch 7, MariaDB 11.4, PHP 8.3 while testing on 8.1 and getting the same results)... on the front-end we are getting this error for any search conducted on the forum:

TypeError: array_map(): Argument #2 ($array) must be of type array, null given (0)
#0 /home/domain/public_html/forums/system/Content/Search/Elastic/Query.php(1315): array_map(Object(Closure), NULL)
#1 /home/domain/public_html/forums/applications/core/modules/front/search/search.php(760): IPS\Content\Search\Elastic\_Query->search('digital', NULL, 17, 'or')
#2 /home/domain/public_html/forums/applications/core/modules/front/search/search.php(126): IPS\core\modules\front\search\_search->_results()
#3 /home/domain/public_html/forums/system/Dispatcher/Controller.php(118): IPS\core\modules\front\search\_search->manage()
#4 /home/domain/public_html/forums/system/Dispatcher/Dispatcher.php(153): IPS\Dispatcher\_Controller->execute()
#5 /home/domain/public_html/forums/index.php(13): IPS\_Dispatcher->run()
#6 {main}

 

and in the backend it shows that + the backtrace:
 

#0 /home/domain/public_html/forums/init.php(1049): IPS\_Log::log('TypeError: arra...', 'uncaught_except...')
#1 [internal function]: IPS\IPS::exceptionHandler(Object(TypeError))
#2 {main}

 

Any idea what's happening here and how to fix this?

 

[Marc]

Please could I confirm you are running at least 7.2.0?

[teraßyte]

PHP 8.3 is not supported, so you should really revert to PHP 8.1 anyway.

[Miso]

4 hours ago, teraßyte said:

PHP 8.3 is not supported, so you should really revert to PHP 8.1 anyway.

As I noted in the original post, both 8.1 and 8.3 produced the same result/error, so I highly doubt the PHP version has anything to do with this problem.

What I do suspect is that it has something to do with the Invision Board code, as per some other posts on this topic where Invision team has admitted that similar errors were caused by bugs in the current Invision code, and they fixed them at some point. I have a feeling this is one of those bugs that they didn't foresee or anticipate either...

 

p.s. Even though 8.3 is not "officially" supported, Invision Board works perfectly fine on it and we haven't seen ANY issues on 8.3, so there's that.

 

[Jim M]

5 hours ago, Marc said:

Please could I confirm you are running at least 7.2.0?

My colleagues question here looks to have been missed. Are you running ElasticSearch at least 7.2.0?

[Miso]

19 minutes ago, Jim M said:

My colleagues question here looks to have been missed. Are you running ElasticSearch at least 7.2.0?

Yes, literally installed the latest v7 (7.17 I believe?) yesterday from the 7.* repo.

https://prnt.sc/KMY_dtm1EaZm

Edited November 25 by Miso

[teraßyte]

3 hours ago, Miso said:

p.s. Even though 8.3 is not "officially" supported, Invision Board works perfectly fine on it and we haven't seen ANY issues on 8.3, so there's that.

No, it does not. While the error you posted happens with both versions, there is still a difference in the end. You may not notice it immediately, but some things are most likely not working as they should.

 

For example, at some point, many people reported issues upgrading to a newer version, and they were all using PHP 8.2+. Switching back to PHP 8.1 allowed them to upgrade without issues. You might see it working, but it's not fully working at 100%.

[Miso]

10 minutes ago, teraßyte said:

No, it does not. While the error you posted happens with both versions, there is still a difference in the end. You may not notice it immediately, but some things are most likely not working as they should.

 

For example, at some point, many people reported issues upgrading to a newer version, and they were all using PHP 8.2+. Switching back to PHP 8.1 allowed them to upgrade without issues. You might see it working, but it's not fully working at 100%.

Well, we've gone through half a dozen upgrades just fine on 8.3, without a single issue, and haven't seen anything or haven't had anything reported over the last few months on 8.3 from users or admins, so I'll assume it's working just fine until proven otherwise and until we see some sort of issues with the board on 8.3.

You might say it's not working 100%, but unless you can point out some specifics that aren't working properly on 8.3 I'll stick with our assumption and 8.3, thank you very much.

Anyway, back to this Elasticsearch issue instead... which, I mentioned, happens in exact same way on PHP 8.1 and 8.3, so it's not PHP related, that's for sure.

Edited November 26 by Miso

[Marc]

7 hours ago, Miso said:

Well, we've gone through half a dozen upgrades just fine on 8.3, without a single issue, and haven't seen anything or haven't had anything reported over the last few months on 8.3 from users or admins, so I'll assume it's working just fine until proven otherwise and until we see some sort of issues with the board on 8.3.

You might say it's not working 100%, but unless you can point out some specifics that aren't working properly on 8.3 I'll stick with our assumption and 8.3, thank you very much.

Anyway, back to this Elasticsearch issue instead... which, I mentioned, happens in exact same way on PHP 8.1 and 8.3, so it's not PHP related, that's for sure.

Please feel free to use 8.3 if you would like. However please bear in mind we are unable to issue support while you are using that version. As mentioned above, we do not support PHP 8.3

[Miso]

28 minutes ago, Marc said:

Please feel free to use 8.3 if you would like. However please bear in mind we are unable to issue support while you are using that version. As mentioned above, we do not support PHP 8.3

Ok, so if I flip it over to 8.1 and you assume that we're on 8.1 from here on, can you help with this issue then?

 

[Marc]

17 minutes ago, Miso said:

Ok, so if I flip it over to 8.1 and you assume that we're on 8.1 from here on, can you help with this issue then?

 

Yes, we can assist if you are using versions of items we support, of course. 

[Miso]

37 minutes ago, Marc said:

Yes, we can assist if you are using versions of items we support, of course. 

Ok, so how do we go about it and where do we go from here?

[Marc]

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. 

We look forward to further assisting you. 

 

[Miso]

26 minutes ago, Marc said:

We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. 

We look forward to further assisting you. 

 

Updated the FTP access details. Forum admin details shouldn't have changed at all, so those should be good to go.

[Marc]

Things look to work fine when all 3rd party items are disabled on your site. Unfortunately this appears to be one of your 3rd party items. Its worth noting also that your server appears to be very very slow at present

[Miso]

31 minutes ago, Marc said:

Things look to work fine when all 3rd party items are disabled on your site. Unfortunately this appears to be one of your 3rd party items. Its worth noting also that your server appears to be very very slow at present

Ok, good to know. We'll troubleshoot those one by one then, to see which one is the offending one.

That's somehow the effect of Elasticsearch running the indexing in the background... not sure how to deal with that - do you have any suggestions on what sort of settings to use for Elasticsearch to improve that?

And the actual reason why we are trying to use Elasticsearch is because when we use MySQL engine for search index, some of the user accounts have their "My Feeds -> Content I Follow" feeds empty, even though there should be quite a few feeds and content in there, and we can't figure out why this is happening. It's not likely that mySQL index is skipping the exact same users every time we run it... when we switch to Elasticsearch that content shows up just fine for specific users, but in mySQL it doesn't. But then again, if Elasticsearch indexing will be this straining on the server...  

Edited November 26 by Miso

[Marc]

You would really need to speak to your hosting company on elasticsearch taking up so many resources, if that is the case. We cant really advise on server setup, as we dont know the specifics of your servers setup

[Miso]

5 minutes ago, Marc said:

You would really need to speak to your hosting company on elasticsearch taking up so many resources, if that is the case. We cant really advise on server setup, as we dont know the specifics of your servers setup

Well, let's try this - can we troubleshoot this issue with mySQL not indexing/showing some of the user accounts' "My Feeds -> Content I Follow" and shows them empty, even though they should have content (as shown once we switch over to Elasticsearch and from testing with known users who follow tons of specific feeds on the forum)?

That way we won't have to deal with Elasticsearch at all - and I'd rather not deal with something we aren't familiar with using or configuring and something that will be bogging the server down anyway. MySQL has been working out great and the search results are instant, really... except for this issue of missing feed content for certain users. 

[Marc]

You would need to switch back, and reindex in order for me to take a look at that and see whats happening. Once you have, I would need an example user 

[Miso]

3 minutes ago, Marc said:

You would need to switch back, and reindex in order for me to take a look at that and see whats happening. Once you have, I would need an example user 

Ok, reindexing is at 42%. Should be done within the hour or so.

Did you want me to post the username here or PM you or...? I don't mind either.

[Marc]

Post here if you dont mind either way please

[Miso]

Sure. 

Re-index is done, and the user in question is "kdokoza".

Once logged in as that user, on Elasticsearch it showed tons of feeds under "Content I Follow", in mySQL it doesn't show any for some reason, just to mention again.

 

Edited November 26 by Miso

[Marc]

Ah I see what the issue is there. Standard search on streams will do the last 365 days. You get more if using elasticsearch. 

[Miso]

17 minutes ago, Marc said:

Ah I see what the issue is there. Standard search on streams will do the last 365 days. You get more if using elasticsearch. 

Can that be changed/tweaked in settings somewhere, somehow?

[Miso]

Actually, I need some clarification on what you mean by that "standard search on streams will do the last 365 days", because this specific user is very active on the forum and she's had plenty of recent content (within this week, let alone the last year) that should be showing in there, so I assume you're saying that the account doesn't show any streams in the last 365 days? 

Which would be wrong, because it should, as that user was the one who raised this as a concern, since she uses that feed to interact with other users on the forum regularly, so those threads would definitely have recent content and that feed would definitely be filled up with content... so it might be something else in play?

Just asking, as I don't really know from my point of view as I can't look under the hood of that software (I mean, I could, but it will take me forever to follow the trail down to some sort of a clue and figure out what's happening).