24 days ago
Hello! After yesterday's crash i tried many things to deploy my NocoDB server and i can't.
It always crashes.
Can someone help me resolve this as soon as possible, because we use it for work.
61 Replies
24 days ago
Did you deploy a template or is this a custom service?
24 days ago
(refering to NocoDB)
But this is very old for 1 year it was working perfect and from yesterday because it crashed i cant deploy it again
Attachments
Attachments
24 days ago
Ah I see, in that case you can go to the template you deployed and on the right you can select Get template help, this will request help from the template author (since this seems to be an issue with the template having broken or something)
Attachments
24 days ago
ooh that doesn't look good
24 days ago
i dont know much (or anything for that matter) about NocoDB unfortunately so I can't help much here 🥲
24 days ago
yea someone who knows more about NocoDB might jump into this thread hopefully
24 days ago
in the mean time I have one idea
24 days ago
can you send a screenshot of the top of your settings of the nocodb service?
Attachments
I saw nocodb had update yesteraday and im trying to deploy with the latest version but still it crashes
24 days ago
oh so you edited the source image?
24 days ago
my theory was it was on the latest tag, and so upon redeploy it deployed a new version which might've not been compatible with the previous version causing the crash loop
Should i deploy from backup?
Attachments
24 days ago
oh neat, and yes, if i were in your shoes I'd find the version it was on before it started crashing
24 days ago
those only backs up the volume content, not the service settings or deployment environment
24 days ago
you'll want to see what date and time your last healthy deployment went out, use that to find what the latest version at the time was and then move back to that version
24 days ago
if you got it back on an the same version it used to be and it still crash loops then I'd recommend restoring a backup (cause the new version might've made the files unreadable for the old version, potentially)
Attachments
24 days ago
yea, just find what version was latest 11 months ago
24 days ago
exactly
24 days ago
alright! hopefully that works
Here is something strange
Attachments
Attachments
24 days ago
was yesterday's backup made on the newer version?
24 days ago
the newer version must've made huge changes to how storage works, as for how it got to 3.4gb is beyond me
So i rolledback the nocodb version , mounted the old storage and it says "online" but still its not accessible.
Attachments
24 days ago
any errors in logs?
tried deploying with the new volume but gave error. Now trying to deploy again with the old volume and it gives error...
24 days ago
so upon deploy it had no errors, then the next deploy with that volume it got errors again?
Now its online
Attachments
24 days ago
that service is in a very unstable state wow
24 days ago
are you sure that is the correct version?
24 days ago
then I'm out of ideas
Attachments
24 days ago
that is some odd ordering 🤨
24 days ago
probs just a UI issue
network is not started so thats why i cant connect.. anyway i will update if i find a solution
24 days ago
your serivce has healthcheck endpoints, I don't think it'd start if the network wasnt working
24 days ago
well, i guess considering your service is inaccessible, those healthchecks arent doing their job 😓
24 days ago
unless you removed the healthcheck endpoints
I fixed the issue .
Redeployed brand new nocodb. And just replaced the variables so its connected to the original database
24 days ago
Nice! Glad you got it working
Status changed to Solved dev • 24 days ago