Presearch 3Node not showing in Pre Dashboard

[Mik-TF]

This is half-way between a bug and an issue.

The Situation

A ThreeFolder + Presearch user wants to deploy a Pre weblet but it is hard to find a working 3Node with Presearch. The user must deploy on different 3Nodes until one Presearch weblet shows correctly in the Presearch Dashboard.

Here's the link to the forum post on this.

The Feature

The idea would be to add some configurations in the weblet so that the nodes that show for Presearch weblet are 100% compatible with the Presearch dashboard.

User's description of the issue

"I tried to set up several Presearch nodes, and it was unfortunately really tedious because most of the nodes did not show up in the Presearch Nodes Dashboard.

So I had to delete them again and again. Then I tried other ones, in different countries, etc. - in the end I’ve used only “Certified” nodes because they were mostly working, but again not all of them.

I also tried to find and use my uncertified Dell server (that I have in my home) but it wasn’t even available while the server is online all the time.

Some of the certified nodes were working for just an hour, then they suddenly disconnected and did not come back online again. After many tries I’ve found seven which are working for now.

The setup itself was very easy and I liked that, but to find actually working nodes was not really satisfying"

[Mahmoud-Emad]

Still investigating

[Mahmoud-Emad]

After conducting thorough research and testing various scenarios, I've identified the issue. Each farm possesses a public IP similar to a Home Router. If this IP is not being used in any deployment, it can be utilized with Presearch.

However, if this IP is already in use, you'll need to deploy your instance with the public IP option enabled, as illustrated in the screenshot below:

Determining whether an IP is already in use can be challenging, as deployments might be initiated via Terraform or other providers. However, you can identify it by accessing the deployed machine using the provided ssh-key. Upon logging into the running container | docker logs <container_name>, if an error occurs, you'll encounter the following message:

2023-10-16T12:24:00.346Z error: Duplicate IP: This IP Address is already running another Node. Only one Node is permitted per IP Address.

In the absence of errors, you'll observe the following:

2023-10-16T12:18:33.780Z info: Node is listening for searches...

[Mik-TF]

@Mahmoud-Emad Thanks Emad. Nicely done!

So should we add this information in the Presearch docs on the Manual?

Below is a proposition to add in the Presearch docs. Please let me know what you think.

---

Verify if a Presearch workload deployed without a public IP address already has a Presearch workload running

You can do the following to verify if a Presearch workload deployed without a public IP address already has a Presearch workload running.

• SSH into the VM running the Presearch workload

  • ssh root@<VM_IP_Address>
    

• List running containers and identity the Presearch container

  • docker ps
    

• Print the logs of the Presearch container

  • docker logs <Presearch_container_name>
    

• If there is no other Presearch workload running on the 3Node, you will see a similar output:

  • 2023-10-16T12:18:33.780Z info: Node is listening for searches...

• If there is another Presearch workload running on the 3Node, you will see a similar output:

  • 2023-10-16T12:24:00.346Z error: Duplicate IP: This IP Address is already running another Node. Only one Node is permitted per IP Address.

  • If there is another Presearch workload running, you will need to either deploy on another 3Node with a public IP or deploy on another node without a public IP that isn't running a Presearch deployment.

[Mahmoud-Emad]

Good job Mik, yes we should add this information into the Research docs as you mentioned

[Mik-TF]

Thanks for the confirmation @Mahmoud-Emad
The PR is done. I took the opportunity to improve the overall presentation of the Pre docs.

[A-Harby]

Verified,

Docs were updated on PR.

When node is working and showing on Presearch dashboard.

When node isn't showing on Presearch dashboard.