candide Comments - Answer Overflow

candide

•Created by candide on 10/14/2024 in #✋｜help

NocoDB Update Failure: Deployment Failed During Network Process (Health Check)

I reached out to the NocoDB devs, and they helped me solve it: I just had to copy the nc_auth_jwt_secret value in the nc_store table of the Postgres database, paste it in the deployment's NC_AUTH_JWT_SECRET env value, then redeploy.

8 replies

RRailway

•Created by candide on 10/14/2024 in #✋｜help

NocoDB Update Failure: Deployment Failed During Network Process (Health Check)

Deploy Logs:

Failed to decrypt any source or integration. Please configure correct encryption key.
Error: Failed to decrypt any source or integration. Please configure correct encryption key.
at t.default [as handler] (/usr/src/app/docker/main.js:2:2333236)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NcUpgrader.upgrade (/usr/src/app/docker/main.js:2:2307440)
at async InstanceWrapper.useFactory [as metatype] (/usr/src/app/docker/main.js:2:1885383)
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

Failed to decrypt any source or integration. Please configure correct encryption key.
Error: Failed to decrypt any source or integration. Please configure correct encryption key.
at t.default [as handler] (/usr/src/app/docker/main.js:2:2333236)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NcUpgrader.upgrade (/usr/src/app/docker/main.js:2:2307440)
at async InstanceWrapper.useFactory [as metatype] (/usr/src/app/docker/main.js:2:1885383)
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

8 replies

RRailway

•Created by candide on 10/14/2024 in #✋｜help

NocoDB Update Failure: Deployment Failed During Network Process (Health Check)

Build Logs:

Attempt #1 failed with service unavailable. Continuing to retry for 4m59s
Attempt #2 failed with service unavailable. Continuing to retry for 4m58s
Attempt #3 failed with service unavailable. Continuing to retry for 4m56s
Attempt #4 failed with service unavailable. Continuing to retry for 4m52s
Attempt #5 failed with service unavailable. Continuing to retry for 4m43s
Attempt #6 failed with service unavailable. Continuing to retry for 4m27s
Attempt #7 failed with service unavailable. Continuing to retry for 3m57s
Attempt #8 failed with service unavailable. Continuing to retry for 3m27s
Attempt #9 failed with service unavailable. Continuing to retry for 2m57s
Attempt #10 failed with service unavailable. Continuing to retry for 2m27s
Attempt #11 failed with service unavailable. Continuing to retry for 1m57s
Attempt #12 failed with service unavailable. Continuing to retry for 1m27s
Attempt #13 failed with service unavailable. Continuing to retry for 57s
Attempt #14 failed with service unavailable. Continuing to retry for 27s
 
1/1 replicas never became healthy!
Healthcheck failed!

Attempt #1 failed with service unavailable. Continuing to retry for 4m59s
Attempt #2 failed with service unavailable. Continuing to retry for 4m58s
Attempt #3 failed with service unavailable. Continuing to retry for 4m56s
Attempt #4 failed with service unavailable. Continuing to retry for 4m52s
Attempt #5 failed with service unavailable. Continuing to retry for 4m43s
Attempt #6 failed with service unavailable. Continuing to retry for 4m27s
Attempt #7 failed with service unavailable. Continuing to retry for 3m57s
Attempt #8 failed with service unavailable. Continuing to retry for 3m27s
Attempt #9 failed with service unavailable. Continuing to retry for 2m57s
Attempt #10 failed with service unavailable. Continuing to retry for 2m27s
Attempt #11 failed with service unavailable. Continuing to retry for 1m57s
Attempt #12 failed with service unavailable. Continuing to retry for 1m27s
Attempt #13 failed with service unavailable. Continuing to retry for 57s
Attempt #14 failed with service unavailable. Continuing to retry for 27s
 
1/1 replicas never became healthy!
Healthcheck failed!

8 replies

RRailway

•Created by candide on 8/30/2024 in #✋｜help

Navidrome Deployment: Trouble with using Volumes, Error while scanning media

@Adam I tried moving /data and /music to the root of the volume using the File Browser, then re-mounted it to the Navidrome deployment and kept the same env files, but it still didn't work...

5 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

Good news: the issue has been resolved. I didn't need to run that other query after all, just needed to deploy the following image provided by a NocoDB dev, which skips transaction so the deployment works as expected: nocodb/nocodb-timely:0.204.0-pr-7425-20240113-1241 Then, once that deployed successfully, I just needed to switch back to nocodb:latest. Thank you again for your support, Brody! I've been dealing with this issue for months, and I'm sure the fresh deploy also made a difference, somehow. I'll probably refer to that guide in the future, and hopefully it helps someone else.

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

No problem! I'll do some more digging and troubleshooting with them, and report the solution here.

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

My question is: how do I find the schema name to replace and run this query?

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

I was then asked to do the following:

Please run the following query as well .... replace schema_name with your schema name used in connection. And you should connect to the database you are using as well.

SELECT
      f.attname AS cn,
      i.relname as key_name,
      ix.indnatts, ix.indkey, f.attnum as seq_in_index,
      pg_catalog.format_type(f.atttypid,f.atttypmod) AS type,
      f.attnotnull as rqd,
      p.contype as cst,
      p.conname as cstn,
      CASE
          WHEN i.oid<>0 THEN true
          ELSE false
      END AS is_index,
      CASE
          WHEN p.contype = 'p' THEN true
          ELSE false
      END AS primarykey,
      CASE
          WHEN p.contype = 'u' THEN 0
      WHEN p.contype = 'p' THEN 0
          ELSE 1
      END AS non_unique_original,
      CASE
          WHEN p.contype = 'p' THEN true
          ELSE false
      END AS primarykey,
      CASE
          WHEN p.contype = 'u' THEN 0
      WHEN p.contype = 'p' THEN 0
          ELSE 1
      END AS non_unique,
      CASE
          WHEN f.atthasdef = 't' THEN pg_get_expr(d.adbin, d.adrelid)
      END AS default  FROM pg_attribute f
      JOIN pg_class c ON c.oid = f.attrelid
      JOIN pg_type t ON t.oid = f.atttypid
      LEFT JOIN pg_attrdef d ON d.adrelid = c.oid AND d.adnum = f.attnum
      LEFT JOIN pg_namespace n ON n.oid = c.relnamespace
      LEFT JOIN pg_constraint p ON p.conrelid = c.oid AND f.attnum = ANY (p.conkey)
      LEFT JOIN pg_class AS g ON p.confrelid = g.oid
      LEFT JOIN pg_index AS ix ON f.attnum = ANY(ix.indkey) and c.oid = f.attrelid and c.oid = ix.indrelid
      LEFT JOIN pg_class AS i ON ix.indexrelid = i.oid
      WHERE
        c.relkind = 'r'::char
      AND n.nspname = '__schema_name__'
      and i.oid<>0
      AND f.attnum > 0
      ORDER BY i.relname, f.attnum;

SELECT
      f.attname AS cn,
      i.relname as key_name,
      ix.indnatts, ix.indkey, f.attnum as seq_in_index,
      pg_catalog.format_type(f.atttypid,f.atttypmod) AS type,
      f.attnotnull as rqd,
      p.contype as cst,
      p.conname as cstn,
      CASE
          WHEN i.oid<>0 THEN true
          ELSE false
      END AS is_index,
      CASE
          WHEN p.contype = 'p' THEN true
          ELSE false
      END AS primarykey,
      CASE
          WHEN p.contype = 'u' THEN 0
      WHEN p.contype = 'p' THEN 0
          ELSE 1
      END AS non_unique_original,
      CASE
          WHEN p.contype = 'p' THEN true
          ELSE false
      END AS primarykey,
      CASE
          WHEN p.contype = 'u' THEN 0
      WHEN p.contype = 'p' THEN 0
          ELSE 1
      END AS non_unique,
      CASE
          WHEN f.atthasdef = 't' THEN pg_get_expr(d.adbin, d.adrelid)
      END AS default  FROM pg_attribute f
      JOIN pg_class c ON c.oid = f.attrelid
      JOIN pg_type t ON t.oid = f.atttypid
      LEFT JOIN pg_attrdef d ON d.adrelid = c.oid AND d.adnum = f.attnum
      LEFT JOIN pg_namespace n ON n.oid = c.relnamespace
      LEFT JOIN pg_constraint p ON p.conrelid = c.oid AND f.attnum = ANY (p.conkey)
      LEFT JOIN pg_class AS g ON p.confrelid = g.oid
      LEFT JOIN pg_index AS ix ON f.attnum = ANY(ix.indkey) and c.oid = f.attrelid and c.oid = ix.indrelid
      LEFT JOIN pg_class AS i ON ix.indexrelid = i.oid
      WHERE
        c.relkind = 'r'::char
      AND n.nspname = '__schema_name__'
      and i.oid<>0
      AND f.attnum > 0
      ORDER BY i.relname, f.attnum;

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

So, update on this issue: I've been troubleshooting with NocoDB for the last little bit, and here's what was said so far: I was asked to run

select *
from pg_indexes

The NocoDB dev looked over the results and said, "Somehow index list query returns empty list even if there are index and which is causing this issue."

53 replies

RRailway

•Created by devnyxie on 11/7/2023 in #✋｜help

Postgres Query Tab - can I enable it back somehow?

Thank you!

12 replies

RRailway

•Created by devnyxie on 11/7/2023 in #✋｜help

Postgres Query Tab - can I enable it back somehow?

Found this thread because I, too, miss the simple Query tab. How does dbgate compare to pgAdmin? I'm having a hard time finding insight online.

12 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

Well, I really appreciate the guide and all the help! The updated dockerfile was definitely something I would've missed if it wasn't for your help, and I'm sure the guide will help others. I'm going to try flagging down a NocoDB dev to see if the data error can be fixed, and report back in case someone else has the same error.

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

Awesome, so far so good...

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

Okay, I just want to make sure I understand the following passage from your guide:

Copy the DATABASE_URL variable from the Postgres database in your old NocoDB project into the note. making sure denote that it is the old database's URL Copy the DATABASE_PRIVATE_URL variable from the Postgres database in your new NocoDB project into the note. making sure denote that it is the old database's URL

I wasn't sure if the last sentence was a typo, so I noted down:

OLD DATABASE_URL: A OLD DATABASE_PRIVATE_URL: B NEW DATABASE_URL: C NEW DATABASE_PRIVATE_URL: D

Am I correct to place the following values? :

PLUGIN_URL: A NEW_URL: D

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

Should I delete the Postgres Plugin Migration, or just edit the variables?

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

You're right. I used DATABASE_URL for both old and new. Let me try again

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

53 replies

RRailway

•Created by candide on 1/11/2024 in #✋｜help

NocoDB: deployment crash, migration failure, current transaction is aborted

Ouf, I see what you mean now by my deployment being very old... The dockerfile from Railway isn't even the same as the one I have in my repo... Do you think it would be enough to just edit my dockerfile to match it to the new one? If not, a ping would be perfect.

53 replies

Gaming

Programming