Solved Cloudron not launching after reboot

[RazielKanos]

I opened a ticket already, but maybe somehere here can help me out sooner. I had some odd CPU spikes, so i rebootet cloudron, but the dashboard didn't come back. So i rebootet the whole server, tried to launch claudron by hand, but I get an error message about ngix

I have no clue how to fix that

[msbt]

@RazielKanos a good start would be posting the error message to see what's going on

[RazielKanos]

2022-12-04T01:47:46 ==> start: Cloudron Start
media500:
2022-12-04T01:47:46 ==> start: Configuring docker
Synchronizing state of apparmor.service with SysV service script with /lib/syste md/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable apparmor
2022-12-04T01:47:47 ==> start: Ensuring directories
2022-12-04T01:47:47 ==> start: Configuring journald
2022-12-04T01:47:47 ==> start: Setting up unbound
2022-12-04T01:47:47 ==> start: Adding systemd services
Synchronizing state of unbound.service with SysV service script with /lib/system d/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable unbound
Synchronizing state of cron.service with SysV service script with /lib/systemd/s ystemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable cron
2022-12-04T01:47:49 ==> start: Configuring sudoers
2022-12-04T01:47:49 ==> start: Configuring collectd
2022-12-04T01:47:50 ==> start: Configuring sysctl
2022-12-04T01:47:50 ==> start: Configuring logrotate
2022-12-04T01:47:50 ==> start: Adding motd message for admins
2022-12-04T01:47:50 ==> 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.
root@v2202211115363206125:~# sudo systemctl status nginx
● 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 Sun 2022-12-04 01:47:51 UTC; 1min 46s ago
Docs: http://nginx.org/en/docs/
Process: 30103 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE)

Dez 04 01:47:51 v2202211115363206125 systemd[1]: nginx.service: Service hold-off time over, scheduling restart.
Dez 04 01:47:51 v2202211115363206125 systemd[1]: nginx.service: Scheduled restart job, restart counter is at 5.
Dez 04 01:47:51 v2202211115363206125 systemd[1]: Stopped nginx - high performance web server.
Dez 04 01:47:51 v2202211115363206125 systemd[1]: nginx.service: Start request repeated too quickly.
Dez 04 01:47:51 v2202211115363206125 systemd[1]: nginx.service: Failed with result 'exit-code'.
Dez 04 01:47:51 v2202211115363206125 systemd[1]: Failed to start nginx - high performance web server.

[msbt]

@RazielKanos and what's in journalctl -xe

[RazielKanos]

This post is deleted!

[RazielKanos]

@msbt

Well, no clue how to look into that thing, but when i type it in i get this:

root@v2202211115363206125:~# journalctl -xe
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat

-- A session with the ID 33 has been terminated.
Dez 04 02:57:22 v2202211115363206125 kernel: Packet dropped: IN=eth0 OUT= MAC=96
Dez 04 02:57:35 v2202211115363206125 sshd[17963]: Accepted password for root fro
Dez 04 02:57:35 v2202211115363206125 sshd[17963]: pam_unix(sshd:session): sessio
Dez 04 02:57:35 v2202211115363206125 systemd-logind[1116]: New session 37 of use
-- Subject: A new session 37 has been created for user root
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat

-- A new session with the ID 37 has been created for the user root.

-- The leading process of the session is 17963.
Dez 04 02:57:35 v2202211115363206125 systemd[1]: Started Session 37 of user root
-- Subject: Unit session-37.scope has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support

-- Unit session-37.scope has finished starting up.

-- The start-up result is RESULT.
lines 1393-1415/1415 (END)
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat

-- A session with the ID 33 has been terminated.
Dez 04 02:57:22 v2202211115363206125 kernel: Packet dropped: IN=eth0 OUT= MAC=96:9a:62:d6:fc:70:2c:6b:f5:a0:77:c0:08:00 SRC=212.70.149.42 DST=89.58.58.224 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=14229 PROTO=TCP SPT=48811 DPT=30364 WINDOW=1024 R
Dez 04 02:57:35 v2202211115363206125 sshd[17963]: Accepted password for root from 5.147.49.78 port 40415 ssh2
Dez 04 02:57:35 v2202211115363206125 sshd[17963]: pam_unix(sshd:session): session opened for user root by (uid=0)
Dez 04 02:57:35 v2202211115363206125 systemd-logind[1116]: New session 37 of user root.
-- Subject: A new session 37 has been created for user root
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat

-- A new session with the ID 37 has been created for the user root.

-- The leading process of the session is 17963.
Dez 04 02:57:35 v2202211115363206125 systemd[1]: Started Session 37 of user root.
-- Subject: Unit session-37.scope has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support

-- Unit session-37.scope has finished starting up.

-- The start-up result is RESULT.

[girish]

@RazielKanos Try journalctl -u nginx -fa to see the logs. If that doesn't have anything interesting, try systemctl restart nginx and then try the logs command again.

[girish]

Issue was https://forum.cloudron.io/topic/6506/after-a-reboot-nginx-does-not-start