dohertj2/lmxopcua
1
0
Fork 0
Code Issues 43 Pull Requests Actions Packages Projects Releases Wiki Activity

QuestDB: silence the libgssapi_krb5 boot warning (Npgsql GSS probe) #758

New Issue
Open
opened 2026-11-06 15:27:10 -05:00 by dohertj2 · 0 comments
dohertj2 commented 2026-11-06 15:27:10 -05:00
Owner
Copy Link
Copy Source

The QuestDB live gate saw Cannot load library libgssapi_krb5.so.2 once per central boot. It did not appear on site nodes, which have no Npgsql client. This is most likely Npgsql's default GSS-encryption probe, which falls back cleanly, so it is cosmetic. It is still a misleading error-looking line at boot.

Work: confirm the line comes from Npgsql. If it does, set GSS Encryption Mode=Disable in the QuestDB (and Postgres, if it applies) connection builder, or document the line. Nothing in src/ or docker-dev/ sets this today. Verify it is still emitted.

Source: docs/plans/2026-10-10-questdb-historian-live-gate.md §Gate findings item 2. (Finding 1 there is #672, closed.)

The QuestDB live gate saw `Cannot load library libgssapi_krb5.so.2` once per central boot. It did not appear on site nodes, which have no Npgsql client. This is most likely Npgsql's default GSS-encryption probe, which falls back cleanly, so it is cosmetic. It is still a misleading error-looking line at boot. Work: confirm the line comes from Npgsql. If it does, set `GSS Encryption Mode=Disable` in the QuestDB (and Postgres, if it applies) connection builder, or document the line. Nothing in `src/` or `docker-dev/` sets this today. Verify it is still emitted. Source: docs/plans/2026-10-10-questdb-historian-live-gate.md §Gate findings item 2. (Finding 1 there is #672, closed.)
dohertj2 added the type:debtpriority:p3migrated labels 2026-11-06 15:27:10 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto-managed
queue management
 blocked
Blocked by dependency or external hold
 cross-driver
queue management
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 driver/abcip
queue management
 driver/ablegacy
queue management
 driver/focas
queue management
 driver/mqtt
MQTT / Sparkplug B broker-subscribe driver
 driver/opcuaclient
queue management
 driver/s7
queue management
 driver/twincat
queue management
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 phase/1
queue management
 phase/2
queue management
 phase/3
queue management
 phase/4
queue management
 phase/5
queue management
 phase/6
queue management
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 queue/blocked
queue management
 queue/done
queue management
 queue/failed
queue management
 queue/in-progress
queue management
 queue/queued
queue management
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label migrated priority:p3 type:debt
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#758
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?