Operations index

Confirm First

Troubleshooting index.

A central, symptom-first index for ObjectDB, Message Broker, LogDB, and cross-product support details handoff. Use it to pick the right runbook before changing local state or broadening a support claim.

Index Snapshot

Entries
23
Categories
5
Products
4
Documentation status
Routed

Triage Flow

  1. 1
    Match SymptomUse the category and product before running a command or changing local state.
  2. 2
    Capture First FailureRecord the first status, reason code, script, route, and evidence owner.
  3. 3
    Open Product RunbookUse the linked runbook for exact commands, expected output, cleanup, and limits.
  4. 4
    Redact Before HandoffMinimize credentials, payloads, tenant data, object keys, traces, and topology details.

Startup And Health

Startup And Health troubleshooting entries
ProductSymptomFirst checkLikely causeNext actionSource scopeRunbook
ObjectDBHealth check cannot connect.Compare OBJECTDB_BIND_ADDRESS with OBJECTDB_ENDPOINT and check the service terminal.Service is not running, still compiling, or bound to another address.Start the service on an unprivileged loopback port and retry /health.documented source scopeObjectDB operator runbooks
ObjectDBStartup platform probe fails.Read service stderr and verify OBJECTDB_DATA_DIR.Data directory cannot be created, written, flushed, renamed, or inspected.Choose a writable local path and capture stderr plus capability context before retrying.documented source scopeObjectDB operator runbooks
Message BrokerBroker health reports storage not ready.Capture GET /health, selected node id, data directory, and storage status.Local storage path, startup flags, or recovery state needs review.Preserve health output and use the Message Broker startup runbook before changing local state.documented source scopeMessage Broker operator runbooks
LogDBHealth route cannot be reached.Confirm LOGDB_BIND_ADDRESS, service terminal state, and /health URL.Service is not running, still compiling, exited early, or bound to another address.Restart on a loopback bind and capture the first startup error before retrying.documented source scopeLogDB operator runbooks

Auth And Admission

Auth And Admission troubleshooting entries
ProductSymptomFirst checkLikely causeNext actionSource scopeRunbook
ObjectDBS3 route returns AccessDenied.Capture request path, headers used, operation header, and error XML.Local request is missing expected credential shape or the operation is outside the active profile.Retry only with scoped local credentials and link the S3 Core compatibility or limits row.documented source scopeObjectDB operator runbooks
Message BrokerProtected route returns 401 or 403.Confirm security.auth_mode in /health and the route/auth compatibility row.API key, mTLS source, or trusted-header setup is missing or mismatched.Retry with valid local credentials or the configured trusted upstream path.documented source scopeMessage Broker operator runbooks
Message BrokerPublish or consumer group returns quota_exceeded.Capture status 429, error body, tenant or stream scope, and quota config.Tenant publish or consumer-group quota rejected the request.Reduce request shape or adjust reviewed local quota config; do not classify expected rejection as an outage.documented source scopeMessage Broker operator runbooks
LogDBIngest or query returns missing_tenant.Capture headers and route without payload contents.x-logdb-tenant was omitted or empty.Send the expected tenant header for local checks and keep broader tenant wording in security review.documented source scopeLogDB operator runbooks
LogDBIngest returns invalid_credentials or tenant_mismatch.Compare bearer token, tenant header, and OTLP resource tenant claim.Token does not match local policy or resource tenant differs from authenticated tenant.Align local credentials and tenant attributes; preserve the rejected body shape for security review.documented source scopeLogDB operator runbooks

Data Visibility And State

Data Visibility And State troubleshooting entries
ProductSymptomFirst checkLikely causeNext actionSource scopeRunbook
ObjectDBNoSuchBucket or NoSuchKey.Confirm bucket/key values and list current objects.Bucket or key was not created in the current data directory.Create the bucket/object again or point at the intended data directory.documented source scopeObjectDB operator runbooks
ObjectDBBucketNotEmpty during cleanup.Run ListObjectsV2 with the smoke prefix.Visible current objects remain in the bucket.Delete current smoke objects before deleting the bucket; avoid shared data cleanup.documented source scopeObjectDB operator runbooks
Message BrokerReplay returns no records.Check stream name, start offset, max records, consumer group, and publish result.Stream was not created, endpoint points at another node, or offset window is empty.Recreate the scoped smoke stream or query the exact offset produced by publish.documented source scopeMessage Broker operator runbooks
Message BrokerQueue delivery state cannot be stored.Capture route, delivery id, subscription id, and error body.Queue persistence path or storage admission rejected the mutation.Stop mutating the delivery and route limits and compatibility guidance to support review.documented source scopeMessage Broker operator runbooks
LogDBQuery returns zero matches.Re-run ingest, re-extract record ID, and check dataset.Dataset, record ID, trace ID, time filter, or data directory differs.Query the exact dataset and identifier produced by the smoke ingest.documented source scopeLogDB operator runbooks

Limits And Unsupported Behavior

Limits And Unsupported Behavior troubleshooting entries
ProductSymptomFirst checkLikely causeNext actionSource scopeRunbook
ObjectDBUnsupported S3 request returns NotImplemented.Capture status, x-objectdb-s3-operation, error code, path, query string, and request ID.Request is outside the active s3-core-v1 profile.Use a supported S3 Core route or record an unsupported-behavior follow-up.documented source scopeObjectDB operator runbooks
Message Broker/metrics returns 404 metrics_disabled.Check startup flags for --metrics-exposure http.Broker was not started with HTTP metrics exposure.Restart local broker with HTTP metrics exposure only if metrics are needed for the check.documented source scopeMessage Broker operator runbooks
Message BrokerReplication worker route returns replication_not_configured.Capture binding source, route body, stream, source site, target site, and timestamp.Replication bindings are not configured for the local run.Treat as configuration state; do not present it as a failed replication outcome.documented source scopeMessage Broker operator runbooks
LogDBMetrics or profiles are sent to LogDB.Check route and content against the compatibility matrix.Metrics and profiles are outside the documented LogDB route surface.Use logs/traces routes or track metrics/profile need as future compatibility work.documented source scopeLogDB operator runbooks
LogDBS3 query read fails.Confirm LOGDB_QUERY_STORE=s3 and redacted LOGDB_QUERY_S3_* values.S3 query-read config, region, bucket, prefix, or credentials failed.Treat as query-read configuration evidence only; do not infer ingest publication behavior.documented source scopeLogDB operator runbooks

support details And Handoff

support details And Handoff troubleshooting entries
ProductSymptomFirst checkLikely causeNext actionSource scopeRunbook
ObjectDBSupport details include sensitive object data.Inspect S3 response headers, XML errors, object key, payload sample, and data-directory context.Review capture included payload contents or sensitive object names.Minimize to status, operation header, request ID, and known-limits link before sharing.documented source scopeObjectDB operator runbooks
Message BrokerDiagnostics bundle includes payloads.Confirm mq diagnostics collect was run without --include-payloads.Payload inclusion was requested or a bundle shape drifted.Regenerate a payload-free bundle and route bundle contents through support and privacy review.documented source scopeMessage Broker operator runbooks
LogDBSupport package contains raw telemetry.Inspect query, OTLP, segment, and WAL evidence before sharing.Raw payloads, trace/span IDs, dataset names, or record IDs were captured without minimization.Replace with shape-only query evidence, counts, indexes, and redacted IDs when needed.documented source scopeLogDB operator runbooks
Cross-productClaim-sensitive wording appears in a troubleshooting note.Run docs claim lint and inspect nearby limits or evidence.Troubleshooting text strengthened support, availability, security, performance, scale, or customer-commitment wording.Rewrite to observed behavior and route through documented source scope before publishing.documented source scopeObservability and audit guide

Product Runbook Links

Troubleshooting sources and escalation routes
ProductTroubleshooting sourceRunbook routeLimits route
ObjectDBdocs/operations/documented source scope-objectdb-operator-runbooks.mdObjectDB operator runbooksObjectDB limits
Message Brokerdocs/operations/documented source scope-message-broker-operator-runbooks.mdMessage Broker operator runbooksMessage Broker limits
LogDBdocs/operations/documented source scope-logdb-operator-runbooks.mdLogDB operator runbooksLogDB limits
Cross-productdocs/operations/documented source scope-observability-audit-guide.mdObservability and audit guideErrors and limits catalog

Troubleshooting Boundaries

Start With status notes

Capture the first failing status, reason code, route, script, and runtime context before remediation changes the signal.

Unsupported Is Not Outage

Known unsupported behavior stays a limits entry unless a documented supported route or workflow is also failing.

Use Product Owners

The central index routes symptoms; product runbooks own exact commands, cleanup, escalation, and product support boundaries.

Source scope

Source scope map
Index areaSource scopeStatus
Startup, health, auth, state, limits, and status-note rowsdocumented source scopeSource-scoped
ObjectDB troubleshooting entriesdocumented source scope, and documented source scopeSource-scoped
Message Broker troubleshooting entriesdocumented source scope, and documented source scopeSource-scoped
LogDB troubleshooting entriesdocumented source scope, and documented source scopeSource-scoped
Sensitive troubleshooting and support handoff guidancedocumented source scope, and documented source scopeSource-scoped

Limits

  • This index points to first checks and next actions. Product runbooks own exact commands, expected output, cleanup, remediation, escalation, and review requirements.
  • Entries should not be used to claim support coverage, incident response timing, data retention, security posture, privacy approval, availability, performance, scale, production deployment readiness, or customer commitments.
  • Unsupported behavior should stay separate from incidents unless a documented supported path is also failing.
  • Support details must be minimized and redacted before sharing outside the approved support channel.

Safe Next Steps