"Installing - Waiting for Cloudron to initialize" and no install

[FortyTwo]

Hi there,

Provider : dedicated server by Scaleway.
OS : ubuntu server 20.04

Since 3 or 4 days I have a problem of installation of application, the message "Installing - Waiting for Cloudron to initialize" to install Vaultwarden (and all others app's) remains displayed and the applications do not install any more. I formatted my server to do it properly, Cloudron was working fine but since nothing, I can't install anything.

At first, I had a message like "Failed to install ntp", so I install manually an ntp server then I launch the Cloudron installation script which installs correctly. I have configured the domain correctly, the DNS entries are correct and in Services everything is green (unbound too). When I click on the installation to display the logs, the terminal is empty, there is nothing.

When I click on the red cross to stop the installation, nothing happens. I have a screen where I cannot act anymore.

I am blocked and I don't know how to solve this problem!

Someone to help me ?

Thanks

[nebulon]

@fortytwo I can reproduce the issues mentioned. Looks like the scaleway image for Ubuntu 20.04 needs special treatment to work at the moment. We will investigate to see how our installer needs to be fixed for the next release to support those instances.

[nebulon]

The setup is fixed with https://git.cloudron.io/cloudron/box/-/commit/ba2475dc7ed80a7de9b1792f79e1f8f9ea8e287c but will only be part of the next release then.

[girish]

I guess workaround is to install apt install systemd-timesyncd and then reboot the server?

[nebulon]

Indeed that will solve it for now.

[FortyTwo]

@nebulon @girish

Thank you very much for your help, I had noticed that the name of the ubuntu image had changed to ubuntu_server_compat_64bits, that's was the name of the image at Scaleway. But I got into trouble with Scaleway customer service and decided to cancel my server with them.

Can you tell me if a server at Kimsufi under ubuntu server works with Cloudron ?

[nebulon]

@fortytwo we don't actively test Kimsufi, however like most other VPS providers, as long as they don't tweak the vanilla Ubuntu much it should just work, otherwise we will see if we can fix our installer accordingly.

[FortyTwo]

@nebulon

Thank you very much for your answers & good work !

Best regards,

[FortyTwo]

Hello,

I just subscribed to a dedicated Kimsufi server, but I have the same problem with the same message "Installing - Waiting for Cloudron to initialize" and the applications do not install.

There is also a pop-up with the message "Cloudron Error - Response timeout".

The ubuntu server image used does not appear to be modified, it is called "Ubuntu server 20.04 Focal Fossa (64 bits)".

Can you help me please ?

Thanks,

[nebulon]

@fortytwo can you check /home/yellowtent/platformdata/logs/box.log to see what the platform there is waiting for or doing?

[FortyTwo]

@nebulon

I have this :
2021-09-02T10:35:40.018Z box:apphealthmonitor app health: 0 alive / 1 dead

It's ok for you ? Do you need more information ?

Thanks

[nebulon]

@fortytwo can you run systemctl restart box and then take a look at the log file to get an idea where it gets stuck during initializing?

[FortyTwo]

Hi @nebulon

Can you check these lines please ? I have delete some information (password MD5 MySQL, MySQL token, my domain...).

Thanks

2021-09-03T08:27:27.387Z box:locker Lock unreleased platform_start
2021-09-03T08:27:30.017Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:27:40.037Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:27:50.022Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:28:00.043Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:28:10.033Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:28:20.020Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:28:30.020Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:28:40.022Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:28:50.019Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:29:00.049Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:29:10.023Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:29:20.020Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:29:30.021Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:29:40.017Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:29:50.018Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:30:00.024Z box:janitor Cleaning up expired tokens
2021-09-03T08:30:00.060Z box:disks checkDiskSpace: checking disk space
2021-09-03T08:30:00.102Z box:janitor Cleaned up 0 expired tokens
2021-09-03T08:30:00.121Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:30:00.364Z box:disks checkDiskSpace: disk space checked. out of space: no
2021-09-03T08:30:10.022Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:30:20.022Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:30:30.014Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:30:40.020Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:30:50.020Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:31:00.045Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:31:10.022Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:31:20.026Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:31:30.021Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:31:40.021Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:31:50.018Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:32:00.032Z box:apphealthmonitor app health: 0 alive / 1 dead.
Box GET /api/v1/apps/fb918100-4edf-4eab-a72f-5b013ddce285/execws?tty=true&rows=48&columns=178&access_token=<redacted>&cmd=[%22/bin/bash%22] 409 Conflict App not installed or running 78.064 ms - 71
Box GET /api/v1/apps/fb918100-4edf-4eab-a72f-5b013ddce285/execws?tty=true&rows=48&columns=178&access_token=<redacted>&cmd=[%22/bin/bash%22] 409 Conflict App not installed or running 77.400 ms - 71
Box GET /api/v1/apps/fb918100-4edf-4eab-a72f-5b013ddce285/execws?tty=true&rows=48&columns=178&access_token=<redacted>&cmd=[%22/bin/bash%22] 409 Conflict App not installed or running 62.905 ms - 71
Box GET /api/v1/apps/fb918100-4edf-4eab-a72f-5b013ddce285/execws?tty=true&rows=48&columns=178&access_token=<redacted>&cmd=[%22/bin/bash%22] 409 Conflict App not installed or running 88.553 ms - 71
2021-09-03T08:32:10.018Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:32:20.025Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:32:27.388Z box:locker Lock unreleased platform_start
2021-09-03T08:32:30.017Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:32:40.021Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:32:50.017Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:33:00.033Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:33:10.019Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:33:20.029Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:33:30.018Z box:apphealthmonitor app health: 0 alive / 1 dead.
2021-09-03T08:33:35.954Z box:box Received SIGTERM. Shutting down.
2021-09-03T08:33:35.959Z box:tasks stopTask: stopping all tasks
2021-09-03T08:33:35.961Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2021-09-03T08:33:36.019Z box:shell stopTask (stdout): box-task-2.service loaded failed failed /home/yellowtent/box/src/scripts/../taskworker.js 2 /home/yellowtent/platformdata/logs/tasks/2.log

2021-09-03T08:33:42.414Z box:server ==========================================
2021-09-03T08:33:42.417Z box:server            Cloudron 6.3.6  
2021-09-03T08:33:42.417Z box:server ==========================================
2021-09-03T08:33:42.683Z box:settings initCache: pre-load settings
2021-09-03T08:33:42.802Z box:tasks stopTask: stopping all tasks
2021-09-03T08:33:42.804Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2021-09-03T08:33:42.945Z box:reverseproxy writeDashboardConfig: writing admin config for my_domain
2021-09-03T08:33:43.019Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
2021-09-03T08:33:43.081Z box:dockerproxy startDockerProxy: started proxy on port 3003
Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
2021-09-03T08:33:43.141Z box:shell reload (stdout): nginx: [emerg] no host in upstream ":8000" in /etc/nginx/applications/fb918100-4edf-4eab-a72f-5b013ddce285.conf:136

2021-09-03T08:33:43.143Z box:shell reload code: 1, signal: null
2021-09-03T08:33:43.150Z box:cloudron onActivated: running post activation tasks
2021-09-03T08:33:43.151Z box:platform initializing addon infrastructure
2021-09-03T08:33:43.152Z box:platform Updating infrastructure from none to 48.20.0
2021-09-03T08:33:43.153Z box:locker Acquired : platform_start
2021-09-03T08:33:43.154Z box:platform removeAllContainers: removing all containers for infra upgrade
2021-09-03T08:33:43.155Z box:shell removeAllContainers exec: docker ps -qa --filter 'label=isCloudronManaged' | xargs --no-run-if-empty docker stop
2021-09-03T08:33:56.604Z box:shell removeAllContainers (stdout): 347a4deeac81
6efb59b7b2df
9f3e3e4aa567
4ce6e3ce9d86
cad77d4f9361
1b43818652be
2b4da617d393

2021-09-03T08:33:56.604Z box:shell removeAllContainers (stderr): 
2021-09-03T08:33:56.604Z box:shell removeAllContainers exec: docker ps -qa --filter 'label=isCloudronManaged' | xargs --no-run-if-empty docker rm -f
2021-09-03T08:33:57.257Z box:shell removeAllContainers (stdout): 347a4deeac81
6efb59b7b2df
9f3e3e4aa567
4ce6e3ce9d86
cad77d4f9361
1b43818652be
2b4da617d393

2021-09-03T08:33:57.258Z box:shell removeAllContainers (stderr): 
2021-09-03T08:33:57.259Z box:platform markApps: restoring installed apps
2021-09-03T08:33:57.288Z box:apps restoreInstalledApps: marking save.my_domain.fr for restore using restore config null
2021-09-03T08:33:57.378Z box:apps restoreInstalledApps: marked fb918100-4edf-4eab-a72f-5b013ddce285 for restore with taskId 8
2021-09-03T08:33:57.385Z box:services startServices: none -> 48.20.0. starting all services
2021-09-03T08:33:57.391Z box:mail restartMail: restarting mail container with mailFqdn:my_domain.fr dashboardDomain:my_domain.fr
2021-09-03T08:33:57.501Z box:shell stopMail exec: docker stop mail || true
2021-09-03T08:33:57.676Z box:shell stopMail (stdout): 
2021-09-03T08:33:57.677Z box:shell stopMail (stderr): Error response from daemon: No such container: mail

2021-09-03T08:33:57.677Z box:shell removeMail exec: docker rm -f mail || true
2021-09-03T08:33:57.854Z box:shell removeMail (stdout): 
2021-09-03T08:33:57.854Z box:shell removeMail (stderr): Error: No such container: mail

2021-09-03T08:33:57.855Z box:mail createMailConfig: generating mail config
2021-09-03T08:33:57.867Z box:shell startMail exec: docker run --restart=always -d --name="mail"                             --net cloudron                             --net-alias mail                             --log-driver syslog                             --log-opt syslog-address=udp://127.0.0.1:2514                             --log-opt syslog-format=rfc5424                             --log-opt tag=mail                             -m 161480704                             --memory-swap 536870912                             --dns 172.18.0.1                             --dns-search=.                             -e CLOUDRON_MAIL_TOKEN="4d26e09740b27b339d8351f2669181e2d1a93fa6f1fbd0bc9dbb192666ece7dad24968808cdf81af73930fcb9f4b5726a1e820eee514d8abde8f9a48c098d57a9d2de8fff57da68151d236092bf5f00939c0d04cfa3755ad2a596199714efdb68c3a1e314a86842f411330bfeb56f63aa3f4658e821fd480a0f1a061a838ee7f"                             -e CLOUDRON_RELAY_TOKEN="8a6b1616897ce2900579fe9eb65048df7601ce9109c38eebd68fe180efa0653fc0a66472a9fb7ffe2d17b76cdd1c4576d10e364794ccedb94df1c1afdf6919f579a220df976fcf2ab67f74ffa4ccf744418b50ea6ba1643761a9f2002466170ac3f16a8e2256cdaf2b6151f01e6dcbafc52b7dd96e297e4d532868f5e67f937d"                             -v "/home/yellowtent/boxdata/mail:/app/data"                             -v "/home/yellowtent/platformdata/addons/mail:/etc/mail"                                                          --label isCloudronManaged=true                             --read-only -v /run -v /tmp cloudron/mail:3.3.3@sha256:b1093e6f38bebf4a9ae903ca385aea3a32e7cccae5ede7f2e01a34681e361a5f
2021-09-03T08:34:00.834Z box:shell startMail (stdout): 28d25c9fcd0494dde3a468e819fb5262003f293bea3b88de7c13f745527e68b5

2021-09-03T08:34:00.835Z box:shell startMail (stderr): 
2021-09-03T08:34:00.871Z box:shell stopTurn exec: docker stop turn || true
2021-09-03T08:34:01.054Z box:shell stopTurn (stdout): 
2021-09-03T08:34:01.054Z box:shell stopTurn (stderr): Error response from daemon: No such container: turn

2021-09-03T08:34:01.054Z box:shell removeTurn exec: docker rm -f turn || true
2021-09-03T08:34:01.227Z box:shell removeTurn (stdout): 
2021-09-03T08:34:01.227Z box:shell removeTurn (stderr): Error: No such container: turn

2021-09-03T08:34:01.227Z box:shell startTurn exec: docker run --restart=always -d --name="turn"                     --hostname turn                     --net host                     --log-driver syslog                     --log-opt syslog-address=udp://127.0.0.1:2514                     --log-opt syslog-format=rfc5424                     --log-opt tag=turn                     -m 80740352                     --memory-swap 268435456                     --dns 172.18.0.1                     --dns-search=.                     -e CLOUDRON_TURN_SECRET="a0ad5d93dd0b1d360eb4aa7f20cc80a"                     -e CLOUDRON_REALM="my_domain.fr"                     --label isCloudronManaged=true                     --read-only -v /tmp -v /run "cloudron/turn:1.3.1@sha256:759cafab7625ff538418a1f2ed5558b1d5bff08c576bba577d865d6d02b49091"
2021-09-03T08:34:03.626Z box:shell startTurn (stdout): 696f750f20210aeb72fb838a7af1227aa602337cc7a1ed62b8fac99adeaedf2c

2021-09-03T08:34:03.627Z box:shell startTurn (stderr): 
2021-09-03T08:34:03.629Z box:shell stopMysql exec: docker stop mysql || true
2021-09-03T08:34:03.846Z box:shell stopMysql (stdout): 
2021-09-03T08:34:03.846Z box:shell stopMysql (stderr): Error response from daemon: No such container: mysql

2021-09-03T08:34:03.847Z box:shell removeMysql exec: docker rm -f mysql || true
2021-09-03T08:34:04.020Z box:shell removeMysql (stdout): 
2021-09-03T08:34:04.020Z box:shell removeMysql (stderr): Error: No such container: mysql

2021-09-03T08:34:04.021Z box:shell startMysql exec: docker run --restart=always -d --name="mysql"                     --hostname mysql                     --net cloudron                     --net-alias mysql                     --log-driver syslog                     --log-opt syslog-address=udp://127.0.0.1:2514                     --log-opt syslog-format=rfc5424                     --log-opt tag=mysql                     --dns 172.18.0.1                     --dns-search=.                     -e CLOUDRON_MYSQL_TOKEN=information_deleted_by_me07ab526a0f3b1                     -e CLOUDRON_MYSQL_ROOT_HOST=172.18.0.1                     -e CLOUDRON_MYSQL_ROOT_PASSWORD=information_deleted_by_me                     -v "/home/yellowtent/platformdata/mysql:/var/lib/mysql"                     --label isCloudronManaged=true                     --cap-add SYS_NICE                     --read-only -v /tmp -v /run "cloudron/mysql:3.0.7@sha256:6679c2fb96f8d6d62349b607748570640a90fc46b50aad80ca2c0161655d07f4"

[FortyTwo]

Hey team, YOU ROCK!!! I don't know if you made any changes, but I rebooted the server and the installation went well. And I can install other applications.

Can you tell me if you made any changes please ?

I think we can confirm that Cloudron works well on Kimsufi servers.

Thank you so much,

[nebulon]

@fortytwo we haven't done anything on your setup, since we don't even have access to your system. I suspect from the logs that there might have been some initial docker hickup on your server, which was resolved by the reboot.