After App and Redis stop Installation no more found by cloudron

[m-si]

After a bug in my peertube-instance I stopped the App and tried to restart the app via repair menu section (PeerTube 4.2.2, v7.2.5 (Ubuntu 20.04.3 LTS)). The app stop stopped the redis as well, therefore the restart of the app failed (after manually restarting redis) the app is no more “found” by my cloudron instance even though it is successfully running:

"You are seeing this page because the DNS record of ... is set to this server's IP but Cloudron has no app configured for this domain."

After complete uninstalling and reinstalling the app under the same subdomain the error persists. How am I able to "cleanup" the subdomains at least...?

After the app stop i found the following in the logs:

 npm ERR! path /app/code/server
Aug 19 18:54:24 npm ERR! command failed
Aug 19 18:54:24 npm ERR! signal SIGTERM
Aug 19 18:54:24 npm ERR! command sh -c node dist/server
Aug 19 18:54:24
Aug 19 18:53:25 Starting supervisor
Aug 19 18:53:26 2022-08-19 16:53:26,108 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
Aug 19 18:53:26 2022-08-19 16:53:26,108 INFO Included extra file "/etc/supervisor/conf.d/redis-service.conf" during parsing
Aug 19 18:53:26 2022-08-19 16:53:26,108 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
Aug 19 18:53:26 2022-08-19 16:53:26,113 INFO RPC interface 'supervisor' initialized
Aug 19 18:53:26 2022-08-19 16:53:26,113 CRIT Server 'inet_http_server' running without any HTTP authentication checking
Aug 19 18:53:26 2022-08-19 16:53:26,113 INFO RPC interface 'supervisor' initialized
Aug 19 18:53:26 2022-08-19 16:53:26,113 CRIT Server 'unix_http_server' running without any HTTP authentication checking
Aug 19 18:53:26 2022-08-19 16:53:26,113 INFO supervisord started with pid 1
Aug 19 18:53:27 2022-08-19 16:53:27,117 INFO spawned: 'redis' with pid 13
Aug 19 18:53:27 2022-08-19 16:53:27,120 INFO spawned: 'redis-service' with pid 14
Aug 19 18:53:27 13:C 19 Aug 2022 16:53:27.124 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 19 18:53:27 13:C 19 Aug 2022 16:53:27.124 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=13, just started
Aug 19 18:53:27 13:C 19 Aug 2022 16:53:27.124 # Configuration loaded
Aug 19 18:53:27 13:M 19 Aug 2022 16:53:27.125 * Running mode=standalone, port=6379.
Aug 19 18:53:27 13:M 19 Aug 2022 16:53:27.125 # Server initialized
Aug 19 18:53:27 13:M 19 Aug 2022 16:53:27.125 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
Aug 19 18:53:27 13:M 19 Aug 2022 16:53:27.125 * Ready to accept connections
Aug 19 18:53:27 Redis service endpoint listening on http://:::3000
Aug 19 18:53:28 2022-08-19 16:53:28,255 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Aug 19 18:53:28 2022-08-19 16:53:28,255 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Aug 19 18:53:40 [GET] /healthcheck
Aug 19 18:54:25 2022-08-19 16:54:25,223 WARN received SIGTERM indicating exit request
Aug 19 18:54:25 2022-08-19 16:54:25,224 INFO waiting for redis, redis-service to die
Aug 19 18:54:25 2022-08-19 16:54:25,226 INFO stopped: redis-service (terminated by SIGTERM)
Aug 19 18:54:25 13:signal-handler (1660928065) Received SIGTERM scheduling shutdown...
Aug 19 18:54:25 13:M 19 Aug 2022 16:54:25.314 # User requested shutdown...
Aug 19 18:54:25 13:M 19 Aug 2022 16:54:25.314 * Saving the final RDB snapshot before exiting.
Aug 19 18:54:25 13:M 19 Aug 2022 16:54:25.316 * DB saved on disk
Aug 19 18:54:25 13:M 19 Aug 2022 16:54:25.316 * Removing the pid file.
Aug 19 18:54:25 13:M 19 Aug 2022 16:54:25.316 # Redis is now ready to exit, bye bye...
Aug 19 18:54:25 2022-08-19 16:54:25,317 INFO stopped: redis (exit status 0)

As you can see, the redis seems to abnormally stops after the npm SIGTERM (or does this work as designed?)…the restart seems to be not successful in restarting the redis service after that...

[m-si]

Update:

Steps to reproduce:

1. go to cloudron app store install peertube
2. wait untill peertube reaches state running.
3. stop peertube
4. go to section repair in cloudron peertube app
5. select "restart app" and restart app.
6. try visit your youtube instance

After step 5. redis is stopped as well (without manual restart ist produces a ton of errors like:

2022-08-20T04:53:25.000Z [...:443] 2022-08-20 04:53:25.979 info: Connecting to redis...
2022-08-20T04:53:26.000Z [...:443] 2022-08-20 04:53:26.007 error: Error in job queue activitypub-http-fetcher. {
2022-08-20T04:53:26.000Z "err": {
2022-08-20T04:53:26.000Z "stack": "Error: getaddrinfo ENOTFOUND redis-876aae5e-572c-45d1-b48e-5176ba2e62fe\n    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)",
2022-08-20T04:53:26.000Z "message": "getaddrinfo ENOTFOUND redis-876aae5e-572c-45d1-b48e-5176ba2e62fe",
2022-08-20T04:53:26.000Z "errno": -3008,
2022-08-20T04:53:26.000Z "code": "ENOTFOUND",
2022-08-20T04:53:26.000Z "syscall": "getaddrinfo",
2022-08-20T04:53:26.000Z "hostname": "redis-876aae5e-572c-45d1-b48e-5176ba2e62fe"
2022-08-20T04:53:26.000Z }

and after step 6 one will see the following message:

You are seeing this page because the DNS record of ... is set to this server's IP but Cloudron has no app configured for this domain.

the message persists even after manually turning redis on and repeat steps 3. to 6.

[jdaviescoates]

@m-si said in After App and Redis stop Installation no more found by cloudron:

youtube

you mean Peertube

[nebulon]

Thanks for reporting this, indeed I am able to reproduce this and we have to fix the start/stop/restart logic here.

One workaround to get peertube working again is to start/stop the app and not using restart. I am not yet sure why it is this way but will investigate.

[nebulon]

We have pushed a change to fix this for the next release: https://git.cloudron.io/cloudron/box/-/commit/84ca85b315f75870a94abd8fdf749b43f412f721