Cloudron Forum

@girish Realized I already asked about a timeout on my old account. I think I am just running into that again now.

@girish Automatic backups are also failing for me, so would this fix not address it? I am doing another run now with significantly reduced concurrency.

@imc67 Are you using rsync?

@girish It was already at 40GB but I increased it to 64 and reduced the concurrent uploads. It does seem to be crashing when uploading very large files. Does it need to store the entire file its uploading in memory or does it break large files into parts? I don't understand if the multi part upload size is used for rsync also or just tgz backups.

@girish Thanks but that doesn't quite remove all the gnome stuff that the Cloudron installer installed. The following and their dependencies are still installed, might be more also.

gnome-control-center-data/focal-updates,now 1:3.36.4-0ubuntu2 all [installed,automatic]
gnome-control-center-faces/focal-updates,now 1:3.36.4-0ubuntu2 all [installed,automatic]
gnome-control-center/focal-updates,now 1:3.36.4-0ubuntu2 amd64 [installed,automatic]
gnome-desktop3-data/focal-updates,now 3.36.8-0ubuntu1 all [installed,automatic]
gnome-keyring-pkcs11/focal,now 3.36.0-1ubuntu1 amd64 [installed,automatic]
gnome-keyring/focal,now 3.36.0-1ubuntu1 amd64 [installed,automatic]
gnome-online-accounts/focal,now 3.36.0-1ubuntu1 amd64 [installed,automatic]
gnome-settings-daemon-common/focal-updates,now 3.36.1-0ubuntu1 all [installed,automatic]
gnome-settings-daemon/focal-updates,now 3.36.1-0ubuntu1 amd64 [installed,automatic]
gnome-user-docs/focal-updates,now 3.36.2+git20200704-0ubuntu0.1 all [installed,automatic]

@girish I forgot one more line Jan 04 06:16:13 box:shell backup-snapshot/app_dd36cce2-7674-4985-b671-a7dcd2d96a6c code: null, signal: SIGKILL. The rest of the log is just the normal uploading messages. I'd post the whole thing but there are a lot of file names I'd rather not share.

@girish It looks like a full gnome desktop is not installed. There is gnome shell and a few other gnome components, obviously enough to launch a basic window manager because that is what it is doing.

I've been continuously working on this for the last 3 days so let me give some updates. It turns out Cloudron did manage to do a backup after the update to 6.0.1 before my server died so that is what I restored. I was very happy about this because I believe the underlying problem that initially brought my server down had to do with the power management in certain 4.x kernel versions causing data corruption in certain Samsung SSDs. There are supposedly workarounds for this but it was fixed so I'd rather use a newer kernel if possible. So since version 6+ works on Ubuntu 20.04.x that is what I installed and did the recovery on. My understanding is only the Cloudron versions need to match for a recovery and not the Ubuntu version but perhaps I am wrong about this. Either way the issues with gnome occur before I even start the recovery process.

I have done several reinstalls with a base Ubuntu Server 20.04.1 image. I tell the installer to install openssh and nothing else. After the install I setup ssh, I do some modifications to ssh options and copy my key pair. After all these steps gnome is not installed. If I reboot the server it boots into shell. Then I install Cloudron using commands:

wget https://cloudron.io/cloudron-setup
chmod +x ./cloudron-setup
./cloudron-setup --version 6.0.1

The installer finishes normally. After reboot gnome is installed and I boot into GUI login screen which I can log into and takes me to some sort of gnome desktop (although I don't think it is complete gnome desktop, I don't know that much about gnome). After this the system has some weird behavior where it goes into some sort of unrecoverable hibernation after about 5 - 10 minutes. I tried various methods to disable sleep and none of them resolved the problem. Finally I modified grub so it forcibly boots into cli shell instead of gnome. After that, everything is working like normal so far. The Cloudron restore has been succesful and while I haven't tested much yet, it all seems to be working so far.

To clean things up my next step will be to remove packages that shouldn't be there for Cloudron. Here is the full list of packages installed by apt . If you have some quick way to match this to what it should be I would appreciate you letting me know which packages shouldn't be installed. This server is dedicated solely to Cloudron so if Cloudron wasn't supposed to install it, it shouldn't be there.

I haven't tried installing on any other devices virtual or otherwise with 6.0.1 but if someone wants to try to replicate this bug it would be a very quick test. I could give the full specs of the system I am running Cloudron on but it probably is too much work to try to replicate that. My opinion on what relevant factors may be are:

1. Physical bare metal server
2. Has display and keyboard connected
3. Has dedicated GPU
4. Uses dedicated account for Cloudron (but this is the only account and the server does nothing else, I just didn't want to use root)

So perhaps someone could try to replicate with latest Ubuntu 20.0.4 Server installer and Cloudron 6.0.1. Either way I would appreciate knowing which of my packages should be removed.

@jan_z Do you know the names of all the unnecessary packages. I want to remove them without doing a fresh install. Or maybe Cloudron will remove them automatically with the next update?

First backup after restoring Cloudron is failing with the following error:

box:backups nextcloud.domain Unable to backup { BoxError: Backuptask crashed
at /home/yellowtent/box/src/backups.js:872:29
at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)
at ChildProcess.emit (events.js:198:13)
at ChildProcess.EventEmitter.emit (domain.js:448:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
name: 'BoxError',
reason: 'Internal Error',
details: {},
message: 'Backuptask crashed' }
Jan 02 06:37:07 box:taskworker Task took 16626.103 seconds
Jan 02 06:37:07 box:tasks setCompleted - 1205: {"result":null,"error":{"stack":"BoxError: Backuptask crashed\n at /home/yellowtent/box/src/backups.js:872:29\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)\n at ChildProcess.emit (events.js:198:13)\n at ChildProcess.EventEmitter.emit (domain.js:448:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}
Jan 02 06:37:07 box:tasks 1205: {"percent":100,"result":null,"error":{"stack":"BoxError: Backuptask crashed\n at /home/yellowtent/box/src/backups.js:872:29\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)\n at ChildProcess.emit (events.js:198:13)\n at ChildProcess.EventEmitter.emit (domain.js:448:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}

I'm using rsync.

@subven It is just a base Ubuntu server install, I did not manually install any packages. Gnome was not installed when I ran the Cloudron installer. After installing Cloudron Gnome was installed. It appears as if the Cloudron installer installed Gnome.

@girish my initial questions are all resolved now. I'm having some new problems though. Namely that it seems the Cloudron installer is installing Gnome which is making my server enter sleep mode. I disabled it now but I'm confused as to why Gnome is being installed.

@subven Directory names are also encrypted with rsync, except for the box directory. I was talking about ssh specifically because @girish wanted to ssh into the server to see if he could recover it.

I see box backup filename is not encrypted like all the others, just hadn't been backed up for a while so I had to go back to older dates.

@subven I think file names are different for rsync and tgz. With rsync file names are encrypted. Also, this is my own physical server, I am not using a VPS.

@girish I don't think anyone will be help to help me recover the server because even ssh isn't working. As for the backup names, I think encryption is making it so I can't see the naming you're talking about. Do I need to decrypt it in order to see the names?

My Cloudron died when I updated to 6.0 and I'm now attempting to do a full restore. I read the backup documentation again but I'm unclear on a few things.

1. I am using encrypted rsync backup on Wasabi. With rsync there is not one archive per backup so I don't understand what I am supposed to enter for backup ID as I have a ton of files that all have different encrypted names.
2. The documentation says the Cloudron version used for the backup must be the same as the version that was backed up. How do I know what version the backup was made for?