R
Railway7mo ago
rom

Not able to connect to PostgresDB after migration

Hello, we have 5 different apps with Postgres DB running on railway. We've started the migration of one of our app but we encounter an issue with the new DB. with this error : could not receive data from client: Connection reset by peer We currently connect our app to the Postgres Legacy so our services are not down, but it's important to be able to migrate everything safely. Thanks ProjectId: ca07cd9d-fb81-4dce-ad1b-161d8d544c3e
2 Replies
Percy
Percy7mo ago
Project ID: ca07cd9d-fb81-4dce-ad1b-161d8d544c3e
rom
rom7mo ago
Here is the full logs 2023-11-29 08:40:09.244 UTC [7] LOG: PostgreSQL Database directory appears to contain a database; Skipping initialization 2023-11-29 08:40:09.244 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-29 08:40:09.244 UTC [7] LOG: listening on IPv4 address "0.0.0.0", port 5432 2023-11-29 08:40:09.244 UTC [7] LOG: listening on IPv6 address "::", port 5432 2023-11-29 08:40:09.248 UTC [7] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2023-11-29 08:40:09.255 UTC [34] LOG: database system was interrupted; last known up at 2023-11-29 08:31:29 UTC 2023-11-29 08:40:09.295 UTC [34] LOG: database system was not properly shut down; automatic recovery in progress 2023-11-29 08:40:09.299 UTC [34] LOG: redo starts at 0/283F538 2023-11-29 08:40:09.299 UTC [34] LOG: invalid record length at 0/283F570: wanted 24, got 0 2023-11-29 08:40:09.299 UTC [34] LOG: redo done at 0/283F538 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2023-11-29 08:40:09.304 UTC [32] LOG: checkpoint starting: end-of-recovery immediate wait 2023-11-29 08:40:09.315 UTC [32] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.002 s, total=0.013 s; sync files=2, longest=0.002 s, average=0.001 s; distance=0 kB, estimate=0 kB 2023-11-29 08:40:09.323 UTC [7] LOG: database system is ready to accept connections 2023-11-29 08:40:09.328 UTC [37] LOG: TimescaleDB background worker launcher connected to shared catalogs 2023-11-29 08:44:27.082 UTC [47] LOG: could not receive data from client: Connection reset by peer Hello here, I saw the issue was marked in an other thread but quick question I got a Pro Plan and I can't see my role after verifying my account. What's the best way to get support on this issue?