It crashed
vambe
PROOP

2 years ago

I need to reset the database

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

Solved

12 Replies

Hi, you deleted the service you linked to from your production environment, so we cannot review the deployment details you linked. Please share more context on the issue you are observing.


Status changed to Awaiting User Response Railway over 1 year ago


vambe
PROOP

2 years ago

Can yo connect quickly?


Status changed to Awaiting Railway Response Railway over 1 year ago


2 years ago

Please explain the issue you are experiencing clearly.


vambe
PROOP

2 years ago

2024-07-19 18:19:40.822 UTC [11] 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-07-19 18:19:40.822 UTC [11] LOG: listening on IPv4 address "0.0.0.0", port 5432

2024-07-19 18:19:40.822 UTC [11] LOG: listening on IPv6 address "::", port 5432

2024-07-19 18:19:40.838 UTC [11] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2024-07-19 18:19:40.845 UTC [34] LOG: database system was interrupted; last known up at 2024-07-19 17:06:30 UTC

2024-07-19 18:19:40.901 UTC [34] LOG: invalid resource manager ID in checkpoint record

2024-07-19 18:19:40.901 UTC [34] PANIC: could not locate a valid checkpoint record

2024-07-19 18:19:41.982 UTC [11] LOG: startup process (PID 34) was terminated by signal 6: Aborted

2024-07-19 18:19:41.982 UTC [11] LOG: aborting startup due to startup process failure

2024-07-19 18:19:41.983 UTC [11] LOG: database system is shut down

Certificate will not expire

PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-07-19 18:20:34.065 UTC [11] 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-07-19 18:20:34.065 UTC [11] LOG: listening on IPv4 address "0.0.0.0", port 5432

2024-07-19 18:20:34.065 UTC [11] LOG: listening on IPv6 address "::", port 5432

2024-07-19 18:20:34.070 UTC [11] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2024-07-19 18:20:34.078 UTC [34] LOG: database system was interrupted; last known up at 2024-07-19 17:06:30 UTC

2024-07-19 18:20:34.133 UTC [34] LOG: invalid resource manager ID in checkpoint record

2024-07-19 18:20:34.133 UTC [34] PANIC: could not locate a valid checkpoint record

2024-07-19 18:20:34.350 UTC [11] LOG: startup process (PID 34) was terminated by signal 6: Aborted

2024-07-19 18:20:34.350 UTC [11] LOG: aborting startup due to startup process failure

2024-07-19 18:20:34.352 UTC [11] LOG: database system is shut down


vambe
PROOP

2 years ago

Our server lost conection to the DB, and this logs started appearing in postgres


vambe
PROOP

2 years ago

We wanted to know if there is some way to reset the certificate, or something and when we redeploy it persists


vambe
PROOP

2 years ago

I need to do a pg dump as fast as posible to recover the data


vambe
PROOP

2 years ago

Or redeploy the service


vambe
PROOP

2 years ago

how I connect to a postgres disk?


vambe
PROOP

2 years ago

I need to recover this data

Attachments


vambe
PROOP

2 years ago

Plisss


Closing this as a duplicate of URGENT DATABASE IS NOT STARTING.


Status changed to Awaiting User Response Railway over 1 year ago


Status changed to Solved christian over 1 year ago


Loading...