SQL error

[jcalag]

Tried updating cloudron and we got this error
SQL is not runinng:

(HTTP code 500) server error - Cannot restart container mysql: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/yellowtent/platformdata/mysql" to rootfs at "/var/lib/mysql": mount /home/yellowtent/platformdata/mysql:/var/lib/mysql (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

Our version:

v7.7.2 (Ubuntu 20.04.5 LTS)
VendorLinode
ProductCompute Instance
CPU16 Core "AMD EPYC 7542 32-Core Processor"
Memory33.66 GB RAM & 4.29 GB Swap
storage 600+
storage used: 400+
Kernel: We tried 5.4, 5.10 and 5.15

[robi]

You might need some updates, friend.

[james]

Hello @jcalag

Please ssh into your server and run cloudron-support --troubleshoot and post the output here.

[jcalag]

@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:~#

[joseph]

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.

[jcalag]

@joseph said in SQL error:

support@cloudron.io

I sent an email on support@cloudron.io please check

[joseph]

@jcalag I think I have replied to your email.

[jcalag]

@joseph

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.

[jcalag]

also just to add, the last time this cloudron was updated was on july 2024

[james]

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.

[jcalag]

@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

[jcalag]

@james maybe you got something that could help us in the weekend sorry I can't give much details because we already restored it.

[james]

Hello @jcalag
If you have an active cloudron subscription you can contact support@cloudron.io.
When you have a restored state, which is failing on cloudron-support --troubleshoot that is where you should send the mail so we can have a look.

[jcalag]

@james Hello james we can only do troubleshooting in weekends if you got time in weekend maybe I can give you access to the server.

But I just saw this blog https://forum.cloudron.io/topic/14045/services-and-all-apps-down-due-to-cgroups-error/7?_=1771850781969 it has the same issue with us and you guys fixed it maybe you can give me some details on how it was fixed maybe I can do it if you guys are not available in weekend.

[girish]

@jcalag did you get this sorted out? Unfortunately, we don't provide this kind of support (troubleshooting over weekends). But if you write to support@ , we can look into your server.

[jcalag]

@girish yeah did found a solution,

I only did recreate container before updating and it fixed the mysql issue.