2 years ago
container event container died
PostgreSQL Database directory appears to contain a database; Skipping initialization
2024-08-23 21:05:51.465 UTC [2] 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-08-23 21:05:51.466 UTC [2] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-08-23 21:05:51.466 UTC [2] LOG: listening on IPv6 address "::", port 5432
2024-08-23 21:05:51.471 UTC [2] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-08-23 21:05:51.479 UTC [25] LOG: database system was interrupted while in recovery at 2024-08-23 21:05:49 UTC
2024-08-23 21:05:51.479 UTC [25] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2024-08-23 21:05:51.539 UTC [25] LOG: database system was not properly shut down; automatic recovery in progress
2024-08-23 21:05:51.542 UTC [25] LOG: redo starts at 0/6707FC28
2024-08-23 21:05:51.543 UTC [25] FATAL: mismatching overwritten LSN 0/670C6B00 -> 0/670D1148
2024-08-23 21:05:51.543 UTC [25] CONTEXT: WAL redo at 0/670C8018 for XLOG/OVERWRITE_CONTRECORD: lsn 0/670C6B00; time 2024-08-22 17:26:31.275659+00
2024-08-23 21:05:51.546 UTC [2] LOG: startup process (PID 25) exited with exit code 1
2024-08-23 21:05:51.546 UTC [2] LOG: terminating any other active server processes
2024-08-23 21:05:51.547 UTC [2] LOG: shutting down due to startup process failure
2024-08-23 21:05:51.550 UTC [2] LOG: database system is shut down
container event container died
ⓘ Deployment information is only viewable by project members and Railway employees.
0 Replies