SEEK Upgrade - Seeking Assistance for Persistent Search Service Unavailability

[mbd hki]

Hello Seek Developers,

I trust this message finds you well. I'm reaching out regarding a persistent issue encountered during the SEEK upgrade process within our Dockerized environment.

SEEK Version: 1.13

Despite following the documented upgrade procedures, the search service consistently remains unavailable, leading to a critical 503 status code. The error messages indicate a connection problem with SOLR:


ERROR - RSolr::Error::ConnectionRefused (Connection refused - {... details ...})
...
method=GET path=/assays format=html controller=AssaysController action=index status=503 duration=145.80 view=5.29 db=8.44 time=12969819.77 user_agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Investigation Steps:

    Confirmed SOLR service is running.
    Verified SOLR configuration.
    Examined relevant logs without identifying a solution.

Your insights and guidance on resolving this persistent search service unavailability are highly appreciated.

Thank you for your valuable assistance.

Kind Regards,
Khaled

[Finn Bacall]

Hi Khaled,

Just to confirm - you are running SEEK via docker-compose and have a container running Solr?

If so, have you tried recreating the Solr container and it's volume (seek-solr-data)?

Thanks,

Finn

On 24/01/2024 13:10, mbd hki wrote:

Hello Seek Developers, I trust this message finds you well. I'm reaching out regarding a persistent issue encountered during the SEEK upgrade process within our Dockerized environment. SEEK Version: 1. 13 Despite following the documented upgrade

ZjQcmQRYFpfptBannerStart

This Message Is From a New External Sender

You have not previously corresponded with this sender. Please exercise caution when opening links or attachments included in this message.

 

ZjQcmQRYFpfptBannerEnd

--
You received this message because you are subscribed to the Google Groups "SEEK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to seek-develope...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/seek-developers/2efcaef4-ce69-4d0d-b565-0ba8ceed8f3en%40googlegroups.com.

[mbd hki]

Hello Finn,

Thank you for your prompt response.

Yes, I can confirm that I am running SEEK via docker-compose, and the Solr container is indeed running. I have attempted to resolve the issue by recreating both the Solr container and its associated volume (seek-solr-data). Unfortunately, this did not alleviate the problem.

Furthermore, in my efforts to troubleshoot, I recreated all Docker images and their volumes associated with SEEK. Despite these attempts, the search service remains consistently unavailable, and both the 503 status code and Connection refused log error persist.

I also took the additional step of recreating the entire docker-compose setup to ensure the integrity of the configuration. However, the issue still persists.

Any further guidance or insights you can provide would be greatly appreciated.

Kind regards,
Khaled