Cloudron post install questions
-
@ejarvis to rule out some error cases, can you disable the proxying for that domain in cloudflare and check if this may be the issue?
@nebulon I tried that actually and was able to get it connected. However, now I have an app that is stuck on 'installing' and won't let me stop the task, or remove the app (or go through the steps that requires placing the app in a recovery mode).
Is there a way to completely wipe my slate so that I can try to install an app again?
-
@nebulon I tried that actually and was able to get it connected. However, now I have an app that is stuck on 'installing' and won't let me stop the task, or remove the app (or go through the steps that requires placing the app in a recovery mode).
Is there a way to completely wipe my slate so that I can try to install an app again?
-
@nebulon I tried that actually and was able to get it connected. However, now I have an app that is stuck on 'installing' and won't let me stop the task, or remove the app (or go through the steps that requires placing the app in a recovery mode).
Is there a way to completely wipe my slate so that I can try to install an app again?
@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?
-
@BrutalBirdie I'm checking this now, thanks for the link.
-
@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?
@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?
-
-
@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@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 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?@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 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?
-
@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?
@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.086Top header says Cloudron 7.3.2
-
@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.086Top header says Cloudron 7.3.2
-
@ejarvis no, there should be some other error. You can also do
systemctl restart boxand it should give some docker error. Otherwise, if you contact us on support@cloudron.io, i can take a look. -
@ejarvis no, there should be some other error. You can also do
systemctl restart boxand it should give some docker error. Otherwise, if you contact us on support@cloudron.io, i can take a look.@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...
-
@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...
@ejarvis
Did you install Cloudron on your Ubuntu Desktop Computer?
It looks like you are running as userjarviswho does not have permission to execute that command.
So you should usesudo systemctl restart box.serviceBut please answer first on what systems you installed Cloudron.
Like very specific, tell us all. -
@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...
@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 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.@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=focalI 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 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.@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 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.@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
Did you install Cloudron on your Ubuntu Desktop Computer?
It looks like you are running as userjarviswho does not have permission to execute that command.
So you should usesudo systemctl restart box.serviceBut please answer first on what systems you installed Cloudron.
Like very specific, tell us all.@BrutalBirdie said in Cloudron post install questions:
@ejarvis
Did you install Cloudron on your Ubuntu Desktop Computer?
It looks like you are running as userjarviswho does not have permission to execute that command.
So you should usesudo systemctl restart box.serviceBut 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.
-
@BrutalBirdie said in Cloudron post install questions:
@ejarvis
Did you install Cloudron on your Ubuntu Desktop Computer?
It looks like you are running as userjarviswho does not have permission to execute that command.
So you should usesudo systemctl restart box.serviceBut 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.
