[GH-ISSUE #1333] Postgresql Upgrade Connection Issues 1.9.0 #10620

Closed
opened 2026-05-06 14:18:59 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @ex-aequo-et-bono on GitHub (Aug 24, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1333

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 GitHub (Aug 24, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1333 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.
Author
Owner

@oschwartz10612 commented on GitHub (Aug 24, 2025):

Feels like the PG migration didn't go to well. Uugg sorry about this.
Taking a look now... Missing column it seems.

<!-- gh-comment-id:3218365906 --> @oschwartz10612 commented on GitHub (Aug 24, 2025): Feels like the PG migration didn't go to well. Uugg sorry about this. Taking a look now... Missing column it seems.
Author
Owner

@oschwartz10612 commented on GitHub (Aug 24, 2025):

Okay there are some missing cols in the PG migration that slipped
through apologies! Can you try adding this manually and running again? I
am rebuilding the container now but it wont run the migration for you
now that it is done unless you revert the db.

ALTER TABLE 'exitNodes' ADD 'online' integer DEFAULT false NOT NULL;
ALTER TABLE 'exitNodes' ADD 'lastPing' integer;
ALTER TABLE 'exitNodes' ADD 'type' text DEFAULT 'gerbil';

<!-- gh-comment-id:3218369219 --> @oschwartz10612 commented on GitHub (Aug 24, 2025): Okay there are some missing cols in the PG migration that slipped through apologies! Can you try adding this manually and running again? I am rebuilding the container now but it wont run the migration for you now that it is done unless you revert the db. ALTER TABLE 'exitNodes' ADD 'online' integer DEFAULT false NOT NULL; ALTER TABLE 'exitNodes' ADD 'lastPing' integer; ALTER TABLE 'exitNodes' ADD 'type' text DEFAULT 'gerbil';
Author
Owner

@ex-aequo-et-bono commented on GitHub (Aug 24, 2025):

Worked like a charm--thank you very much for the speedy help!

<!-- gh-comment-id:3218374540 --> @ex-aequo-et-bono commented on GitHub (Aug 24, 2025): Worked like a charm--thank you very much for the speedy help!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#10620