Cloudron does not start after Update to 6.3.3

[necrevistonnezr]

@girish

• All my apps were in an error state after the update: Nginx Error: Error reloading nginx: reload exited with code 1 signal null
• the System Reboot button does nothing
• after a manual reboot, Cloudron cannot be reached
• systemctl restart box does not help, either
• sh /home/yellowtent/box/setup/start.sh results in sh /home/yellowtent/box/setup/start.sh: 3: set: Illegal option -o pipefail

[necrevistonnezr]

as per https://stackoverflow.com/questions/54055549/linux-ubuntu-set-illegal-option-o-pipefail: the option pipefail does not work with sh:

You are running bin/sh, on Ubuntu it is a symbolic link pointing to /bin/dash, but pipefail is a bashism.

After running start.sh with bash, I get the following error:

sudo bash /home/yellowtent/box/setup/start.sh
2021-06-26T07:43:16 ==> start: Cloudron Start
media:x:500:
2021-06-26T07:43:16 ==> start: Configuring docker
Synchronizing state of apparmor.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable apparmor
Error response from daemon: network with name cloudron already exists
2021-06-26T07:43:21 ==> start: Ensuring directories
2021-06-26T07:43:21 ==> start: Configuring journald
2021-06-26T07:43:23 ==> start: Setting up unbound
2021-06-26T07:43:23 ==> start: Adding systemd services
Synchronizing state of unbound.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable unbound
Synchronizing state of cron.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable cron
2021-06-26T07:45:18 ==> start: Configuring sudoers
2021-06-26T07:45:18 ==> start: Configuring collectd
2021-06-26T07:45:18 ==> start: Configuring logrotate
2021-06-26T07:45:18 ==> start: Adding motd message for admins
2021-06-26T07:45:18 ==> start: Configuring nginx
Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.

about that nginx error:

systemctl status nginx.service
● nginx.service - nginx - high performance web server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/nginx.service.d
             └─cloudron.conf
     Active: failed (Result: exit-code) since Sat 2021-06-26 07:45:22 UTC; 2min 42s ago
       Docs: http://nginx.org/en/docs/

Jun 26 07:45:22 my.ckfl.net systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
Jun 26 07:45:22 my.ckfl.net systemd[1]: Stopped nginx - high performance web server.
Jun 26 07:45:22 my.ckfl.net systemd[1]: nginx.service: Start request repeated too quickly.
Jun 26 07:45:22 my.ckfl.net systemd[1]: nginx.service: Failed with result 'exit-code'.
Jun 26 07:45:22 my.ckfl.net systemd[1]: Failed to start nginx - high performance web server.

[necrevistonnezr]

And found the error!

• sudo nginx -t led me to etc/nginx/applications
• There I found super old (+ 2 years old) conf files relating to two domains that I had used once to access my Cloudron.
• After deleting these files and retrying the start script, Cloudron is reachable.
• Now I just have to click on the "Retry configure task" in each app and they are running!

[girish]

@necrevistonnezr ah, glad you figured that out.

[girish]

I will see if we can delete unused old nginx config files during upgrade

[robi]

@girish I would avoid deleting them, but instead migrate them to the deactivated directory.