SQL error
-
@james sorry of the late response I tried it, and it shows these data
root@CloudronMain:~# cloudron-support --troubleshoot
[OK] node version is correct
[OK] docker is running
[OK] MySQL is running
[OK] nginx is running
[OK] box is running
[OK] unbound is running
[OK] Dashboard is reachable via domain name
[OK] Domain elevatecalls.io is valid and has not expired
root@CloudronMain:~# -
Usually, that error happens when docker became corrupt (for example, server ran out of disk space). Is that a possibility in your case? This is quite an old version of Cloudron. The recent versions of cloudron-support have --recreate-docker but I don't think it's there ins Cloudron 7 . If you write to support@cloudron.io , I can look into it.
-
Usually, that error happens when docker became corrupt (for example, server ran out of disk space). Is that a possibility in your case? This is quite an old version of Cloudron. The recent versions of cloudron-support have --recreate-docker but I don't think it's there ins Cloudron 7 . If you write to support@cloudron.io , I can look into it.
-
I’d like to inform everyone that our current backup takes approximately 3 hours and 45 minutes to complete.
In the event that the server goes down, the full restoration process could take 8–9 hours or possibly longer, depending on the situation.
With this in mind, I would like to ask for your recommendation on how we should proceed. Would it be better to schedule this activity over the weekend to minimize disruption to our employees and clients in case a restore is required?
If we are confident that this will not cause any issues or downtime, we can proceed today.
Please advise on the best course of action.
-
Hello @jcalag
Is this still an issue?
Depending on your hosting provider you might be able to create a server snapshot as an alternative backup method for a fast restoration if something goes wrong.@james Yeah, for now we can only do it in weekend because if we fcked up restoration it's gonna take around 17 hours like last time,
Also maybe you got something we can test or any article we can try to use in the weekend that would be helpful;
Last time we tried updating ubuntu to 22 but these are the error's
"When we update the ubuntu to 22 it shows these error and we tried to update it to 24 to see if it might fix but it still shows the same error."
Errors were encountered while processing:
nginx-core
nginx-common[OK] node version is correct
Docker is down. Trying to restart docker ...
[OK] docker is running
[OK] MySQL is running
[OK] nginx is running
[FAIL] Could not load dashboard website with loopback check -
Hello @jcalag
Is this still an issue?
Depending on your hosting provider you might be able to create a server snapshot as an alternative backup method for a fast restoration if something goes wrong.
