[Bug] Failed to connect - something went wrong.
Describe the bug
Steps to reproduce the behavior
This seems to happen randomly. Sometimes running stop then start fixes it. It appears to be related to not having internet access on the TH when started? possibly?
Expected behavior
nothing goes wrong. But also that there's a way to recover. We have a way to recover, at the very least that should be documented here. I was told to re-install the TH from scratch and that took HOURS and the error came back almost immediately. Luckily, an ATL knew how to fix it, but the error is cryptic.
Log files
No response
PICS file
No response
Screenshots
No response
Environment
No response
Additional Information
No response
@cecille what was the ATL workaround? cycle start?
ATL workaround is to run stop then start, but also ensure that there is internet access, not just local network access either when start was run or when you first connect to the TH. I wasn't clear on when it was required, and didn't have time to attempt a repro for both cases.
The lack of internet access indeed caused the backend to fail startup when trying to run the prestart.sh script on the initialization.
The PR#184 merged solves this by ignoring the dependencies online search and installing the python wheels directly from files.
The solution will be integrated (in the branch of spring2025) with the PR#521 and this issue may be closed.