Search Function Issues

[anthony]

I have no idea why the search is suddenly an issue, but it is. I have disabled the current search system, restoring the default MySQL one for the time being, while I work on trying to solve the problem with the, normally, better system.

 

[anthony]

I think I know the answer to this issue... but I am away at present and will implement the previous main version once I return home in a few days. I tried the latest 8.x of ElasticSearch, where I was running 7.x previously. Not sure it is that, but I think that is a good start. Could be an issue moving from NGINX to Apache that I am not aware of, as been using NGINX for a long time now.

 

[anthony]

I am crossing my fingers and toes, what I discovered is that I had the wrong JavaJDK version installed on the server, simply it was using an incompatible version, which makes sense it kept crashing. I am hoping this was the issue and fixes the problem, as ElasticSearch is far superior than MySQL default searching.

 

[anthony]

Ok, fingers crossed. Rebuilt and live.

 

[Charbella]

I am crossing my fingers and toes, what I discovered is that I had the wrong JavaJDK version installed on the server, simply it was using an incompatible version, which makes sense it kept crashing. I am hoping this was the issue and fixes the problem, as ElasticSearch is far superior than MySQL default searching.

I have no idea what that means, but here’s hoping it worked. Now if you need someone to tell you what a recipe is missing, I got ya.

 

[AngelKeeperJ]

Thank you for all you do!!!!!

 

[anthony]

So far, so good. Went to bed, woke up, still working. Taking the small win at this moment. Time will tell. From the error, I think this was the fix... slap myself round for not thinking about JDK compatibility earlier.

 

[Friday]

I have no idea what that means, but here’s hoping it worked. Now if you need someone to tell you what a recipe is missing, I got ya.

Usually, if you click on “your content”, or someone else’s post count, or a few other places that allows one to see your own or someone else’s most recent posts… It generates a list of your/their most recent posts. Lately, that’s shown up as 0/nothing/zip/nada/zilch.

We all navigate the site differently, hence redundancies. For those of us who regularly check our own, or someone else’s most recent posts… it’s been a bit of an

…O.o?!?…

Site upgrades = All things weird & wonderful & WTFO

 

[anthony]

Ok... try try again. After much trial and error, playing around with this, with some changed settings and lots of fairy dust to hope it works this time, the better search is live once again.

 

[anthony]

Ok... chatgpt just rocks for helping find server errors. After a lot of back and forth with it, analysing log files for me, giving me clues for things to find, chatgpt actually believes it found the issue for me, which was Imunify360 that was running on the server, that has an issue with elasticsearch and causes it to stop, then restart, empty itself, away it goes again.

Hoping... that fixed the issue.

 

[anthony]

Nope, still not the issue. Working on it with chatgpt. One issue down, a myriad of other possibilities available, less one.

 

[anthony]

Ok, fingers crossed this time. Seems there were still misconfigured settings... which I have no idea how, but hey... live and learn. Crossing fingers and toes that solved the issue of the index being reset. Found a precedence issue which was exposing a port which could reset the search DB if hit by a bot doing port scans or such. Locked up tighter now.