lanford33 Posts - Answer Overflow

lanford33

Explore posts from servers

•Created by lanford33 on 11/15/2023 in #✋｜help

Cannot connect to new database after migration

project id: 6fbf03b2-6e85-491d-bda7-591922fe9dd7 The database's logs:

2023-11-15 16:09:18.136 UTC [7] LOG:  starting PostgreSQL 15.4 (Ubuntu 15.4-2.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit

2023-11-15 16:09:18.137 UTC [7] LOG:  listening on IPv4 address "0.0.0.0", port 5432

2023-11-15 16:09:18.137 UTC [7] LOG:  listening on IPv6 address "::", port 5432

2023-11-15 16:09:18.141 UTC [7] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2023-11-15 16:09:18.148 UTC [34] LOG:  database system was interrupted; last known up at 2023-11-15 16:05:16 UTC

2023-11-15 16:09:18.199 UTC [34] LOG:  database system was not properly shut down; automatic recovery in progress

2023-11-15 16:09:18.203 UTC [34] LOG:  redo starts at 0/13A10DD0

2023-11-15 16:09:18.203 UTC [34] LOG:  invalid record length at 0/13A10E08: wanted 24, got 0

2023-11-15 16:09:18.203 UTC [34] LOG:  redo done at 0/13A10DD0 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

2023-11-15 16:09:18.208 UTC [32] LOG:  checkpoint starting: end-of-recovery immediate wait

2023-11-15 16:09:18.222 UTC [32] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.006 s, sync=0.002 s, total=0.016 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB

2023-11-15 16:09:18.230 UTC [7] LOG:  database system is ready to accept connections

2023-11-15 16:09:18.231 UTC [37] LOG:  TimescaleDB background worker launcher connected to shared catalogs

2023-11-15 16:09:18.136 UTC [7] LOG:  starting PostgreSQL 15.4 (Ubuntu 15.4-2.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit

2023-11-15 16:09:18.137 UTC [7] LOG:  listening on IPv4 address "0.0.0.0", port 5432

2023-11-15 16:09:18.137 UTC [7] LOG:  listening on IPv6 address "::", port 5432

2023-11-15 16:09:18.141 UTC [7] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2023-11-15 16:09:18.148 UTC [34] LOG:  database system was interrupted; last known up at 2023-11-15 16:05:16 UTC

2023-11-15 16:09:18.199 UTC [34] LOG:  database system was not properly shut down; automatic recovery in progress

2023-11-15 16:09:18.203 UTC [34] LOG:  redo starts at 0/13A10DD0

2023-11-15 16:09:18.203 UTC [34] LOG:  invalid record length at 0/13A10E08: wanted 24, got 0

2023-11-15 16:09:18.203 UTC [34] LOG:  redo done at 0/13A10DD0 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

2023-11-15 16:09:18.208 UTC [32] LOG:  checkpoint starting: end-of-recovery immediate wait

2023-11-15 16:09:18.222 UTC [32] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.006 s, sync=0.002 s, total=0.016 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB

2023-11-15 16:09:18.230 UTC [7] LOG:  database system is ready to accept connections

2023-11-15 16:09:18.231 UTC [37] LOG:  TimescaleDB background worker launcher connected to shared catalogs

However, I cannot connect to it from my local mac or my railway app.

29 replies

RRailway

•Created by lanford33 on 7/12/2023 in #✋｜help

Error: P1001: Can't reach database server at xxxx, Please make sure your database server ...

I'm using PostgreSQL Basically, every time I deploy my application (a simple express app using Prisma), this error is triggered. Sometimes it takes two to three minutes to successfully connect, and other times it continues until the application crashes. I've already switched databases once, but the issue remains the same. It's incredibly frustrating. (I'm writing this post now because half an hour has passed, and I still haven't successfully deployed.) I have several applications deployed on Railway, but this is the first time I've encountered this problem. Previously, I had a Developer plan account, but now it has been changed to Hobby. I'm not sure if that is related to the issue. Here is my ServiceID: b5e0ccd6-5868-4f37-aefa-01fa0a8dda6b.

25 replies

Gaming

Programming