Postgresql Upgrade Connection Issues 1.9.0 #1026

Closed
opened 2026-04-05 18:07:37 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @ex-aequo-et-bono on 8/24/2025

Hello,

I run two deployments of Pangolin, one default and one postgres. The upgrade to 1.9.0 for the "regular" deployment was fine, but my postgres instance is giving me some issues.

When starting the stack, I get the following error on the compose up -d command:

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to create new parent process: namespace path: lstat /proc/38571/ns/net: no such file or directory: unknown

And my logs for postgres show a mismatch issue:

postgres | 2025-08-24 16:26:35.430 EDT [636] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE pangolin_db REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
postgres | 2025-08-24 16:26:37.956 EDT [585] ERROR: column "online" does not exist at character 113
postgres | 2025-08-24 16:26:37.956 EDT [585] STATEMENT: select "exitNodeId", "name", "address", "endpoint", "publicKey", "listenPort", "reachableAt", "maxConnections", "online", "lastPing", "type" from "exitNodes" where "exitNodes"."publicKey" = $1

My pangolin container similarly is having issues connecting to the db:

pangolin | 2025-08-24T20:28:38.744Z [error]: Failed query: select "exitNodeId", "name", "address", "endpoint", "publicKey", "listenPort", "reachableAt", "maxConnections", "online", "lastPing", "type" from "exitNodes" where "exitNodes"."publicKey" = $1
pangolin | params: qp4j7NhgB3cq6Z/7H9Gy8mQeducgH5dnE8mayXrP6yg=
pangolin | Stack: Error: Failed query: select "exitNodeId", "name", "address", "endpoint", "publicKey", "listenPort", "reachableAt", "maxConnections", "online", "lastPing", "type" from "exitNodes" where "exitNodes"."publicKey" = $1
pangolin | params: qp4j7NhgB3cq6Z/7H9Gy8mQeducgH5dnE8mayXrP6yg=
pangolin | at NodePgPreparedQuery.queryWithCache (file:///app/node_modules/drizzle-orm/pg-core/session.js:41:15)
pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
pangolin | at async file:///app/node_modules/drizzle-orm/node-postgres/session.js:117:22
pangolin | at async Lw (file:///app/dist/server.mjs:32:105074) {"query":"select \"exitNodeId\", \"name\", \"address\", \"endpoint\", \"publicKey\", \"listenPort\", \"reachableAt\", \"maxConnections\", \"online\", \"lastPing\", \"type\" from \"exitNodes\" where \"exitNodes\".\"publicKey\" = $1","params":["qp4j7NhgB3cq6Z/7H9Gy8mQeducgH5dnE8mayXrP6yg="],"cause":{"length":107,"name":"error","severity":"ERROR","code":"42703","position":"113","file":"parse_relation.c","line":"3716","routine":"errorMissingColumn"}}

Grateful for any thoughts.

*Originally created by @ex-aequo-et-bono on 8/24/2025* Hello, I run two deployments of Pangolin, one default and one postgres. The upgrade to 1.9.0 for the "regular" deployment was fine, but my postgres instance is giving me some issues. When starting the stack, I get the following error on the compose up -d command: `Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to create new parent process: namespace path: lstat /proc/38571/ns/net: no such file or directory: unknown` And my logs for postgres show a mismatch issue: `postgres | 2025-08-24 16:26:35.430 EDT [636] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE pangolin_db REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.` `postgres | 2025-08-24 16:26:37.956 EDT [585] ERROR: column "online" does not exist at character 113` `postgres | 2025-08-24 16:26:37.956 EDT [585] STATEMENT: select "exitNodeId", "name", "address", "endpoint", "publicKey", "listenPort", "reachableAt", "maxConnections", "online", "lastPing", "type" from "exitNodes" where "exitNodes"."publicKey" = $1` My pangolin container similarly is having issues connecting to the db: `pangolin | 2025-08-24T20:28:38.744Z [error]: Failed query: select "exitNodeId", "name", "address", "endpoint", "publicKey", "listenPort", "reachableAt", "maxConnections", "online", "lastPing", "type" from "exitNodes" where "exitNodes"."publicKey" = $1` `pangolin | params: qp4j7NhgB3cq6Z/7H9Gy8mQeducgH5dnE8mayXrP6yg=` `pangolin | Stack: Error: Failed query: select "exitNodeId", "name", "address", "endpoint", "publicKey", "listenPort", "reachableAt", "maxConnections", "online", "lastPing", "type" from "exitNodes" where "exitNodes"."publicKey" = $1` `pangolin | params: qp4j7NhgB3cq6Z/7H9Gy8mQeducgH5dnE8mayXrP6yg=` `pangolin | at NodePgPreparedQuery.queryWithCache (file:///app/node_modules/drizzle-orm/pg-core/session.js:41:15)` `pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:105:5)` `pangolin | at async file:///app/node_modules/drizzle-orm/node-postgres/session.js:117:22` `pangolin | at async Lw (file:///app/dist/server.mjs:32:105074) {"query":"select \"exitNodeId\", \"name\", \"address\", \"endpoint\", \"publicKey\", \"listenPort\", \"reachableAt\", \"maxConnections\", \"online\", \"lastPing\", \"type\" from \"exitNodes\" where \"exitNodes\".\"publicKey\" = $1","params":["qp4j7NhgB3cq6Z/7H9Gy8mQeducgH5dnE8mayXrP6yg="],"cause":{"length":107,"name":"error","severity":"ERROR","code":"42703","position":"113","file":"parse_relation.c","line":"3716","routine":"errorMissingColumn"}}` Grateful for any thoughts.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1026