search

OpenHistoricalMap / issues

File your issues here, regardless of repo until we get all our repos squared away; we don't want to miss anything.
Creative Commons Zero v1.0 Universal
17 stars 1 forks source link

Postgres 14 - Staging, error #765

Closed Rub21 closed 3 weeks ago

Rub21 commented 1 month ago

I have been trying to upload a considerable amount of data to staging, but seems some issues in the DB. i am working on solving it.

k logs staging-db-0 --previous

PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-04-23 03:27:58.300 UTC [1] LOG:  starting PostgreSQL 14.11 (Debian 14.11-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-04-23 03:27:58.300 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-04-23 03:27:58.300 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2024-04-23 03:27:58.305 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-04-23 03:27:58.352 UTC [27] LOG:  database system was interrupted; last known up at 2024-04-23 02:16:30 UTC
2024-04-23 03:27:58.371 UTC [27] LOG:  database system was not properly shut down; automatic recovery in progress
2024-04-23 03:27:58.374 UTC [27] LOG:  redo starts at 10/C5629660
2024-04-23 03:27:58.375 UTC [27] LOG:  invalid record length at 10/C5629818: wanted 24, got 0
2024-04-23 03:27:58.375 UTC [27] LOG:  redo done at 10/C56297D8 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-04-23 03:27:58.393 UTC [1] LOG:  database system is ready to accept connections
2024-04-23 03:33:41.439 UTC [46] LOG:  could not send data to client: Connection reset by peer
2024-04-23 03:33:41.439 UTC [46] STATEMENT:  SELECT e.node_id AS id, e.version, e.timestamp, e.visible, u.data_public, u.id AS user_id, u.display_name, e.changeset_id, e.latitude, e.longitude FROM nodes e INNER JOIN tmp_nodes t ON e.node_id = t.node_id AND e.version = t.version INNER JOIN changesets c ON e.changeset_id = c.id INNER JOIN users u ON c.user_id = u.id
2024-04-23 03:33:41.439 UTC [46] FATAL:  connection to client lost
2024-04-23 03:33:41.439 UTC [46] STATEMENT:  SELECT e.node_id AS id, e.version, e.timestamp, e.visible, u.data_public, u.id AS user_id, u.display_name, e.changeset_id, e.latitude, e.longitude FROM nodes e INNER JOIN tmp_nodes t ON e.node_id = t.node_id AND e.version = t.version INNER JOIN changesets c ON e.changeset_id = c.id INNER JOIN users u ON c.user_id = u.id
2024-04-25 15:49:08.117 UTC [1] LOG:  received fast shutdown request
2024-04-25 15:49:08.212 UTC [1] LOG:  aborting any active transactions
2024-04-25 15:49:08.280 UTC [815] FATAL:  terminating connection due to administrator command
2024-04-25 15:49:08.280 UTC [815] STATEMENT:  CREATE TEMPORARY TABLE tmp_nodes ON COMMIT DROP AS SELECT node_id, version FROM nodes WHERE (((xid_to_int4(xmin) >= $1 AND xid_to_int4(xmin) <= $2))) AND redaction_id IS NULL
2024-04-25 15:49:08.509 UTC [12305] FATAL:  the database system is shutting down
2024-04-25 15:49:08.772 UTC [1] LOG:  background worker "logical replication launcher" (PID 33) exited with exit code 1
2024-04-25 15:49:08.817 UTC [12312] FATAL:  the database system is shutting down
2024-04-25 15:49:09.619 UTC [28] LOG:  shutting down
2024-04-25 15:49:09.849 UTC [1] LOG:  database system is shut down

cc. @batpad @danrademacher

Rub21 commented 3 weeks ago

This issues has been fixed!!