blackfox1337 Comments - Answer Overflow

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-05-23 18:56:47.331 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-05-23 18:56:47.332 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-05-23 18:56:48.437 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit

2025-05-23 18:56:48.438 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432

2025-05-23 18:56:48.438 UTC [1] LOG:  listening on IPv6 address "::", port 5432

2025-05-23 18:56:48.440 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2025-05-23 18:56:48.446 UTC [28] LOG:  database system was interrupted; last known up at 2025-05-23 18:51:54 UTC

[2025-05-23T18:56:48Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/270143".

[2025-05-23T18:56:48Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/130020".

[2025-05-23T18:56:48Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/270143/segments/9b1ddac7-37c4-4ebd-a837-c6309f305ade".

[2025-05-23T18:56:49Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/130020/segments/686b2e4b-c83d-4047-9fc1-08072fe5628e".

2025-05-23 18:56:49.746 UTC [28] LOG:  database system was not properly shut down; automatic recovery in progress

2025-05-23 18:56:49.751 UTC [28] LOG:  redo starts at 6/DF0840C0

2025-05-23 18:56:50.247 UTC [28] LOG:  unexpected pageaddr 6/D24FC000 in log segment 0000000100000006000000E5, offset 5226496

2025-05-23 18:56:50.247 UTC [28] LOG:  redo done at 6/E54FBDB0 system usage: CPU: user: 0.15 s, system: 0.15 s, elapsed: 0.49 s

2025-05-23 18:56:52.093 UTC [1] LOG:  database system is ready to accept connections

2025-05-23 19:02:56.521 UTC [74] LOG:  could not send data to client: Broken pipe

2025-05-23 19:02:56.521 UTC [74] FATAL:  connection to client lost

2025-05-23 19:08:32.590 UTC [1] LOG:  server process (PID 97) was terminated by signal 13: Broken pipe

2025-05-23 19:08:32.590 UTC [1] LOG:  terminating any other active server processes

2025-05-23 19:08:34.340 UTC [1] LOG:  all server processes terminated; reinitializing

2025-05-23 19:08:37.454 UTC [99] LOG:  database system was interrupted; last known up at 2025-05-23 19:07:09 UTC

2025-05-23 19:10:07.523 UTC [99] LOG:  database system was not properly shut down; automatic recovery in progress

2025-05-23 19:10:07.531 UTC [99] LOG:  redo starts at 6/FEDFF340

Using SSD storage

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-05-23 18:56:47.331 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-05-23 18:56:47.332 GMT [1] LOG:  skipping missing configuration file "/var/lib/postgresql/data/postgresql.override.conf"

2025-05-23 18:56:48.437 UTC [1] LOG:  starting PostgreSQL 14.17 (Debian 14.17-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit

2025-05-23 18:56:48.438 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432

2025-05-23 18:56:48.438 UTC [1] LOG:  listening on IPv6 address "::", port 5432

2025-05-23 18:56:48.440 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2025-05-23 18:56:48.446 UTC [28] LOG:  database system was interrupted; last known up at 2025-05-23 18:51:54 UTC

[2025-05-23T18:56:48Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/270143".

[2025-05-23T18:56:48Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/130020".

[2025-05-23T18:56:48Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/270143/segments/9b1ddac7-37c4-4ebd-a837-c6309f305ade".

[2025-05-23T18:56:49Z INFO  service::utils::clean] Find directory "pg_vectors/indexes/130020/segments/686b2e4b-c83d-4047-9fc1-08072fe5628e".

2025-05-23 18:56:49.746 UTC [28] LOG:  database system was not properly shut down; automatic recovery in progress

2025-05-23 18:56:49.751 UTC [28] LOG:  redo starts at 6/DF0840C0

2025-05-23 18:56:50.247 UTC [28] LOG:  unexpected pageaddr 6/D24FC000 in log segment 0000000100000006000000E5, offset 5226496

2025-05-23 18:56:50.247 UTC [28] LOG:  redo done at 6/E54FBDB0 system usage: CPU: user: 0.15 s, system: 0.15 s, elapsed: 0.49 s

2025-05-23 18:56:52.093 UTC [1] LOG:  database system is ready to accept connections

2025-05-23 19:02:56.521 UTC [74] LOG:  could not send data to client: Broken pipe

2025-05-23 19:02:56.521 UTC [74] FATAL:  connection to client lost

2025-05-23 19:08:32.590 UTC [1] LOG:  server process (PID 97) was terminated by signal 13: Broken pipe

2025-05-23 19:08:32.590 UTC [1] LOG:  terminating any other active server processes

2025-05-23 19:08:34.340 UTC [1] LOG:  all server processes terminated; reinitializing

2025-05-23 19:08:37.454 UTC [99] LOG:  database system was interrupted; last known up at 2025-05-23 19:07:09 UTC

2025-05-23 19:10:07.523 UTC [99] LOG:  database system was not properly shut down; automatic recovery in progress

2025-05-23 19:10:07.531 UTC [99] LOG:  redo starts at 6/FEDFF340

23 replies

IImmich

•Created by blackfox1337 on 5/23/2025 in #help-desk-support

Issue upgrading to 1.133.0 from 1.132.2

23 replies

IImmich

•Created by blackfox1337 on 5/23/2025 in #help-desk-support

Issue upgrading to 1.133.0 from 1.132.2

23 replies

IImmich

•Created by blackfox1337 on 5/23/2025 in #help-desk-support

Issue upgrading to 1.133.0 from 1.132.2

server logs

Postgres notice: {

  severity_local: 'WARNING',

  severity: 'WARNING',

  code: '57P02',

  message: 'terminating connection because of crash of another server process',

  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',

  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',

  file: 'postgres.c',

  line: '2916',

  routine: 'quickdie'

}

Postgres notice: {

  severity_local: 'WARNING',

  severity: 'WARNING',

  code: '57P02',

  message: 'terminating connection because of crash of another server process',

  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',

  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',

  file: 'postgres.c',

  line: '2916',

  routine: 'quickdie'

}

Postgres notice: {

  severity_local: 'WARNING',

  severity: 'WARNING',

  code: '57P02',

  message: 'terminating connection because of crash of another server process',

  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',

  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',

  file: 'postgres.c',

  line: '2916',

  routine: 'quickdie'

}

Postgres notice: {

  severity_local: 'WARNING',

  severity: 'WARNING',

  code: '57P02',

  message: 'terminating connection because of crash of another server process',

  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',

  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',

  file: 'postgres.c',

  line: '2916',

  routine: 'quickdie'

}

Query failed : {

  durationMs: 309189.720595,

  error: Error: write CONNECTION_CLOSED immich_postgres:5432

      at Socket.closed (/usr/src/app/node_modules/postgres/cjs/src/connection.js:440:57)

      at Socket.emit (node:events:518:28)

      at TCP.<anonymous> (node:net:351:12) {

    code: 'CONNECTION_CLOSED',

    errno: 'CONNECTION_CLOSED',

    address: [ 'immich_postgres' ],

    port: [ 5432 ]

  },

  sql: 'SELECT pg_advisory_lock($1)',

  params: [ 200 ]

}

Query failed : {

  durationMs: 309014.87378399994,

  error: Error: write CONNECTION_CLOSED immich_postgres:5432

      at Socket.closed (/usr/src/app/node_modules/postgres/cjs/src/connection.js:440:57)

      at Socket.emit (node:events:518:28)

      at TCP.<anonymous> (node:net:351:12) {

    code: 'CONNECTION_CLOSED',

    errno: 'CONNECTION_CLOSED',

    address: [ 'immich_postgres' ],

    port: [ 5432 ]

  },

  sql: 'ALTER TABLE face_search ALTER COLUMN embedding SET DATA TYPE real[]',

Postgres notice: {

  severity_local: 'WARNING',

  severity: 'WARNING',

  code: '57P02',

  message: 'terminating connection because of crash of another server process',

  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',

  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',

  file: 'postgres.c',

  line: '2916',

  routine: 'quickdie'

}

Postgres notice: {

  severity_local: 'WARNING',

  severity: 'WARNING',

  code: '57P02',

  message: 'terminating connection because of crash of another server process',

  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',

  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',

  file: 'postgres.c',

  line: '2916',

  routine: 'quickdie'

}

Postgres notice: {

  severity_local: 'WARNING',

  severity: 'WARNING',

  code: '57P02',

  message: 'terminating connection because of crash of another server process',

  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',

  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',

  file: 'postgres.c',

  line: '2916',

  routine: 'quickdie'

}

Postgres notice: {

  severity_local: 'WARNING',

  severity: 'WARNING',

  code: '57P02',

  message: 'terminating connection because of crash of another server process',

  detail: 'The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.',

  hint: 'In a moment you should be able to reconnect to the database and repeat your command.',

  file: 'postgres.c',

  line: '2916',

  routine: 'quickdie'

}

Query failed : {

  durationMs: 309189.720595,

  error: Error: write CONNECTION_CLOSED immich_postgres:5432

      at Socket.closed (/usr/src/app/node_modules/postgres/cjs/src/connection.js:440:57)

      at Socket.emit (node:events:518:28)

      at TCP.<anonymous> (node:net:351:12) {

    code: 'CONNECTION_CLOSED',

    errno: 'CONNECTION_CLOSED',

    address: [ 'immich_postgres' ],

    port: [ 5432 ]

  },

  sql: 'SELECT pg_advisory_lock($1)',

  params: [ 200 ]

}

Query failed : {

  durationMs: 309014.87378399994,

  error: Error: write CONNECTION_CLOSED immich_postgres:5432

      at Socket.closed (/usr/src/app/node_modules/postgres/cjs/src/connection.js:440:57)

      at Socket.emit (node:events:518:28)

      at TCP.<anonymous> (node:net:351:12) {

    code: 'CONNECTION_CLOSED',

    errno: 'CONNECTION_CLOSED',

    address: [ 'immich_postgres' ],

    port: [ 5432 ]

  },

  sql: 'ALTER TABLE face_search ALTER COLUMN embedding SET DATA TYPE real[]',

23 replies

Gaming

Programming