Cloudron Forum

@girish @nebulon You guys should partner with Storj.io as they are decentralized and amazing platform. I use them for our Cloud backup of our File Server and they are quick, fast amazing, and cheap!

never mind, I fixed the issue with the IP. I went into GoDaddy and noticed the IP was different, so I changed it back, restarted unbound service and now my dashboard is loading with my domain. Now to restoring all of the apps with my backups.

Hi @joseph I checked this and unbound was running and active. Now I did check and host domain.com 127.0.0.1 and that failed. I followed the link in the document and created the customer.conf file and added in what it required and restarted the unbound service and did a check again to host domain.com 127.0.0.150 and that worked, but the problem is, the URL is pointing to the wrong IP and I did not set that up. I need that changed to my custom IP I use for this service, which I know I entered when I tried to get this working. How do I change that when GoDaddy is setup fine and my firewall has all the rules forwarding that customer IP to the internal IP of the Cloudron server

Hello,

I had to reinstall Cloudron an another server as the server it was on crashed. Taking my backup is not working and I am using the same IP (as server is hosted internally) so I can make sure that I do have to setup new Port Forwarding rules. It is giving me the following Error:

I did do the host -t NS (hostname) and it came back with NS servers on Godaddy and when I did a host -t NS (hostname) 127.0.0.1 I was getting no response at all and nothing was found. I did this on the server side. I am confused as to why it is doing this and I need to get my server backup.

Hi @girish,

I did that step and did a server reboot as the systemctl restart unbound did not work and when it came back up, all was good again! Thank you!

I ran this and got the following:

sudo journalctl -xeu unbound.service
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit unbound.service has begun execution.
░░
░░ The job identifier is 2602.
Sep 30 19:09:37 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStartPre= process belonging to unit unbound.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 203.
Sep 30 19:09:37 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Sep 30 19:09:37 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 2602 and the job result is failed.
Sep 30 19:09:38 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit unbound.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Sep 30 19:09:38 cloudron systemd[1]: unbound.service: Start request repeated too quickly.
Sep 30 19:09:38 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Sep 30 19:09:38 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit unbound.service has finished with a failure.
░░
░░ The job identifier is 2791 and the job result is failed.

I ran this and got the following:

cloudron-support --troubleshoot
Vendor: QEMU Product: Standard PC (i440FX + PIIX, 1996)
Linux: 6.8.0-45-generic
Ubuntu: noble 24.04
Processor: AMD Ryzen 7 3800X 8-Core Processor
BIOS pc-i440fx-9.0 CPU @ 2.0GHz x 8
RAM: 32866264KB
Disk: /dev/sda2 701G
[OK] node version is correct
[OK] IPv6 is enabled
[OK] docker is running
[OK] MySQL is running
[OK] nginx is running
[OK] dashboard cert is valid
[OK] dashboard is reachable via loopback
[OK] box v8.0.6 is running
[OK] netplan is good
[OK] DNS is resolving via systemd-resolved
[FAIL] Could not load dashboard domain.

It is just hanging and nothing is coming up, but I can Control C to stop it

Yes, Unbound is properly installed

Sep 28 05:01:44 cloudron unbound[819]: [819:0] info: generate keytag query _ta-4f66. NULL IN
Sep 28 05:30:33 cloudron systemd[1]: Stopping unbound.service - Unbound DNS Resolver...
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: service stopped (unbound 1.19.2).
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: server stats for thread 0: 1353 queries, 288 answers from cache, 1065 recursions, 0 prefetch, 0 rejected by ip ra>
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: server stats for thread 0: requestlist max 15 avg 0.586854 exceeded 28 jostled 0
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: average recursion processing time 0.108782 sec
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: histogram of recursion processing times
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: [25%]=0.0432723 median[50%]=0.0667963 [75%]=0.117063
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: lower(secs) upper(secs) recursions
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: 0.008192 0.016384 45
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: 0.016384 0.032768 95
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: 0.032768 0.065536 372
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: 0.065536 0.131072 338
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: 0.131072 0.262144 112
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: 0.262144 0.524288 43
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: 0.524288 1.000000 28
Sep 28 05:30:33 cloudron unbound[819]: [819:0] info: 1.000000 2.000000 4
Sep 28 05:30:33 cloudron systemd[1]: unbound.service: Deactivated successfully.
Sep 28 05:30:33 cloudron systemd[1]: Stopped unbound.service - Unbound DNS Resolver.
Sep 28 05:30:33 cloudron systemd[1]: unbound.service: Consumed 2.639s CPU time, 15.4M memory peak, 0B memory swap peak.
Sep 28 05:30:33 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 28 05:30:33 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 28 05:30:33 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 28 05:30:33 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 1.
Sep 28 05:30:34 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 28 05:30:34 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 2.
Sep 28 05:30:34 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 28 05:30:34 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 3.
Sep 28 05:30:34 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 28 05:30:34 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 4.
Sep 28 05:30:34 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 28 05:30:34 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 28 05:30:34 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 28 05:30:35 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Sep 28 05:30:35 cloudron systemd[1]: unbound.service: Start request repeated too quickly.
Sep 28 05:30:35 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 28 05:30:35 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
-- Boot 41862792df8b41d4b1f0d020a113a679 --
Sep 30 14:06:58 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 14:06:58 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 14:06:58 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 14:06:58 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 14:06:58 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 1.
Sep 30 14:06:58 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 14:06:58 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 14:06:58 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 14:06:58 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 14:06:58 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 2.
Sep 30 14:06:59 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 14:06:59 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 3.
Sep 30 14:06:59 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 14:06:59 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 4.
Sep 30 14:06:59 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 14:06:59 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Start request repeated too quickly.
Sep 30 14:06:59 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 14:06:59 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
-- Boot c896dce9e2024762ab95f16909c5b548 --
Sep 30 14:27:08 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 14:27:08 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 1.
Sep 30 14:27:08 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 14:27:08 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 2.
Sep 30 14:27:08 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 14:27:08 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 3.
Sep 30 14:27:08 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 14:27:08 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
lines 1355-1404

I came in this morning and I had a message from my US Office stating that Scan to e-mail is not working, and I use Cloudron to act as the mail server. I tried rebooting and unbound service is still not loading. It is on version 8.0.6 on Ubuntu Server 24.04. An automatic update to 8.0.6 happened on the weekend and now this service is broken. Below are the logs I found:

Sep 30 12:29:29 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 12:29:29 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 1.
Sep 30 12:29:29 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 12:29:29 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 2.
Sep 30 12:29:29 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 12:29:29 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 3.
Sep 30 12:29:29 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 12:29:29 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 12:29:29 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 12:29:30 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 4.
Sep 30 12:29:30 cloudron systemd[1]: Starting unbound.service - Unbound DNS Resolver...
Sep 30 12:29:30 cloudron systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC
Sep 30 12:29:30 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 12:29:30 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.
Sep 30 12:29:30 cloudron systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Sep 30 12:29:30 cloudron systemd[1]: unbound.service: Start request repeated too quickly.
Sep 30 12:29:30 cloudron systemd[1]: unbound.service: Failed with result 'exit-code'.
Sep 30 12:29:30 cloudron systemd[1]: Failed to start unbound.service - Unbound DNS Resolver.

What can I do to get this resolved.

I did the curl command it timed out on port 80. This is weird since I have port 80 and 443 open. Unless you are outside of Canada and the US, as those the only 2 countries I allow because we operate in both countries. The rest of the world is blocked

Yes since I am self hosting it in my office on my own equipment I have an enterprise grade firewall that the server sits behind.

@nebulon yes it is my dashboard and other apps that use OpenID are working just fine. It is just 2fAuth app that is causing me issues

ug 27 10:52:02 172.18.0.1 - - [27/Aug/2024:14:52:02 +0000] "GET / HTTP/1.1" 200 1302 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 Edg/128.0.0.0"
Aug 27 10:52:02 172.18.0.1 - - [27/Aug/2024:14:52:02 +0000] "GET /api/v1/user HTTP/1.1" 401 41 "https://2fauth.experiencedmg.net/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 Edg/128.0.0.0"
Aug 27 10:52:04 172.18.0.1 - - [27/Aug/2024:14:52:04 +0000] "GET /socialite/redirect/openid HTTP/1.1" 302 1378 "https://2fauth.experiencedmg.net/login" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 Edg/128.0.0.0"
Aug 27 10:52:10 172.18.0.1 - - [27/Aug/2024:14:52:10 +0000] "GET / HTTP/1.1" 200 1298 "-" "Mozilla (CloudronHealth)"
Aug 27 10:52:20 172.18.0.1 - - [27/Aug/2024:14:52:20 +0000] "GET / HTTP/1.1" 200 1300 "-" "Mozilla (CloudronHealth)"
Aug 27 10:52:30 172.18.0.1 - - [27/Aug/2024:14:52:30 +0000] "GET / HTTP/1.1" 200 1297 "-" "Mozilla (CloudronHealth)"
Aug 27 10:52:40 172.18.0.1 - - [27/Aug/2024:14:52:40 +0000] "GET / HTTP/1.1" 200 1300 "-" "Mozilla (CloudronHealth)"
Aug 27 10:52:50 172.18.0.1 - - [27/Aug/2024:14:52:50 +0000] "GET / HTTP/1.1" 200 1302 "-" "Mozilla (CloudronHealth)"
Aug 27 10:53:00 172.18.0.1 - - [27/Aug/2024:14:53:00 +0000] "GET / HTTP/1.1" 200 1301 "-" "Mozilla (CloudronHealth)"
Aug 27 10:53:05 172.18.0.1 - - [27/Aug/2024:14:53:05 +0000] "GET /socialite/callback/openid?code===https%3A%2F%2Fmy.experiencedmg.net%2Fopenid HTTP/1.1" 504 578 "https://my.experiencedmg.net/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 Edg/128.0.0.0"
Aug 27 10:53:05 2024/08/27 14:53:05 [error] 69#69: 245 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.18.0.1, server: _, request: "GET /socialite/callback/openid?code=**&state==https%3A%2F%2Fmy.experiencedmg.net%2Fopenid HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.3-fpm.sock", ho

Hello,

I just installed 2FAuth and I tried signing in with OpenID so I can sign in with my Cloudron login, but it is not working at all. How do I go about fixing this since I am checking and resources are not even being pegged. It is showing a 110: Connection timed out error. The only thing I changed in the App Data was changing the Site_Owner to my e-mail.

Thanks,

@TheNils what was done for you to fix your issue? Probably not like the work around that I had to do

I was able to fix it by throwing the redis service for Chatwoot into debug mode and then waited 10 minutes, refreshed the dashboard and all the other apps started with no issues. Later the wiki.js app went none responsive so I restarted it and it was fine
Ended up updating my Cloudron server to Ubuntu 24.04 using your instructions and everything is stable again with no issues. I was able to take my backup of Chatwoot and reinstall it and everything is good. Guess version 8.0.3 does not like Ubuntu 22.04.3 very much

Can I please have a support member such as @girish or @nebulon to review this please. I have tried to fix it, but it is not going well

Here is a log showing the error with Chatwoot not working with redis:

Aug 12 09:36:00 box:services Waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e
Aug 12 09:36:00 box:services Attempt 1 failed. Will retry: Network error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e: connect ECONNREFUSED 172.18.0.11:3000
Aug 12 09:36:00 box:services startRedis: stopping and deleting previous redis container redis-87eca661-9dc4-4b00-8366-7cc47feb319e
Aug 12 09:36:10 box:services startRedis: starting redis container redis-87eca661-9dc4-4b00-8366-7cc47feb319e
Aug 12 09:36:10 box:shell startRedis exec: docker run --restart=always -d --name=redis-87eca661-9dc4-4b00-8366-7cc47feb319e --hostname redis-87eca661-9dc4-4b00-8366-7cc47feb319e --label=location=chatwoot.experiencedmg.net --net cloudron --net-alias redis-87eca661-9dc4-4b00-8366-7cc47feb319e --log-driver syslog --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock --log-opt syslog-format=rfc5424 --log-opt tag=redis-87eca661-9dc4-4b00-8366-7cc47feb319e -m 268435456 --memory-swap -1 -e CLOUDRON_REDIS_PASSWORD=7a843b3e461fcaed5c3a7c859eba8dc43f6fbd71ca16594e -e CLOUDRON_REDIS_TOKEN=85725a3ba6628732adcf7e0a7b17e4a220a14ee8df212249 -v /home/yellowtent/platformdata/redis/87eca661-9dc4-4b00-8366-7cc47feb319e:/var/lib/redis --label isCloudronManaged=true --read-only -v /tmp -v /run registry.docker.com/cloudron/redis:3.5.3@sha256:1e1200900c6fb196950531ecec43f400b4fe5e559fac1c75f21e6f0c11885b5f
Aug 12 09:36:11 box:services Waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e
Aug 12 09:36:11 box:services Attempt 1 failed. Will retry: Network error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e: connect ECONNREFUSED 172.18.0.11:3000
Aug 12 09:36:15 box:services Attempt 2 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:36:16 box:shell restartcollectd /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh collectd
Aug 12 09:36:26 box:services Attempt 2 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
Aug 12 09:36:30 box:services Attempt 3 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:36:41 box:services Attempt 3 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
Aug 12 09:36:45 box:services Attempt 4 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:36:56 box:services Attempt 4 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
[no timestamp] [ServiceUnavailableError]: Response timeout
[no timestamp] at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/connect-timeout/index.js:84:8)
[no timestamp] at IncomingMessage.emit (node:events:518:28)
[no timestamp] at Timeout._onTimeout (/home/yellowtent/box/node_modules/connect-timeout/index.js:49:11)
[no timestamp] at listOnTimeout (node:internal/timers:573:17)
[no timestamp] at process.processTimers (node:internal/timers:514:7) {
[no timestamp] code: 'ETIMEDOUT',
[no timestamp] timeout: 60000
[no timestamp] }
Aug 12 09:37:00 box:services Attempt 5 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:37:11 box:services Attempt 5 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
Aug 12 09:37:14 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
Aug 12 09:37:15 box:services Attempt 6 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:37:26 box:services Attempt 6 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
Aug 12 09:37:30 box:services Attempt 7 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:37:42 box:services Attempt 7 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
Aug 12 09:37:45 box:services Attempt 8 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:37:57 box:services Attempt 8 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
Aug 12 09:38:00 box:services Attempt 9 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:38:09 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
Aug 12 09:38:12 box:services Attempt 9 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
Aug 12 09:38:13 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
Aug 12 09:38:14 box:shell hasAVX execArgs: grep ["-q","avx","/proc/cpuinfo"]
Aug 12 09:38:14 box:shell statusUnbound execArgs: systemctl ["is-active","unbound"]
Aug 12 09:38:14 box:shell statusNginx execArgs: systemctl ["is-active","nginx"]
Aug 12 09:38:15 box:services Attempt 10 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:38:27 box:services Attempt 10 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
Aug 12 09:38:27 box:locker Lock unreleased infra_start
Aug 12 09:38:30 box:services Attempt 11 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined
Aug 12 09:38:42 box:services Attempt 11 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 200 message: process not running
Aug 12 09:38:45 box:services Attempt 12 failed. Will retry: Error waiting for redis-87eca661-9dc4-4b00-8366-7cc47feb319e. Status code: 401 message: undefined