Errors deploying nocodb
[Nest] 11 - 12/01/2023, 3:56:20 PM ERROR [ExceptionHandler] KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Error: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
at NcConfig.create (/usr/src/app/docker/main.js:2:1811775)
at async InstanceWrapper.useFactory [as metatype] (/usr/src/app/docker/main.js:2:1286537)
at async Injector.instantiateClass (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:369:37)
at async callback (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:65:34)
at async Injector.resolveConstructorParams (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:144:24)
at async Injector.loadInstance (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:70:13)
at async Injector.loadProvider (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:97:9)
at async /usr/src/app/node_modules/@nestjs/core/injector/instance-loader.js:56:13
at async Promise.all (index 3)
at async InstanceLoader.createInstancesOfProviders (/usr/src/app/node_modules/@nestjs/core/injector/instance-loader.js:55:9)
(node:9) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
╔══════════════════════════════════════════════════════════════════════════════╗║ ║║ EXCEPTION OCCURED!! in PGClient @ createDatabaseIfNotExists ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ MESSAGE: ║║ getaddrinfo ENOTFOUND postgres.railway.internal ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ CODE: ║║ ENOTFOUND ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ STACK: ║║ Error: getaddrinfo ENOTFOUND postgres.railway.internal ║║ at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26) ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ ║║ ║╚═══════════════════════
[Nest] 11 - 12/01/2023, 3:56:20 PM ERROR [ExceptionHandler] KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Error: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
at NcConfig.create (/usr/src/app/docker/main.js:2:1811775)
at async InstanceWrapper.useFactory [as metatype] (/usr/src/app/docker/main.js:2:1286537)
at async Injector.instantiateClass (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:369:37)
at async callback (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:65:34)
at async Injector.resolveConstructorParams (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:144:24)
at async Injector.loadInstance (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:70:13)
at async Injector.loadProvider (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:97:9)
at async /usr/src/app/node_modules/@nestjs/core/injector/instance-loader.js:56:13
at async Promise.all (index 3)
at async InstanceLoader.createInstancesOfProviders (/usr/src/app/node_modules/@nestjs/core/injector/instance-loader.js:55:9)
(node:9) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
╔══════════════════════════════════════════════════════════════════════════════╗║ ║║ EXCEPTION OCCURED!! in PGClient @ createDatabaseIfNotExists ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ MESSAGE: ║║ getaddrinfo ENOTFOUND postgres.railway.internal ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ CODE: ║║ ENOTFOUND ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ STACK: ║║ Error: getaddrinfo ENOTFOUND postgres.railway.internal ║║ at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26) ║║ ║║ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ║║ - - - - - - - - - - - - - - - - - - - - - - ║║ ║║ ║╚═══════════════════════
5 Replies
Project ID:
719049ed-a2ab-4b3f-b3b8-3d9e66c32b42719049ed-a2ab-4b3f-b3b8-3d9e66c32b42
Postgres service crashed too
Was able to resolve by wiping empty Postgres volume.
PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-12-02 06:51:27.001 UTC [7] LOG: starting PostgreSQL 16.0 (Debian 16.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2023-12-02 06:51:27.001 UTC [7] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-12-02 06:51:27.001 UTC [7] LOG: listening on IPv6 address "::", port 5432
2023-12-02 06:51:27.007 UTC [7] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-12-02 06:51:27.013 UTC [30] LOG: database system was interrupted; last known up at 2023-12-01 15:54:18 UTC
2023-12-02 06:51:27.048 UTC [30] LOG: invalid resource manager ID in checkpoint record
2023-12-02 06:51:27.048 UTC [30] PANIC: could not locate a valid checkpoint record
2023-12-02 06:51:27.296 UTC [7] LOG: startup process (PID 30) was terminated by signal 6: Aborted
2023-12-02 06:51:27.297 UTC [7] LOG: aborting startup due to startup process failure
2023-12-02 06:51:27.299 UTC [7] LOG: database system is shut down
PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-12-02 06:51:27.001 UTC [7] LOG: starting PostgreSQL 16.0 (Debian 16.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2023-12-02 06:51:27.001 UTC [7] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-12-02 06:51:27.001 UTC [7] LOG: listening on IPv6 address "::", port 5432
2023-12-02 06:51:27.007 UTC [7] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-12-02 06:51:27.013 UTC [30] LOG: database system was interrupted; last known up at 2023-12-01 15:54:18 UTC
2023-12-02 06:51:27.048 UTC [30] LOG: invalid resource manager ID in checkpoint record
2023-12-02 06:51:27.048 UTC [30] PANIC: could not locate a valid checkpoint record
2023-12-02 06:51:27.296 UTC [7] LOG: startup process (PID 30) was terminated by signal 6: Aborted
2023-12-02 06:51:27.297 UTC [7] LOG: aborting startup due to startup process failure
2023-12-02 06:51:27.299 UTC [7] LOG: database system is shut down
are you able to connect to it now from nocodb?
Yup, was odd.
indeed