postgresql not crushing after increasing volume

after increasing the volume and successfully deploy, i'm receiving this error when trying to connect

2024-09-14 02:16:17.932 UTC [5] LOG:  starting PostgreSQL 16.3 (Debian 16.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit

2024-09-14 02:16:17.932 UTC [5] LOG:  listening on IPv4 address "0.0.0.0", port 5432

2024-09-14 02:16:17.932 UTC [5] LOG:  listening on IPv6 address "::", port 5432

2024-09-14 02:16:17.937 UTC [5] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2024-09-14 02:16:17.944 UTC [28] LOG:  database system was interrupted; last known up at 2024-09-14 02:00:14 UTC

2024-09-14 02:16:17.990 UTC [28] LOG:  database system was not properly shut down; automatic recovery in progress

2024-09-14 02:16:17.993 UTC [28] LOG:  redo starts at 0/1418EAE0

2024-09-14 02:16:17.993 UTC [28] LOG:  invalid record length at 0/1418EB18: expected at least 24, got 0

2024-09-14 02:16:17.993 UTC [28] LOG:  redo done at 0/1418EAE0 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

2024-09-14 02:16:17.932 UTC [5] LOG:  starting PostgreSQL 16.3 (Debian 16.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit

2024-09-14 02:16:17.932 UTC [5] LOG:  listening on IPv4 address "0.0.0.0", port 5432

2024-09-14 02:16:17.932 UTC [5] LOG:  listening on IPv6 address "::", port 5432

2024-09-14 02:16:17.937 UTC [5] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2024-09-14 02:16:17.944 UTC [28] LOG:  database system was interrupted; last known up at 2024-09-14 02:00:14 UTC

2024-09-14 02:16:17.990 UTC [28] LOG:  database system was not properly shut down; automatic recovery in progress

2024-09-14 02:16:17.993 UTC [28] LOG:  redo starts at 0/1418EAE0

2024-09-14 02:16:17.993 UTC [28] LOG:  invalid record length at 0/1418EB18: expected at least 24, got 0

2024-09-14 02:16:17.993 UTC [28] LOG:  redo done at 0/1418EAE0 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

project/694a1186-3c22-49fe-a25d-eacbfc6592d8 volume/ea87f0aa-352a-4443-84e4-cb208a52dc40 service/cadb89f1-9ce8-4d98-93bf-f53d2018a1eb

Solution:

i was using vpn

Jump to solution

19 Replies

Percy•2mo ago

Project ID: 694a1186-3c22-49fe-a25d-eacbfc6592d8,ea87f0aa-352a-4443-84e4-cb208a52dc40,cadb89f1-9ce8-4d98-93bf-f53d2018a1eb

Brody•2mo ago

what error? there are no errors there

Adel•2mo ago

updated

Brody•2mo ago

nothing there is an error

Adel•2mo ago

Brody•2mo ago

thats nothing to worry about

Adel•2mo ago

i can't connect to it via my app

Brody•2mo ago

please provide the error you get

Adel•2mo ago

Brody•2mo ago

please provide an actual error

Adel•2mo ago

database system was not properly shut down; automatic recovery in progress isn't an error?

Brody•2mo ago

it is not

Adel•2mo ago

okay thanks

Brody•2mo ago

i need the error your app is printing

Adel•2mo ago

if it's a log when database starts then the problem is my app not db thanks @Brody bro i can't connect it via node-postgresql error: Unable to connect to the database. Retrying (2)... {"context":"TypeOrmModule","ms":"+3s","stack":["Error: SASL: SCRAM-SERVER-FIRST-MESSAGE: client password must be a string\n at Object.continueSession it was working fine before rising its volume.....

Brody•2mo ago

you are likely using the postgres client incorrectly, please reference its docs for syntax

Adel•2mo ago

it's the same settings bro, i'm connecting string connection without issue in dbeaver and pgadmin. but not working with typeorm or node-pg problem sovled, thanks

Brody•2mo ago

what was the issue?

Solution

Adel•2mo ago

i was using vpn

Gaming

Programming

postgresql not crushing after increasing volume