cant start peertube after updateing latest cloudron

[awnzky]

@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

[joseph]

@awnzky looks like temp_file_limit is set to 4GB by default. What did you raise this to? How big is your peertube database dump ? you can check /home/yellowtent/appsdata/<appid>/postgresqldump . Maybe we can increase the default size even more in the code.

[awnzky]

its 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.

[joseph]

@awnzky i see, that's quie a large database. have you also given postgres a lot of memory? under Services -> Postgresql -> Configure

[awnzky]

i 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.

[awnzky]

i am using ubuntu 22 on Dual Xeon E5-2670 96GB memory.

[awnzky]

here 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

[nebulon]

Looks like you are hitting now a somewhat older issue with postgres. Does this fix work for you https://forum.cloudron.io/topic/11276/cloudron-update-to-7-7-0-postgresql-does-not-start/2?_=1723244919333 ?

[awnzky]

its 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.

[nebulon]

well glad it worked out somehow in the end.