Cloudron post install questions

[BrutalBirdie]

@ejarvis
Might be connected to:
https://forum.cloudron.io/topic/8101/fix-for-kernel-bug-in-ubuntu-20-04-causing-various-issues

[girish]

@ejarvis said in Cloudron post install questions:

Is there a way to completely wipe my slate so that I can try to install an app again?

You can just reboot the server. That should make it unstuck if this is related to the Ubuntu kernel issue. Can you please try that?

[ejarvis]

@BrutalBirdie I'm checking this now, thanks for the link.

[ejarvis]

@girish said in Cloudron post install questions:

@ejarvis said in Cloudron post install questions:

Is there a way to completely wipe my slate so that I can try to install an app again?

You can just reboot the server. That should make it unstuck if this is related to the Ubuntu kernel issue. Can you please try that?

I've tried that. First rule of troubleshooting, eh?

[ejarvis]

@BrutalBirdie Applied that via SSH, everything went smoothly. However, the app is still stuck in 'installing' mode and won't let me stop or remove it.

^^screenshot

[girish]

@ejarvis Ah, the "Queued" usually either means the platform is still starting or the backup is running. For the latter, you can check in the Backups view. For the former, can you see /home/yellowtent/platformdata/logs/box.log ? Does it show some error or goes on about platform lock not released?

[ejarvis]

@girish said in Cloudron post install questions:

@ejarvis Ah, the "Queued" usually either means the platform is still starting or the backup is running. For the latter, you can check in the Backups view. For the former, can you see /home/yellowtent/platformdata/logs/box.log ? Does it show some error or goes on about platform lock not released?

It does say that there is a conflict and that the task is locked.

Box POST /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/exec 409 Conflict App not installed or running 465.399 ms>
2022-12-01T01:06:16.237Z box:locker Lock unreleased platform_start
Box POST /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/restart 409 Conflict Locked by task 3 : pending_install />

On the bright side, the log files are very verbose and relatively detailed, with nearly everything that we need to know. Is there something else that I can verify for you?

[girish]

@ejarvis said in Cloudron post install questions:

2022-12-01T01:06:16.237Z box:locker Lock unreleased platform_start

If you keep scrolling up, you should find some error. One of the services is not starting. Which version are you on?

[ejarvis]

@girish You mean this?

Box POST /api/v1/tasks/3/stop 409 Conflict task is not active 816.625 ms - 61
Box GET /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/files/ 404 Not Found Unable to find container sftp 401.543>
Box GET /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/files/ 404 Not Found Unable to find container sftp 701.603>
Box GET /api/v1/apps/cf294eb7-14c1-4f18-813a-14f9b2cb6463/files/ 404 Not Found Unable to find container sftp 628.086

Top header says Cloudron 7.3.2

[girish]

@ejarvis no, there should be some other error. You can also do systemctl restart box and it should give some docker error. Otherwise, if you contact us on support@cloudron.io, i can take a look.

[ejarvis]

@girish Let me do a restart and will see what I can see. If that fails, will contact you at that address.

[ejarvis]

@girish Well, the result is interesting:

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to restart 'box.service'.
Authenticating as: Edwin Jarvis (jarvis)
Password:
==== AUTHENTICATION COMPLETE ===

Ummm...

[BrutalBirdie]

@ejarvis
Did you install Cloudron on your Ubuntu Desktop Computer?
It looks like you are running as user jarvis who does not have permission to execute that command.
So you should use sudo systemctl restart box.service

But please answer first on what systems you installed Cloudron.
Like very specific, tell us all.

[subven]

@ejarvis said in Cloudron post install questions:

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
~~
Authenticating as: Edwin Jarvis (jarvis)

Looks like CentOS Desktop to me.

@ejarvis please post the output of cat /etc/*-release If you're not on Ubuntu 20.04 or 22.04 we won't help you any further and I would advice you to follow the Cloudron installation docs.

[ejarvis]

@subven said in Cloudron post install questions:

@ejarvis said in Cloudron post install questions:

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
~~
Authenticating as: Edwin Jarvis (jarvis)

Looks like CentOS Desktop to me.

@ejarvis please post the output of cat /etc/*-release If you're not on Ubuntu 20.04 or 22.04 we won't help you any further and I would advice you to follow the Cloudron installation docs.

Umm... no?

NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

I installed a minimal XFCE4 desktop environment so that I could VNC into the server as needed.

Do you think this is part of the issue?

[ejarvis]

@subven said in Cloudron post install questions:
If you're not on Ubuntu 20.04 or 22.04 we won't help you any further and I would advice you to follow the Cloudron installation docs.

This statement bothers me, since the person that was helping me was directly from the source, and you haven't helped at all yet?

For what it's worth, I did follow the cloudron install docs that you linked. Prior to that, the server has been running on that limited desktop environment.

If I need to nuke it all and do it again, it's not that much of a hassle.

EDIT: Nuking it now.

[ejarvis]

@subven said in Cloudron post install questions:

@ejarvis said in Cloudron post install questions:

==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
~~
Authenticating as: Edwin Jarvis (jarvis)

Looks like CentOS Desktop to me.

@ejarvis please post the output of cat /etc/*-release If you're not on Ubuntu 20.04 or 22.04 we won't help you any further and I would advice you to follow the Cloudron installation docs.

Also:

ls -l /usr/share/xsessions
total 12
-rw-r--r-- 1 root root 303 Mar 26 2020 ubuntu.desktop
-rw-r--r-- 1 root root 6273 Mar 30 2020 xfce.desktop

[ejarvis]

@BrutalBirdie said in Cloudron post install questions:

@ejarvis
Did you install Cloudron on your Ubuntu Desktop Computer?
It looks like you are running as user jarvis who does not have permission to execute that command.
So you should use sudo systemctl restart box.service

But please answer first on what systems you installed Cloudron.
Like very specific, tell us all.

I do notice that there are two users listed in the server now, my own as it was set up when I installed the server, and the Cloudron account that I assume was installed with their script.

The 'jarvis' account is root.

[ejarvis]

Looking around inside the application, going to services, I can see that neither the MySQL nor PostgreSQL are running.

PostgreSQL at least shows an amber indicator like it's trying to load. Could this also contribute?

[BrutalBirdie]

@ejarvis said in Cloudron post install questions:

I installed a minimal XFCE4 desktop environment so that I could VNC into the server as needed.

I am a bit confused with the as needed statement.
You only need a fresh Ubuntu 20.04 / 22.04 server install with ssh access to run the Cloudron install commands.
It's generally not advised to install other software alongside Cloudron because it can lead to many problems.

The fastest and easiest way to come to a working state would be a fresh Ubuntu 20/22 install, ssh into root or the sudo user and then (if sudo switch to root) follow the install.

@ejarvis said in Cloudron post install questions:

The 'jarvis' account is root.

What? No? root is root. . . jarvis might be a sudoer?

The Cloudron install needs to be run with root / sudo.
Amazingly this is not mentioned anywhere @staff I never noticed that until now.

https://docs.cloudron.io/installation/