vayavalla
(vayavalla)
April 11, 2025, 9:41am
1
I have the following error on one of my instances of openHAB:
Error connecting to the openHAB Cloud instance: pool destroyed. Reconnecting after 60000 ms.
Raspberry Pi 3 - openHAB 4.3.4
On my instance running latest 5.0. Millestone I have no problems connecting to the cloud
Is that a problem on my side or on the cloud server?
uk59821
(Ulf)
April 11, 2025, 9:51am
2
I have the same error on OpenHAB 4.3.2
vayavalla
(vayavalla)
April 11, 2025, 9:55am
3
I noticed it today. Yesterday was working good.
Is it the same for you?
uk59821
(Ulf)
April 11, 2025, 9:56am
4
Yes, I check the service every 15 minutes and the failure is since midnight (MESZ).
pmknowles
(Philip Knowles)
April 11, 2025, 4:43pm
5
Same for me on 4.2.1. Reboot not helped,
status.openhab.org says the Cloud server is up.
uk59821
(Ulf)
April 11, 2025, 5:29pm
6
I don’t know what the status was last week, but I also got the "Internal server error"
information when logging into myopenhab.org .
As far as I understand from @digitaldan , the problem wasn’t entirely clear.
I’m not 100% sure why the error was happening, all of the backend servers were running, and i did not see anything right away in the logs, but i went ahead and restarted the web and proxy clusters. Things should be back to normal in just a few minutes.
1 Like
Alexaas
(Alexaas)
April 11, 2025, 6:23pm
7
Still not working for me.
Not working for me either
vayavalla
(vayavalla)
April 11, 2025, 7:20pm
9
Yes, i also had the same problem that day.
I hope @digitaldan finds the problem
1 Like
rothm
(Roth Mark)
April 11, 2025, 7:53pm
10
Same problem right now, cannot connect using Cloud connector.
Also getting random “Internal Server Error” when login on myopenhab.org .
pmknowles
(Philip Knowles)
April 11, 2025, 8:00pm
11
Rebooted and still says Offline
digitaldan
(Dan Cunningham)
April 11, 2025, 9:39pm
12
Looking now, not sure what the issue is
1 Like
digitaldan
(Dan Cunningham)
April 11, 2025, 9:48pm
14
So one of our servers exhausted is DB pool, but continued to take traffic, so if you were unlucky enough to be pinned to that server by our load balancer, it was failing. I look into failing the server completely when that happens, my guess is this was the cause last time we had an issue as well.
Its also strange that both issues happened within 12 hours of our hosting provider doing emergency maintenance on the hardware serving that node. I’m not sure if they reboot it (which would be the safe choice) , or try doing a live migration (which might be causing issues), but something seems to get it into a really bad state.
4 Likes