Updating cloudron to 8.3.1 + installing new app issue

[mathieuepitech]

Hello,
I run into an issue yesterday that I still don't see how to fix it.

I update the cloudron to 8.3.1.
Just after the cloudron update, I install an new custom app that request postgresql.
But since, the box always try to restart 3 services, mysql, postgresql and mail.

After checking, the box try to make a postgresql dump backup of the custom app that is still installing, but the folder of this app doesn't exist yet.
So I create it manually, but now I got another issue, when the box ask to postgresql service to make a backup, it get a 404 error.

I check the app status it says:

Install state:   pending_install
Run state:       running

I tried to cancel installation or uninstall, but cannot because installation is pending.

Does anyone had this issue and how to fix it ?

First issue box log:

2025-05-17T09:38:32.514Z box:server ==========================================
2025-05-17T09:38:32.515Z box:server            Cloudron 8.3.1  
2025-05-17T09:38:32.515Z box:server ==========================================
2025-05-17T09:38:32.516Z box:platform initialize: start platform
2025-05-17T09:38:32.548Z box:tasks stopAllTasks: stopping all tasks
2025-05-17T09:38:32.549Z box:shell tasks /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2025-05-17T09:38:32.586Z box:shell All tasks stopped

2025-05-17T09:38:32.743Z box:locks releaseAll: all locks released
2025-05-17T09:38:32.748Z box:reverseproxy writeDashboardConfig: writing dashboard config for sanchezm.fr
2025-05-17T09:38:32.755Z box:shell reverseproxy: openssl x509 -in /home/yellowtent/platformdata/nginx/cert/_.sanchezm.fr.cert -noout -ocsp_uri
2025-05-17T09:38:32.801Z box:shell reverseproxy /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
2025-05-17T09:38:33.206Z box:shell 2025/05/17 09:38:32 [notice] 22143#22143: signal process started

2025-05-17T09:38:33.632Z box:platform onActivated: starting post activation services
2025-05-17T09:38:33.632Z box:platform startInfra: checking infrastructure
2025-05-17T09:38:33.633Z box:platform startInfra: updating infrastructure from 49.8.0 to 49.8.0
2025-05-17T09:38:33.633Z box:platform markApps: changedAddons: ["mysql","postgresql","mongodb","redis"]
2025-05-17T09:38:33.679Z box:apps restartAppsUsingAddons: marking test.woori.sanchezm.fr for restart
2025-05-17T09:38:33.778Z box:apps restartAppsUsingAddons: error marking test.woori.sanchezm.fr for restart: {"name":"BoxError","reason":"Bad State","details":{},"message":"Another task is scheduled for this app"}
2025-05-17T09:38:33.778Z box:services startServices: existing infra. incremental service create ["start","startTurn","startMysql","startPostgresql","startMongodb","startRedis","startGraphite","start"]
2025-05-17T09:38:33.778Z box:mailserver startMail: starting
2025-05-17T09:38:33.782Z box:mailserver restart: restarting mail container with mailFqdn:my.sanchezm.fr mailDomain:sanchezm.fr
2025-05-17T09:38:33.818Z box:locks write: current locks: {"mail_restart":null}
2025-05-17T09:38:33.818Z box:locks acquire: mail_restart
2025-05-17T09:38:33.827Z box:mailserver configureMail: stopping and deleting previous mail container
2025-05-17T09:38:34.636Z box:services getServiceLogs: getting logs for mysql
2025-05-17T09:38:34.665Z box:services getServiceLogs: getting logs for mail
2025-05-17T09:38:34.669Z box:services getServiceLogs: getting logs for mail
2025-05-17T09:38:39.000Z box:mailserver createMailConfig: generating mail config with my.sanchezm.fr
2025-05-17T09:38:39.004Z box:mailserver configureMail: starting mail container
2025-05-17T09:38:39.004Z box:shell mailserver: /bin/bash -c docker run --restart=always -d --name=mail                 --net cloudron                 --net-alias mail                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mail                 -m 536870912                 --memory-swap -1                 --dns 172.18.0.1                 --dns-search=.                 --ip 172.18.30.4                 -e CLOUDRON_MAIL_TOKEN=751adda287387ac809f3d1bf767b20629e94485f2a766175593332e0ebd463b5164a425c2dcf2763dfaf88243e89f6760df5a6f076ec4f966436c023e64746b752cefac53439e94047e18df6c72abd6b6ce4259436ffb4967f5a2d96082ea3ca05bef4ab70445d312d9bb5a563501188f8887eae9510de0f6e8af72bf165fc51                 -e CLOUDRON_RELAY_TOKEN=e9c08742fbd477e4295974ba2a61f6999074e3c3bf3516b968dff37c08f91bef7b924dc6f52f5fb3c582907ac295f01eb99787ede00b251c3aa5b8c88fc0b80bf85b1b100629b43853100e4f76c81e970004416e7074162b28ae85ef3d29de994a9b76db3a313b433248aa8cc40bd549b6051c18a1b69afc095bf59f71e6402e                 -e LOGLEVEL=info                 -v /home/yellowtent/boxdata/mail:/app/data                 -v /home/yellowtent/platformdata/addons/mail:/etc/mail:ro                 -p 587:2587 -p 993:9993 -p 4190:4190 -p 25:2587 -p 465:2465 -p 995:9995                 --label isCloudronManaged=true                 --read-only -v /run -v /tmp registry.docker.com/cloudron/mail:3.15.0@sha256:c93b5a83fc4e775bda4e05010bd19e5a658936e7a09cf7e51281e3696fde4536 
2025-05-17T09:38:43.122Z box:locks write: current locks: {}
2025-05-17T09:38:43.122Z box:locks release: mail_restart
2025-05-17T09:38:43.122Z box:docker deleteImage: removing registry.docker.com/cloudron/mail:3.14.9@sha256:c51a2ee20b2087e208084a9115cc6a525e3b3b227b52d8cfdac2d98a6409672e
2025-05-17T09:38:43.131Z box:services startTurn: stopping and deleting previous turn container
2025-05-17T09:38:54.248Z box:services startTurn: starting turn container
2025-05-17T09:38:54.248Z box:shell services: /bin/bash -c docker run --restart=always -d --name=turn                 --hostname turn                 --net host                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=turn                 -m 536870912                 --memory-swap -1                 -e CLOUDRON_TURN_SECRET=a29a97bdb506203714ef3c6b5fb50e1                 -e CLOUDRON_REALM=my.sanchezm.fr                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/turn:1.8.0@sha256:cdbe83c3c83b8f25de3a5814b121eb941b457dca7127d2e6ff446c7a0cfa1570 
2025-05-17T09:38:55.781Z box:docker deleteImage: removing registry.docker.com/cloudron/turn:1.7.2@sha256:9ed8da613c1edc5cb8700657cf6e49f0f285b446222a8f459f80919945352f6d
2025-05-17T09:38:55.785Z box:services startMysql: stopping and deleting previous mysql container
2025-05-17T09:39:00.206Z box:services startMysql: starting mysql container
2025-05-17T09:39:00.206Z box:shell services: /bin/bash -c docker run --restart=always -d --name=mysql                 --hostname mysql                 --net cloudron                 --net-alias mysql                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mysql                 --ip 172.18.30.1                 -e CLOUDRON_MYSQL_TOKEN=99de18482b36f56f14140669d5d62465c8bc201df9d501f52c21f81ada5bb7a9ea2a351a5eb81990b3fcf69d4b1a2d2e03c8b90da511d7ae2b4f66a3b901defc8f4653665a3d1e863c835da0c311f9bd12470f02d2b2b3179dd4c0aa662702066215ebef49f86093ac02f6b69e0170ecbf61fd6d2d8ea4ee38a6cc05e494c18a                 -e CLOUDRON_MYSQL_ROOT_HOST=172.18.0.1                 -e CLOUDRON_MYSQL_ROOT_PASSWORD=56d44a0fa68c985761d93634b59e23bc7870837a2c215e280186338253fdb56f7c3e7299f4dfa4dc8edf335552b4178c94e933719c308c798e3164d46789bc1186aa80f79b57f5c07a04c4b4e5b4a9bfda62efba37b3aa144bb6de4a3fce6acfd554a43bd5c9646845a8e503f997008bdd49f84a7bc4ba94742b3361d6dc16b8                 -v /home/yellowtent/platformdata/mysql:/var/lib/mysql                 --label isCloudronManaged=true                 --cap-add SYS_NICE                 --read-only -v /tmp -v /run registry.docker.com/cloudron/mysql:3.5.0@sha256:969ea5b2f91861940ca6309c7676c52e479d2a864ba3aabd08a4266799707280 
2025-05-17T09:39:01.949Z box:services Waiting for mysql
2025-05-17T09:39:01.962Z box:services Attempt 1 failed. Will retry: Network error waiting for mysql: connect ECONNREFUSED 172.18.30.1:3000
2025-05-17T09:39:17.224Z box:services Attempt 2 failed. Will retry: Error waiting for mysql. Status code: 200 message: connect ECONNREFUSED 127.0.0.1:3306
2025-05-17T09:39:32.473Z box:docker deleteImage: removing registry.docker.com/cloudron/mysql:3.4.3@sha256:8934c5ddcd69f24740d9a38f0de2937e47240238f3b8f5c482862eeccc5a21d2
2025-05-17T09:39:32.478Z box:services startPostgresql: postgresql will be upgraded
2025-05-17T09:39:32.479Z box:services exportDatabase: Exporting postgresql
2025-05-17T09:39:32.487Z box:services exportDatabase: Exporting addon postgresql of app 62b254e8-5ac7-4e09-92c1-c851acb28cd0
2025-05-17T09:39:32.487Z box:services Backing up postgresql
2025-05-17T09:39:33.108Z box:services pipeRequestToFile: connected with status code 200
2025-05-17T09:39:33.136Z box:services exportDatabase: Exporting addon postgresql of app 651e1123-08e7-46ef-aa50-1aaaa36f2417
2025-05-17T09:39:33.136Z box:services Backing up postgresql
2025-05-17T09:39:33.139Z Error: EACCES: permission denied, open '/home/yellowtent/appsdata/651e1123-08e7-46ef-aa50-1aaaa36f2417/postgresqldump'

Second issue box log:

2025-05-17T09:48:45.779Z box:server ==========================================
2025-05-17T09:48:45.780Z box:server            Cloudron 8.3.1  
2025-05-17T09:48:45.780Z box:server ==========================================
2025-05-17T09:48:45.780Z box:platform initialize: start platform
2025-05-17T09:48:46.180Z box:tasks stopAllTasks: stopping all tasks
2025-05-17T09:48:46.181Z box:shell tasks /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2025-05-17T09:48:46.605Z box:shell All tasks stopped

2025-05-17T09:48:47.147Z box:locks releaseAll: all locks released
2025-05-17T09:48:47.157Z box:reverseproxy writeDashboardConfig: writing dashboard config for sanchezm.fr
2025-05-17T09:48:47.361Z box:shell reverseproxy: openssl x509 -in /home/yellowtent/platformdata/nginx/cert/_.sanchezm.fr.cert -noout -ocsp_uri
2025-05-17T09:48:48.005Z box:shell reverseproxy /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
2025-05-17T09:48:48.539Z box:shell 2025/05/17 09:48:48 [notice] 1621#1621: signal process started

2025-05-17T09:49:07.972Z box:platform onActivated: starting post activation services
2025-05-17T09:49:07.972Z box:platform startInfra: checking infrastructure
2025-05-17T09:49:08.073Z box:platform startInfra: updating infrastructure from 49.8.0 to 49.8.0
2025-05-17T09:49:08.074Z box:platform markApps: changedAddons: ["mysql","postgresql","mongodb","redis"]
2025-05-17T09:49:09.307Z box:apps restartAppsUsingAddons: marking test.woori.sanchezm.fr for restart
2025-05-17T09:49:17.310Z box:apps restartAppsUsingAddons: error marking test.woori.sanchezm.fr for restart: {"name":"BoxError","reason":"Bad State","details":{},"message":"Another task is scheduled for this app"}
2025-05-17T09:49:17.310Z box:services startServices: existing infra. incremental service create ["start","startTurn","startMysql","startPostgresql","startMongodb","startRedis","startGraphite","start"]
2025-05-17T09:49:17.311Z box:mailserver startMail: starting
2025-05-17T09:49:17.315Z box:mailserver restart: restarting mail container with mailFqdn:my.sanchezm.fr mailDomain:sanchezm.fr
2025-05-17T09:49:17.495Z box:locks write: current locks: {"mail_restart":null}
2025-05-17T09:49:17.495Z box:locks acquire: mail_restart
2025-05-17T09:49:17.502Z box:mailserver configureMail: stopping and deleting previous mail container
2025-05-17T09:49:40.774Z box:mailserver createMailConfig: generating mail config with my.sanchezm.fr
2025-05-17T09:49:41.283Z box:mailserver configureMail: starting mail container
2025-05-17T09:49:41.284Z box:shell mailserver: /bin/bash -c docker run --restart=always -d --name=mail                 --net cloudron                 --net-alias mail                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mail                 -m 536870912                 --memory-swap -1                 --dns 172.18.0.1                 --dns-search=.                 --ip 172.18.30.4                 -e CLOUDRON_MAIL_TOKEN=64d9d469e2d29303a417e909e57f5e4c5c5eb214f458cadc0151052302af14c5899af898ddd586b4866e4c8af272f3ba19b4d4f4b6a4c9a7bda368ec2e9472f384e8539ba7548a7da1947d67807fbe9cc053288086f72cde20ba3c3c7ecd65102893757d23243642282b8f6ab12a3a85c2ee82793944d1e30755e6797c3cd925                 -e CLOUDRON_RELAY_TOKEN=d1dc82f34063f4e674f4b1092ab02faa73d97a049f1e881dd842a7863d5481ab336a452bb796b3d40964585fa127450406debc125bc42edb05bb14383318e70f97453ec126187d5b281b9bb03c09f3c6c2b04ebd8df56fdd7d5a0eaffc87beccc2da9b45cfb5546477094b66296a47ad41eab12ae2070e90658d7c7b67e7fae4                 -e LOGLEVEL=info                 -v /home/yellowtent/boxdata/mail:/app/data                 -v /home/yellowtent/platformdata/addons/mail:/etc/mail:ro                 -p 587:2587 -p 993:9993 -p 4190:4190 -p 25:2587 -p 465:2465 -p 995:9995                 --label isCloudronManaged=true                 --read-only -v /run -v /tmp registry.docker.com/cloudron/mail:3.15.0@sha256:c93b5a83fc4e775bda4e05010bd19e5a658936e7a09cf7e51281e3696fde4536 
2025-05-17T09:50:26.502Z box:services getServiceLogs: getting logs for postgresql
2025-05-17T09:51:03.221Z box:services getServiceLogs: getting logs for mail
2025-05-17T09:51:03.878Z box:services getServiceLogs: getting logs for mysql
2025-05-17T09:51:14.146Z box:shell system: swapon --noheadings --raw --bytes --show=type,size,used,name
2025-05-17T09:51:14.964Z box:shell services: grep -q avx /proc/cpuinfo
2025-05-17T09:51:15.547Z box:shell services: systemctl is-active unbound
2025-05-17T09:51:15.899Z box:shell services: systemctl is-active nginx
2025-05-17T09:52:31.924Z box:locks write: current locks: {}
2025-05-17T09:52:31.924Z box:locks release: mail_restart
2025-05-17T09:52:31.924Z box:docker deleteImage: removing registry.docker.com/cloudron/mail:3.14.9@sha256:c51a2ee20b2087e208084a9115cc6a525e3b3b227b52d8cfdac2d98a6409672e
2025-05-17T09:52:31.931Z box:services startTurn: stopping and deleting previous turn container
2025-05-17T09:52:46.208Z box:services startTurn: starting turn container
2025-05-17T09:52:46.208Z box:shell services: /bin/bash -c docker run --restart=always -d --name=turn                 --hostname turn                 --net host                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=turn                 -m 536870912                 --memory-swap -1                 -e CLOUDRON_TURN_SECRET=a29a97bdb506203714ef3c6b5fb50e1                 -e CLOUDRON_REALM=my.sanchezm.fr                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/turn:1.8.0@sha256:cdbe83c3c83b8f25de3a5814b121eb941b457dca7127d2e6ff446c7a0cfa1570 
2025-05-17T09:52:50.293Z box:docker deleteImage: removing registry.docker.com/cloudron/turn:1.7.2@sha256:9ed8da613c1edc5cb8700657cf6e49f0f285b446222a8f459f80919945352f6d
2025-05-17T09:52:50.297Z box:services startMysql: stopping and deleting previous mysql container
2025-05-17T09:52:58.207Z box:services startMysql: starting mysql container
2025-05-17T09:52:58.207Z box:shell services: /bin/bash -c docker run --restart=always -d --name=mysql                 --hostname mysql                 --net cloudron                 --net-alias mysql                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mysql                 --ip 172.18.30.1                 -e CLOUDRON_MYSQL_TOKEN=21abde10de7858fd8c248703cd1aaccc8c8b84ac2db28d2b1e73f6c57f4ed362f350ba55c86dda519ce841338ce1a447192846c7765bf6971ed416ddb5efdd053db271a4498b2a7d5c2ff892449710f1a3e7285d5c39dbcfb8f6ce7bd2fab528daa15faeea64ae874e499fc4981d40596140a9c4c286e79e22d895b836f28ace                 -e CLOUDRON_MYSQL_ROOT_HOST=172.18.0.1                 -e CLOUDRON_MYSQL_ROOT_PASSWORD=c66d31e786f29fec6217355823eb2efe5d485d93d9b80da0f12f26e3d088ba3649367e675d0c5247bcd745bd1df3fc5d5e9ffc2bd3176259c558a3a072de4297e421991a1f6a953971dcc3d84260c6db53951c5f02f767d7b916e6054a6998a2e86ccce13ee655a419f90909fe7caf4aa3bee5f4079e0ae48b1bc7f5d4be40bf                 -v /home/yellowtent/platformdata/mysql:/var/lib/mysql                 --label isCloudronManaged=true                 --cap-add SYS_NICE                 --read-only -v /tmp -v /run registry.docker.com/cloudron/mysql:3.5.0@sha256:969ea5b2f91861940ca6309c7676c52e479d2a864ba3aabd08a4266799707280 
2025-05-17T09:53:09.694Z box:services Waiting for mysql
2025-05-17T09:53:09.699Z box:services Attempt 1 failed. Will retry: Network error waiting for mysql: connect ECONNREFUSED 172.18.30.1:3000
2025-05-17T09:53:24.701Z box:services Attempt 2 failed. Will retry: Network error waiting for mysql: connect ECONNREFUSED 172.18.30.1:3000
2025-05-17T09:53:39.705Z box:services Attempt 3 failed. Will retry: Network error waiting for mysql: connect ECONNREFUSED 172.18.30.1:3000
2025-05-17T09:53:55.523Z box:services Attempt 4 failed. Will retry: Error waiting for mysql. Status code: 200 message: connect ECONNREFUSED 127.0.0.1:3306
2025-05-17T09:54:11.331Z box:docker deleteImage: removing registry.docker.com/cloudron/mysql:3.4.3@sha256:8934c5ddcd69f24740d9a38f0de2937e47240238f3b8f5c482862eeccc5a21d2
2025-05-17T09:54:11.334Z box:services startPostgresql: postgresql will be upgraded
2025-05-17T09:54:11.334Z box:services exportDatabase: Exporting postgresql
2025-05-17T09:54:11.340Z box:services exportDatabase: Exporting addon postgresql of app 62b254e8-5ac7-4e09-92c1-c851acb28cd0
2025-05-17T09:54:11.340Z box:services Backing up postgresql
2025-05-17T09:54:17.783Z box:services pipeRequestToFile: connected with status code 200
2025-05-17T09:54:18.774Z box:services exportDatabase: Exporting addon postgresql of app 651e1123-08e7-46ef-aa50-1aaaa36f2417
2025-05-17T09:54:18.774Z box:services Backing up postgresql
2025-05-17T09:54:18.790Z box:services pipeRequestToFile: connected with status code 404
2025-05-17T09:54:18.792Z box:services exportDatabase: Error exporting postgresql of app 651e1123-08e7-46ef-aa50-1aaaa36f2417. BoxError: Unexpected response code or HTTP error when piping http://172.18.30.2:3000/databases/db651e112308e746efaa501aaaa36f2417/backup?access_token=d5e3ea46728d9d921ee9476e157a388b01954dcc128061612c187cfefd0fcd2cbabc67dd8864f37f1a217f81a8eeb5813184f8aab28f5b9abdb413e94c4dad677c5b4bc5088a118a0fb1ed15b3691a66d8dbabcc9f61c48ed4fb6b9bf53037bb4127cf62841fdf00233087ef468e1c253b1e361753898a12122ac1e2fcf4a715 to /home/yellowtent/appsdata/651e1123-08e7-46ef-aa50-1aaaa36f2417/postgresqldump: status 404 at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1353:60) at ClientRequest.emit (node:events:519:28) at ClientRequest.emit (node:domain:488:12) at HTTPParser.parserOnIncomingClient (node:_http_client:702:27) at HTTPParser.parserOnHeadersComplete (node:_http_common:118:17) at Socket.socketOnData (node:_http_client:544:22) at Socket.emit (node:events:519:28) at Socket.emit (node:domain:488:12) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) at Readable.push (node:internal/streams/readable:390:5) at TCP.onStreamRead (node:internal/stream_base_commons:191:23) { reason: 'Addons Error', details: {} }
2025-05-17T09:54:18.792Z box:platform startInfra: Failed to start services. retry=false (attempt 0): Unexpected response code or HTTP error when piping http://172.18.30.2:3000/databases/db651e112308e746efaa501aaaa36f2417/backup?access_token=d5e3ea46728d9d921ee9476e157a388b01954dcc128061612c187cfefd0fcd2cbabc67dd8864f37f1a217f81a8eeb5813184f8aab28f5b9abdb413e94c4dad677c5b4bc5088a118a0fb1ed15b3691a66d8dbabcc9f61c48ed4fb6b9bf53037bb4127cf62841fdf00233087ef468e1c253b1e361753898a12122ac1e2fcf4a715 to /home/yellowtent/appsdata/651e1123-08e7-46ef-aa50-1aaaa36f2417/postgresqldump: status 404
2025-05-17T09:54:18.792Z box:platform BoxError: Unexpected response code or HTTP error when piping http://172.18.30.2:3000/databases/db651e112308e746efaa501aaaa36f2417/backup?access_token=d5e3ea46728d9d921ee9476e157a388b01954dcc128061612c187cfefd0fcd2cbabc67dd8864f37f1a217f81a8eeb5813184f8aab28f5b9abdb413e94c4dad677c5b4bc5088a118a0fb1ed15b3691a66d8dbabcc9f61c48ed4fb6b9bf53037bb4127cf62841fdf00233087ef468e1c253b1e361753898a12122ac1e2fcf4a715 to /home/yellowtent/appsdata/651e1123-08e7-46ef-aa50-1aaaa36f2417/postgresqldump: status 404
    at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1353:60)
    at ClientRequest.emit (node:events:519:28)
    at ClientRequest.emit (node:domain:488:12)
    at HTTPParser.parserOnIncomingClient (node:_http_client:702:27)
    at HTTPParser.parserOnHeadersComplete (node:_http_common:118:17)
    at Socket.socketOnData (node:_http_client:544:22)
    at Socket.emit (node:events:519:28)
    at Socket.emit (node:domain:488:12)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:191:23)

Postgresql service logs:

2025-05-17T09:49:08Z ==> Detected existing installation
2025-05-17T09:49:13Z ==> Copying updated config
2025-05-17T09:49:13Z ==> Updating existing postgresql
2025-05-17T09:49:30Z waiting for server to start........2025-05-17 09:49:30.508 UTC [14] LOG:  starting PostgreSQL 14.15 (Ubuntu 14.15-0ubuntu0.22.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-05-17T09:49:30Z 2025-05-17 09:49:30.508 UTC [14] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-05-17T09:49:30Z 2025-05-17 09:49:30.508 UTC [14] LOG:  listening on IPv6 address "::", port 5432
2025-05-17T09:49:31Z .2025-05-17 09:49:31.143 UTC [14] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-05-17T09:49:32Z .2025-05-17 09:49:32.355 UTC [15] LOG:  database system was shut down at 2025-05-17 09:47:01 UTC
2025-05-17T09:49:33Z .2025-05-17 09:49:33.538 UTC [14] LOG:  database system is ready to accept connections
2025-05-17T09:49:33Z done
2025-05-17T09:49:33Z server started
2025-05-17T09:49:33Z ==> Waiting for Postgres
2025-05-17T09:49:33Z pg_ctl: server is running (PID: 14)
2025-05-17T09:49:33Z /usr/lib/postgresql/14/bin/postgres "-D" "/var/lib/postgresql/14/main"
2025-05-17T09:49:33Z ==> Postgres is running
2025-05-17T09:49:33Z ==> Resetting root password
2025-05-17T09:49:40Z ALTER ROLE
2025-05-17T09:49:40Z ==> Upgrading pgvectors
2025-05-17T09:50:17Z CREATE DATABASE
2025-05-17T09:50:19Z CREATE EXTENSION
2025-05-17T09:50:19Z 2025-05-17 09:50:19.467 UTC [35] root@cloudronpgvectorupdate WARNING:  pgvecto.rs is upgraded. Restart PostgreSQL to take effects.
2025-05-17T09:50:22Z DROP DATABASE
2025-05-17T09:50:22Z ==> Stopping postgresql
2025-05-17T09:50:22Z 2025-05-17 09:50:22.163 UTC [14] LOG:  received fast shutdown request
2025-05-17T09:50:22Z waiting for server to shut down....2025-05-17 09:50:22.405 UTC [14] LOG:  aborting any active transactions
2025-05-17T09:50:22Z 2025-05-17 09:50:22.408 UTC [14] LOG:  background worker "logical replication launcher" (PID 22) exited with exit code 1
2025-05-17T09:50:22Z 2025-05-17 09:50:22.439 UTC [17] LOG:  shutting down
2025-05-17T09:50:24Z ..2025-05-17 09:50:24.668 UTC [14] LOG:  database system is shut down
2025-05-17T09:50:24Z done
2025-05-17T09:50:24Z server stopped
2025-05-17T09:50:24Z ==> Starting supervisor
2025-05-17T09:50:26Z 2025-05-17 09:50:26,237 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.
2025-05-17T09:50:26Z 2025-05-17 09:50:26,390 INFO Included extra file "/etc/supervisor/conf.d/postgresql-service.conf" during parsing
2025-05-17T09:50:26Z 2025-05-17 09:50:26,390 INFO Included extra file "/etc/supervisor/conf.d/postgresql.conf" during parsing
2025-05-17T09:50:26Z 2025-05-17 09:50:26,394 INFO RPC interface 'supervisor' initialized
2025-05-17T09:50:26Z 2025-05-17 09:50:26,395 CRIT Server 'inet_http_server' running without any HTTP authentication checking
2025-05-17T09:50:26Z 2025-05-17 09:50:26,395 INFO RPC interface 'supervisor' initialized
2025-05-17T09:50:26Z 2025-05-17 09:50:26,395 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-05-17T09:50:26Z 2025-05-17 09:50:26,395 INFO supervisord started with pid 1
2025-05-17T09:50:27Z 2025-05-17 09:50:27,398 INFO spawned: 'postgresql' with pid 41
2025-05-17T09:50:27Z 2025-05-17 09:50:27,401 INFO spawned: 'postgresql-service' with pid 42
2025-05-17T09:50:28Z 2025-05-17 09:50:28.131 UTC [41] LOG:  starting PostgreSQL 14.15 (Ubuntu 14.15-0ubuntu0.22.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-05-17T09:50:28Z 2025-05-17 09:50:28.131 UTC [41] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-05-17T09:50:28Z 2025-05-17 09:50:28.131 UTC [41] LOG:  listening on IPv6 address "::", port 5432
2025-05-17T09:50:28Z 2025-05-17 09:50:28.811 UTC [41] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-05-17T09:50:28Z 2025-05-17 09:50:28,811 INFO success: postgresql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-17T09:50:28Z 2025-05-17 09:50:28,811 INFO success: postgresql-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-17T09:50:29Z 2025-05-17 09:50:29.465 UTC [49] LOG:  database system was shut down at 2025-05-17 09:50:24 UTC
2025-05-17T09:50:29Z 2025-05-17 09:50:29.814 UTC [41] LOG:  database system is ready to accept connections
2025-05-17T09:50:56Z PostgreSQL service endpoint listening on http://:::3000
2025-05-17T09:51:15Z [GET] /healthcheck
2025-05-17T09:51:16Z healthcheck: disconnected
2025-05-17T09:54:11Z [POST] /databases/db62b254e85ac74e0992c1c851acb28cd0/backup
2025-05-17T09:54:11Z exists: disconnected
2025-05-17T09:54:18Z backup: successfully dumped database db62b254e85ac74e0992c1c851acb28cd0
2025-05-17T09:54:18Z [POST] /databases/db651e112308e746efaa501aaaa36f2417/backup
2025-05-17T09:54:18Z exists: disconnected

[joseph]

@mathieuepitech said in Updating cloudron to 8.3.1 + installing new app issue:

So I create it manually,

You shouldn't have to but if you did it should be owned by yellowtent . The box code runs as normal user and won't have permissions otherwise. This is the error in the first case.

The second case possibly is also failing for the same reason. The export is failing (pre migration task) possibly because it cannot write dumps in the app folder .

[mathieuepitech]

@joseph I know I shouldn't have to create the forlder manually, but I wanted to try to debug myself.
Of course I set the owner of this folder as yellowtent.
And I create it after I got this error.

For the second error, if you look at this line 2025-05-17T09:54:18.792Z box:platform BoxError: Unexpected response code or HTTP error when piping http://172.18.30.2:3000/databases/db651e112308e746efaa501aaaa36f2417/backup?access_token=d5e3ea46728d9d921ee9476e157a388b01954dcc128061612c187cfefd0fcd2cbabc67dd8864f37f1a217f81a8eeb5813184f8aab28f5b9abdb413e94c4dad677c5b4bc5088a118a0fb1ed15b3691a66d8dbabcc9f61c48ed4fb6b9bf53037bb4127cf62841fdf00233087ef468e1c253b1e361753898a12122ac1e2fcf4a715 to /home/yellowtent/appsdata/651e1123-08e7-46ef-aa50-1aaaa36f2417/postgresqldump: status 404
You see that the postgres service return a 404 error because the database (I assume for the new created app) doesn't exist yet.

I found it weird that the run state of my application is running, when it hasn't even been installed yet.

[joseph]

@mathieuepitech have you tried https://docs.cloudron.io/services/#corrupt-addon already?

[mathieuepitech]

@joseph Yes I tried, but all my apps using postgresql are in pending_restart / running state and I cannot stop them.
And the new app I just install is in pending_install / running state.

Do you have any idea how I can force uninstall the new app ? I'm pretty sure it's causing the issue because I installed before the fully finish

[james]

Hello @mathieuepitech

I am sadly not aware of a force option at the moment.

Disclaimer - the following suggestions and instructions should only be performed by people with a deepened knowledge about docker and Cloudron.

---

If you assume that the new app is causing this error with PostgreSQL you can try to forcefully stop the docker container of the app.

From what you've posted so far I will skip basic guidance and treat you as a more experienced user.
Run docker ps find your new app by appid or image name.
Stop the app with docker stop $ID
Restart the box.service with systemctl restart box.service after that, make sure the stopped docker container is still stopped.
Go into your dashboard and restart the PostgreSQL service and keep the logs for that one open.
Now restart all the other pending apps.

Please report back if this helped in any way, and please provide the log of PostgreSQL after you are done so I can further analyze what went wrong here.

[joseph]

@mathieuepitech I think systemctl restart box will help here. I think the box code is probably stuck in thinking postgresql is still not starting properly.

[mathieuepitech]

@james Thanks for the suggestion, I didn't think about stopping the docker container directly.
I try to, but the container doesn't exist yet.

For you information, my app is int this state on the UI Installing - Waiting for platform to initialize.

Do you know if I can remove the app directly in the box database ?

[mathieuepitech]

So I connect to the hosted mysql to check the box database directly.
Firstly, my new app was in installationState: peding_install and runState: running and without containerId.
I first try to set it to runState: stopped, but didn't work.
So delete the row (and the location du to foreign key).
Please tell me if you think I need to check/delete other data to clean up totally my app.

And now it worked. So the issue, for me, it's that you upgrade from postgresql 14 to 16, to do so, postgresql need to backup every application using postgresql, but before backuping all the postgresql apps, I run installation of a new app.
So the box try to backup also the new app but did have the folder created in /home/yellowtent/appsdata and also doesn't have the database created in the postgresql service.

You can find box and postgresql files here: https://limewire.com/d/nNa7A#br1SRvFEvY
(the files will be remove in 7 days).

[james]

@mathieuepitech
Great analysis!
@staff will be very interested about this for further improvement to circumvent such scenarios.