surrealdb stuck at healthcheck after redeploy
wanted to update but got stuck
Solution:Jump to solution
switching to the old engine works fine after redeploy (lost all data thought)
16 Replies
Project ID:
24072d40-de6b-4ee2-aba6-1972eba9f5c524072d40-de6b-4ee2-aba6-1972eba9f5c5
unlike last time, I didn't move volume around, just simply redeploy cause I saw ping at surrealdb discord that there's an update that have bugfix (which I encounter some) 🥲
for support concerning surrealdb please reach out to the surrealdb devs or community as we are unable to provide support for 3rd party software
I'm using the template, could you check what's causing the heath check failed for me? cause I don't see any useful log
from looking at your service, the health check failed because surrealdb exited
checked surrealdb side they say it need to point to localhost:8000, can I add the port at the healthcheck path? Is it default point to localhost?
this has nothing to do with localhost, surrealdb has exited, check your logs and you will see this
this is all my log
please read the last log
u mean the last line? it's 5mins after, where healthcheck failed
surrealdb never started so the health check timed out after 5 minutes
I see, where can I check the config of a template without deploy a new one?
seems like it's the problem of the db store engine, didn't know the template was using a wip engine
Solution
switching to the old engine works fine after redeploy (lost all data thought)
awesome, glad you found the issue