Cloudron Forum

@berryd great you sorted it out!

@jtippetts atleast the dashboard seems up now. Not sure why the machine shutdown itself though.

@mpeterson0418 I found that the root file system was either corrupt or "reset" . I don't know and unable to guess what happened to the disk (maybe power outage?), but I can explain what I did to recover.

I found host MySQL to be empty. The box database had tables but was empty. The fact that it had tables meant that migration scripts were run on this . Maybe /home/yellowtent/box/setup/start.sh was run at some point on an empty (i.e no tables even) database.

Usually, the last well known mysql dump is located /home/yellowtent/boxdata/box/box.mysqldump . One can also find the same inside the latest backup (inside the box.tar.gz) . To "restore", mysql -uroot -ppassword < /home/yellowtent/boxdata/box/box.mysqldump

Then I found, docker won't start. In Cloudron, containers are throw away infrastructure since data is stored outside the containers. I tried cloudron-support --recreate-docker but this did not work. On investigating further, it seems /var/lib/containerd was also corrupt . Corrupt here means no docker commands work. So, I removed that directory as well. After that, cloudron-support --recreate-docker worked.

The best way to migrate in Cloudron is not to do the above but instead just restore from backups. See https://docs.cloudron.io/backups/#move-cloudron-to-another-server .

@joseph Thank you and yes, did all those, and was in communication with tech support. The issue is actually mysteriously resolved and I'm just trying to figure out what happened so I can share that in this thread and hopefully avoid repeating this issue in the future.

you can check it your self with GRC shields up
https://www.grc.com/x/ne.dll?bh0bkyd2

Thank you @girish , this worked.

For those coming through in the future note that cloudron-support may ask you to reboot and run again, keep an eye out for it.

I didn't uncover the cause, but I believe it was related to the VM running out of disk space. I wound up reinstalling.

I let a large upload job run unattended and wound up completely filling the drive on the VM running Cloudron. I then cleared about 100 GB, rebooted for good measure, resized the partition using parted, expanded the filesystem, rebooted again, and let it run normally for a few days. That's when I noticed I couldn't install any new apps. I suspect that either the partition / filesystem resize or the disk being full broke something internally.

In hindsight I wish I had taken the time to dig into the logs a little more and see what was happening. But this is likely a direct result of my unusual environment fault.

@girish Yes 🙂 Everything is back to normal. Thanks a lot !!!

Thank you very much @girish, you rock!

Yes you are right, the host has it installed. I tried it from a terminal within one of our apps. There it probably would be overkill.

The issue here was DNS related. my.domain.com was not pointing to the public IP.

Yes I think so can confirm it works thank you.
image.png

@girish Are you saying that the user manually updated the node version, which I assume is the one that Cloudron that installed, and it installed that version so that it works, but then had this issue because they did something that they aren't advised to do (which is manually update)???

It might be worthwhile to highlight the fact (on the homepage or in the install instructions) that Cloudron manages the VPS for the user so that new users don't keep doing this, _running apt-get update on their own!

@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.)

@DAMO11-coder see https://docs.cloudron.io/troubleshooting/#expired-domain

@Nozy said in Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003:

the gm docker still is not remove

If you click on the app icon, it will show you the error as to why it's not uninstalling.

@jjhill Can you check if nginx is running ? See https://docs.cloudron.io/troubleshooting/

Hi, brilliant - that was the solution

thank you so much
kr, Andreas

@girish said in Forgot primary domain:

cloudron-support --admin-login

@jdaviescoates you could set up a cron that gets usage info, and prints out a webpage you can monitor with Kuma for a keyword. When a threshold is met, you add/remove the keyword and fire off an alert via TG.

Similar for monitoring something with change detection app or n8n workflow.