Same problem in my peertube instance.
awnzky
Posts
-
Problem editing user quota – "User with this email already exists" error -
cant start peertube after updateing latest cloudronits working now. but with a little trick for my server. so i make postgree not start by making wrong custom.conf postgresql. the problem is when postgres start the server immediately crashes and can't do ssh or ping.
then i can enter dashboard and choose postgres recovery mode.thanks for your help.
-
cant start peertube after updateing latest cloudronhere some error log 2025-03-24T13:21:29Z server started 2025-03-24T13:21:29Z ==> Waiting for Postgres 2025-03-24T13:21:29Z pg_ctl: server is running (PID: 15) 2025-03-24T13:21:29Z /usr/lib/postgresql/16/bin/postgres "-D" "/var/lib/postgresql/16/main" 2025-03-24T13:21:29Z ==> Postgres is running 2025-03-24T13:21:29Z ==> Resetting root password 2025-03-24T13:21:29Z ALTER ROLE 2025-03-24T13:21:29Z ==> Upgrading pgvectors 2025-03-24T13:21:29Z ERROR: database "cloudronpgvectorupdate" already exists 2025-03-24T13:21:29Z 2025-03-24 13:21:29.801 UTC [30] root@postgres ERROR: database "cloudronpgvectorupdate" already exists 2025-03-24T13:21:29Z 2025-03-24 13:21:29.801 UTC [30] root@postgres STATEMENT: CREATE DATABASE cloudronpgvectorupdate 2025-03-24T13:22:30Z ==> Detected existing installation 2025-03-24T13:22:30Z ==> Copying updated config 2025-03-24T13:22:30Z ==> Updating existing postgresql 2025-03-24T13:22:30Z waiting for server to start....2025-03-24 13:22:30.157 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf" 2025-03-24T13:22:30Z 2025-03-24 13:22:30.157 GMT [15] LOG: skipping missing configuration file "/var/lib/postgresql/16/main/custom.conf" 2025-03-24T13:22:30Z 2025-03-24 13:22:30.186 UTC [15] LOG: starting PostgreSQL 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit 2025-03-24T13:22:30Z 2025-03-24 13:22:30.186 UTC [15] LOG: listening on IPv4 address "0.0.0.0", port 5432 2025-03-24T13:22:30Z 2025-03-24 13:22:30.186 UTC [15] LOG: listening on IPv6 address "::", port 5432 2025-03-24T13:22:30Z 2025-03-24 13:22:30.189 UTC [15] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2025-03-24T13:22:30Z 2025-03-24 13:22:30.195 UTC [18] LOG: database system was interrupted; last known up at 2025-03-24 13:21:29 UTC 2025-03-24T13:22:30Z 2025-03-24 13:22:30.315 UTC [18] LOG: database system was not properly shut down; automatic recovery in progress 2025-03-24T13:22:30Z 2025-03-24 13:22:30.318 UTC [18] LOG: redo starts at D/D9A09748 2025-03-24T13:22:30Z 2025-03-24 13:22:30.318 UTC [18] LOG: invalid record length at D/D9A0AE20: expected at least 24, got 0 2025-03-24T13:22:30Z 2025-03-24 13:22:30.318 UTC [18] LOG: redo done at D/D9A0ADC8 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2025-03-24T13:22:30Z 2025-03-24 13:22:30.326 UTC [16] LOG: checkpoint starting: end-of-recovery immediate wait 2025-03-24T13:22:30Z 2025-03-24 13:22:30.337 UTC [16] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=0.003 s, total=0.013 s; sync files=4, longest=0.001 s, average=0.001 s; distance=5 kB, estimate=5 kB; lsn=D/D9A0AE20, redo lsn=D/D9A0AE20 2025-03-24T13:22:30Z 2025-03-24 13:22:30.342 UTC [15] LOG: database system is ready to accept connections 2025-03-24T13:22:30Z done 2025-03-24T13:22:30Z server started 2025-03-24T13:22:30Z ==> Waiting for Postgres 2025-03-24T13:22:30Z pg_ctl: server is running (PID: 15) 2025-03-24T13:22:30Z /usr/lib/postgresql/16/bin/postgres "-D" "/var/lib/postgresql/16/main" 2025-03-24T13:22:30Z ==> Postgres is running 2025-03-24T13:22:30Z ==> Resetting root password 2025-03-24T13:22:30Z ALTER ROLE 2025-03-24T13:22:30Z ==> Upgrading pgvectors 2025-03-24T13:22:30Z 2025-03-24 13:22:30.509 UTC [30] root@postgres ERROR: database "cloudronpgvectorupdate" already exists 2025-03-24T13:22:30Z 2025-03-24 13:22:30.509 UTC [30] root@postgres STATEMENT: CREATE DATABASE cloudronpgvectorupdate 2025-03-24T13:22:30Z ERROR: database "cloudronpgvectorupdate" already exists
-
cant start peertube after updateing latest cloudroni am using ubuntu 22 on Dual Xeon E5-2670 96GB memory.
-
cant start peertube after updateing latest cloudroni give 36GB
how to view postgress error log. maybe it can be done through system rescue. but where is the config that I have to edit to stop postgress on booting..
i cant do anything in my server. just crashed. after postgressql start. -
cant start peertube after updateing latest cloudronits about 32GB. raise to 8GB.
i have new problem now. server crashed now. already remove custom.conf .
If I look at htop, it seems that when starting postgressql, the server cannot be accessed immediately. -
cant start peertube after updateing latest cloudron@joseph said in cant start peertube after updateing latest cloudron:
@awnzky interesting, so you had to create an empty
custom.conf
?i just copy paste from default conf. and rise temp_file_limit
-
cant start peertube after updateing latest cloudronnow my peertube is running. problem solved.
-
cant start peertube after updateing latest cloudronafter create custom custom.conf in /home/yellowtent/platformdata/postgresql/16/main# error message is gone.
my peertube still not responding.
error log
2025/03/24 02:04:50 [error] 316#316: *357 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: default_server, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:9000/", host:from htop showing process postges create index.
-
cant start peertube after updateing latest cloudronerror log
Mar 24 07:37:21 2025-03-24 00:37:21.628 UTC [1762] userf8ee153b7f89431b8a74be747b18e88c@dbf8ee153b7f89431b8a74be747b18e88c ERROR: temporary file size exceeds temp_file_limit (4194304kB) Mar 24 07:37:21 2025-03-24 00:37:21.628 UTC [1762] userf8ee153b7f89431b8a74be747b18e88c@dbf8ee153b7f89431b8a74be747b18e88c STATEMENT: CREATE UNIQUE INDEX "local_video_viewer_url" ON "localVideoViewer" ("url") Mar 24 07:37:21 2025-03-24 00:37:21.633 UTC [1763] FATAL: terminating background worker "parallel worker" due to administrator command Mar 24 07:37:21 2025-03-24 00:37:21.633 UTC [1763] STATEMENT: CREATE UNIQUE INDEX "local_video_viewer_url" ON "localVideoViewer" ("url") Mar 24 07:37:23 2025-03-24 00:37:23.380 UTC [47] LOG: background worker "parallel worker" (PID 1763) exited with exit code 1
-
Redis usage is quite large, 15GB, is that normal?I tried the FLUSHALL command from cloudron terminal, and it seems to be back to normal. I will monitor whether it will go up again.
-
Redis usage is quite large, 15GB, is that normal?yes. is busy peertube.
-
Redis usage is quite large, 15GB, is that normal?here is the log and while postgresql sql memory usage is very small
redis log
Mar 20 23:59:51 13:M 20 Mar 2025 16:59:51.327 * RDB memory usage when created 15005.03 Mb Mar 21 00:00:23 Redis service endpoint listening on http://:::3000 Mar 21 00:06:22 13:M 20 Mar 2025 17:06:22.756 * Done loading RDB, keys loaded: 33349358, keys expired: 998. Mar 21 00:06:22 13:M 20 Mar 2025 17:06:22.756 * DB loaded from disk: 391.667 seconds
-
my peertube and discourse error after auto updated cloudron to v7.4.0@girish yes, thank you...
-
my peertube and discourse error after auto updated cloudron to v7.4.0@girish at the moment it looks like the postgres restore process is complete. and in the app log there are no running tasks.
-
my peertube and discourse error after auto updated cloudron to v7.4.0@girish import task still running. on app log showing some error:
Apr 04 15:26:44 box:services pipeFileToRequest: timeout - connect or post-connect idle timeout Apr 04 15:26:44 box:apptask run: app error for state pending_import: Error: Request timedout at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1247:20) at Object.onceWrapper (node:events:627:28) at ClientRequest.emit (node:events:513:28) at Socket.emitRequestTimeout (node:_http_client:839:9) at Object.onceWrapper (node:events:627:28) at Socket.emit (node:events:525:35) at Socket._onTimeout (node:net:550:8) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7) Apr 04 15:26:45 box:taskworker Task took 2537.803 seconds Apr 04 15:26:45 box:tasks setCompleted - 13: {"result":null,"error":{"stack":"AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:\n\n assert(error instanceof BoxError)\n\n at makeTaskError (/home/yellowtent/box/src/apptask.js:48:5)\n at run (/home/yellowtent/box/src/apptask.js:816:86)\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)","message":"The expression evaluated to a falsy value:\n\n assert(error instanceof BoxError)\n","generatedMessage":true,"name":"AssertionError","code":"ERR_ASSERTION","actual":false,"expected":true,"operator":"=="}} Apr 04 15:26:45 box:tasks update 13: {"percent":100,"result":null,"error":{"stack":"AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:\n\n assert(error instanceof BoxError)\n\n at makeTaskError (/home/yellowtent/box/src/apptask.js:48:5)\n at run (/home/yellowtent/box/src/apptask.js:816:86)\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)","message":"The expression evaluated to a falsy value:\n\n assert(error instanceof BoxError)\n","generatedMessage":true,"name":"AssertionError","code":"ERR_ASSERTION","actual":false,"expected":true,"operator":"=="}} [ERR_ASSERTION]: The expression evaluated to a falsy value: assert(error instanceof BoxError) at makeTaskError (/home/yellowtent/box/src/apptask.js:48:5) at run (/home/yellowtent/box/src/apptask.js:816:86) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5)
-
my peertube and discourse error after auto updated cloudron to v7.4.0@girish thank you, the restore process is running. no errors so far. hopefully this restoring process is successful.
-
my peertube and discourse error after auto updated cloudron to v7.4.0trying to increase postgresql memory and still happen. now with reinstall new ubuntu and cloudron. error still persist. postgresqldump size about 18G
An error occurred during the import operation: Addons Error: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/f8ee153b-7f89-431b-8a74-be747b18e88c/postgresqldump to http://172.18.30.2:3000/databases/dbf8ee153b7f89431b8a74be747b18e88c/restore?access_token=6cd6f48e2c1270cd0a483c729fb92037486bc9dd7fe8bf312926757213b607997279217deb8ac60213817241e8909c5568c617b8852a9caacaacb9962c19c177d99e7e0ae0d8c5fc04175af27dfafe3b22e9c251a2b612b6d69bc588393146f339d5bd9c2cd6e53805a0a3ba93b980da0d5a788024ed496b4f7a55c222eab816&username=userf8ee153b7f89431b8a74be747b18e88c: status 408 complete false
app log :
Apr 03 22:02:25 box:services restoreAddons: restoring ["localstorage","postgresql","redis","sendmail","ldap"] Apr 03 22:02:25 box:services pipeFileToRequest: piping /home/yellowtent/appsdata/f8ee153b-7f89-431b-8a74-be747b18e88c/postgresqldump to http://172.18.30.2:3000/databases/dbf8ee153b7f89431b8a74be747b18e88c/restore?access_token=6cd6f48e2c1270cd0a483c729fb92037486bc9dd7fe8bf312926757213b607997279217deb8ac60213817241e8909c5568c617b8852a9caacaacb9962c19c177d99e7e0ae0d8c5fc04175af27dfafe3b22e9c251a2b612b6d69bc588393146f339d5bd9c2cd6e53805a0a3ba93b980da0d5a788024ed496b4f7a55c222eab816&username=userf8ee153b7f89431b8a74be747b18e88c Apr 03 22:07:31 box:services pipeFileToRequest: request completed with status code 408 Apr 03 22:07:31 box:apptask run: app error for state pending_import: BoxError: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/f8ee153b-7f89-431b-8a74-be747b18e88c/postgresqldump to http://172.18.30.2:3000/databases/dbf8ee153b7f89431b8a74be747b18e88c/restore?access_token=6cd6f48e2c1270cd0a483c729fb92037486bc9dd7fe8bf312926757213b607997279217deb8ac60213817241e8909c5568c617b8852a9caacaacb9962c19c177d99e7e0ae0d8c5fc04175af27dfafe3b22e9c251a2b612b6d69bc588393146f339d5bd9c2cd6e53805a0a3ba93b980da0d5a788024ed496b4f7a55c222eab816&username=userf8ee153b7f89431b8a74be747b18e88c: status 408 complete false Apr 03 22:07:33 box:taskworker Task took 2953.303 seconds Apr 03 22:07:33 box:tasks setCompleted - 5: {"result":null,"error":{"stack":"BoxError: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/f8ee153b-7f89-431b-8a74-be747b18e88c/postgresqldump to http://172.18.30.2:3000/databases/dbf8ee153b7f89431b8a74be747b18e88c/restore?access_token=6cd6f48e2c1270cd0a483c729fb92037486bc9dd7fe8bf312926757213b607997279217deb8ac60213817241e8909c5568c617b8852a9caacaacb9962c19c177d99e7e0ae0d8c5fc04175af27dfafe3b22e9c251a2b612b6d69bc588393146f339d5bd9c2cd6e53805a0a3ba93b980da0d5a788024ed496b4f7a55c222eab816&username=userf8ee153b7f89431b8a74be747b18e88c: status 408 complete false\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1252:60)\n at ClientRequest.emit (node:events:513:28)\n at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)\n at Socket.socketOnData (node:_http_client:534:22)\n at Socket.emit (node:events:513:28)\n at addChunk (node:internal/streams/readable:315:12)\n at readableAddChunk (node:internal/streams/readable:289:9)\n at Socket.Readable.push (node:internal/streams/readable:228:10)\n at TCP.onStreamRead (node:internal/stream_base_commons:190:23)","name":"BoxError","reason":"Addons Error","details":{},"message":"Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/f8ee153b-7f89-431b-8a74-be747b18e88c/postgresqldump to http://172.18.30.2:3000/databases/dbf8ee153b7f89431b8a74be747b18e88c/restore?access_token=6cd6f48e2c1270cd0a483c729fb92037486bc9dd7fe8bf312926757213b607997279217deb8ac60213817241e8909c5568c617b8852a9caacaacb9962c19c177d99e7e0ae0d8c5fc04175af27dfafe3b22e9c251a2b612b6d69bc588393146f339d5bd9c2cd6e53805a0a3ba93b980da0d5a788024ed496b4f7a55c222eab816&username=userf8ee153b7f89431b8a74be747b18e88c: status 408 complete false"}} Apr 03 22:07:33 box:tasks update 5: {"percent":100,"result":null,"error":{"stack":"BoxError: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/f8ee153b-7f89-431b-8a74-be747b18e88c/postgresqldump to http://172.18.30.2:3000/databases/dbf8ee153b7f89431b8a74be747b18e88c/restore?access_token=6cd6f48e2c1270cd0a483c729fb92037486bc9dd7fe8bf312926757213b607997279217deb8ac60213817241e8909c5568c617b8852a9caacaacb9962c19c177d99e7e0ae0d8c5fc04175af27dfafe3b22e9c251a2b612b6d69bc588393146f339d5bd9c2cd6e53805a0a3ba93b980da0d5a788024ed496b4f7a55c222eab816&username=userf8ee153b7f89431b8a74be747b18e88c: status 408 complete false\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1252:60)\n at ClientRequest.emit (node:events:513:28)\n at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)\n at Socket.socketOnData (node:_http_client:534:22)\n at Socket.emit (node:events:513:28)\n at addChunk (node:internal/streams/readable:315:12)\n at readableAddChunk (node:internal/streams/readable:289:9)\n at Socket.Readable.push (node:internal/streams/readable:228:10)\n at TCP.onStreamRead (node:internal/stream_base_commons:190:23)","name":"BoxError","reason":"Addons Error","details":{},"message":"Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/f8ee153b-7f89-431b-8a74-be747b18e88c/postgresqldump to http://172.18.30.2:3000/databases/dbf8ee153b7f89431b8a74be747b18e88c/restore?access_token=6cd6f48e2c1270cd0a483c729fb92037486bc9dd7fe8bf312926757213b607997279217deb8ac60213817241e8909c5568c617b8852a9caacaacb9962c19c177d99e7e0ae0d8c5fc04175af27dfafe3b22e9c251a2b612b6d69bc588393146f339d5bd9c2cd6e53805a0a3ba93b980da0d5a788024ed496b4f7a55c222eab816&username=userf8ee153b7f89431b8a74be747b18e88c: status 408 complete false"}} Apr 04 00:37:27 [GET] /healthcheck Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/f8ee153b-7f89-431b-8a74-be747b18e88c/postgresqldump to http://172.18.30.2:3000/databases/dbf8ee153b7f89431b8a74be747b18e88c/restore?access_token=6cd6f48e2c1270cd0a483c729fb92037486bc9dd7fe8bf312926757213b607997279217deb8ac60213817241e8909c5568c617b8852a9caacaacb9962c19c177d99e7e0ae0d8c5fc04175af27dfafe3b22e9c251a2b612b6d69bc588393146f339d5bd9c2cd6e53805a0a3ba93b980da0d5a788024ed496b4f7a55c222eab816&username=userf8ee153b7f89431b8a74be747b18e88c: status 408 complete false