Error: P1001: Can't reach database server at
postgres.railway.internal:5432

Anonymous
TRIAL

a year ago

It was working fine past 2 weeks now when I opened it is not opening and throwing this error.
Getting this in deployed logs
2024-06-24 10:02:32.297 UTC [9] LOG: database system is ready to accept connections

2024-06-24 10:02:41.874 UTC [39] LOG: starting logical decoding for slot "prismapulse33254e6c"

2024-06-24 10:02:41.874 UTC [39] DETAIL: Streaming transactions committing after 0/1954B81, reading WAL from 0/1954B80.

2024-06-24 10:02:41.874 UTC [39] STATEMENT: STARTREPLICATION SLOT "prismapulse33254e6c" LOGICAL 0/0 (protoversion '1', publicationnames 'prismapulse_33254e6c')

2024-06-24 10:02:41.874 UTC [39] LOG: logical decoding found consistent point at 0/1954B80

2024-06-24 10:02:41.874 UTC [39] DETAIL: There are no running transactions.

2024-06-24 10:02:41.874 UTC [39] STATEMENT: STARTREPLICATION SLOT "prismapulse33254e6c" LOGICAL 0/0 (protoversion '1', publicationnames 'prismapulse_33254e6c')

0 Replies

Anonymous
TRIAL

a year ago

02bf7224-8c69-4953-b45b-39ebb8a39e9c


a year ago

red doesn't always mean error, please look at the content of the log to determine if it's an error and not the colour.

what is the deployment status of the database.


Error: P1001: Can't reach database server at `postgres.railway.internal:5432` - Railway Help Station