Cloudron Forum

I am generally not in the group of AI = bad, however it likely just lacks lots of knowledge about the Cloudron internals, which make recommendations often not very useful in this area (yet). Overall I am still not sure based on this thread why DNS was involved here and given that you hit 3 different addons with apparently diverse issues, maybe something unrelated to them individually caused the trouble. We will add a few more helpers to the cloudron-support script for the future, to hopefully get down to such issues faster. If you haven't deleted the server yet, maybe we could take a closer look via SSH, since you already invested much time in debugging. If you want that, please enable remote ssh support and send a mail to support@cloudron.io with your Cloudron details.

Turns out the mysql service wasn't starting, not too clear what the root cause was, but rebuilding it made it work again.

Ok, it seemed running the /home/yellowtent/box/setup/start.sh to trigger the migration after restoring the database (because of the ERROR 1046 (3D000) at line 22: No database selected i needed to add these two lines to the dump file: CREATE DATABASE box; USE box; Then it was able to backup the database and run the migration.

I guess that is solved via https://forum.cloudron.io/post/95877

Yep, as usual. It's user error. I was using the box config backup. I just had to adjust the backup path to point to the app. I figured out the correct path by logging into my Backblaze dashboard, browsed through the bucket (by date) and the file "name" is your path. Copy/paste into the import box along with the box settings and voila!

This was sorted out in support.

@joack said in Cloudron partial install but server seems active: I tried installing it on my recently updated ubuntu20.04 desktop As others warned, don't do this! It's not meant to be run this way. You can create a VM on your desktop and install it in the VM though. The error itself is happening because you probably are using MySQL already and this is conflicting with Cloudron installation.

@jonslab did you find what it was?

Closed due to inactivity

@cleveradmin OK, I reread your original post and understood now. You are offering your setup as a way to understand how to recover MySQL which is in some indeterminate state. In general, we don't attempt to recover databases unless it's super crucial. It's almost always just easy to recover from a backup and we also don't support setups with no backup. (IMO, MySQL recovery is very complicated and kind of arcane. Fixing one issue leads to another and it can take days really. So, not worth the effort.)

@girish haha true, just wanted to throw that in there

I have given these stable IPs now - https://git.cloudron.io/cloudron/box/-/commit/582994b9d646989b42e27dde1ae0c27bbb964834

@natzilla Ah ok, I think I will improve the docs to say how to exactly recover if mysql is not even running. The troubleshooting guide assumes mysql is running but corrupt.

Closed due to inactivity

@harrowsmith can you run docker network inspect cloudron to see if the network it tries to bind on is actually created?

@necrevistonnezr I wasn't aware of the setting, good to know.

Also, see https://forum.cloudron.io/topic/3237/remote-sql-support-on-a-per-app-basis?_=1652377131316 on how one can connect with a SSH tunnel.

(please read warning in above comment before following instructions below). If you want to make config file changes: docker exec -ti mysql /bin/bash Edit /run/mysql/my.cnf as needed supervisorctl restart mysql It is important to note that the changes to config files are not persistent across container restarts and server reboot. In general, we have not envisioned Cloudron as a development environment, but we do have many devs using it as such. So, if there is interest, maybe we need to improve things for such use cases.

@iamthefij Ok. Just restored matomo from backup again and it's all good.

I put some docs on how to fix the mysql addon here - https://docs.cloudron.io/troubleshooting/#mysql-addon . It's not "complete" but it's very hard to write those docs since there's a lot of things that can go wrong with mysql....