{"record":{"id":"6285b61de0a6935b","repo":"influxdata/influxdb","slug":"heap-dump-failed-0","errorCode":null,"errorMessage":"heap dump failed: {0}","messagePattern":"heap dump failed: (.+?)","errorType":"http","errorClass":"Error","httpStatus":null,"severity":"warning","filePath":"influxdb3_server/src/http.rs","lineNumber":349,"sourceCode":"\n    #[error(\"must provide only one InfluxQl statement per query\")]\n    InfluxqlSingleStatement,\n\n    #[error(\"must specify a 'db' parameter, or provide the database in the InfluxQL query\")]\n    InfluxqlNoDatabase,\n\n    #[error(\n        \"provided a database in both the parameters ({param_db}) and \\\n        query string ({query_db}) that do not match, if providing a query \\\n        that specifies the database, you can omit the 'database' parameter \\\n        from your request\"\n    )]\n    InfluxqlDatabaseMismatch { param_db: String, query_db: String },\n\n    #[error(\"Operation with object store failed: {0}\")]\n    ObjectStore(#[from] object_store::Error),\n\n    #[error(\"heap dump failed: {0}\")]\n    HeapPprof(#[from] jemalloc_pprof_http::Error),\n\n    #[error(transparent)]\n    Catalog(#[from] CatalogError),\n\n    #[error(\"Python plugins not enabled on this server\")]\n    PythonPluginsNotEnabled,\n\n    #[error(\"Plugin error: {0}\")]\n    Plugin(#[from] influxdb3_processing_engine::plugins::PluginError),\n\n    #[error(\"Processing engine error: {0}\")]\n    ProcessingEngine(#[from] influxdb3_processing_engine::manager::ProcessingEngineError),\n\n    #[error(transparent)]\n    Influxdb3TypesHttp(#[from] influxdb3_types::http::Error),\n\n    #[error(\"Authorization error: {0}\")]","sourceCodeStart":331,"sourceCodeEnd":367,"githubUrl":"https://github.com/influxdata/influxdb/blob/06200ef96ba82c5f6727e5038a83af8e722c6875/influxdb3_server/src/http.rs#L331-L367","documentation":"Wraps jemalloc_pprof_http::Error raised when an on-demand heap profile dump fails. InfluxDB3 exposes a debug/ops endpoint that snapshots jemalloc heap profiles; failures in the profiling machinery (jemalloc not enabled, profiling not compiled in, dump failure) produce this error.","triggerScenarios":"Hitting the heap-profile/debug HTTP endpoint on a build without jemalloc profiling support compiled in, or when the pprof dump cannot be generated from the allocator.","commonSituations":"Requesting heap dumps on official binaries or container images built without the jemalloc-pprof feature; debugging memory growth on unsupported builds.","solutions":["Confirm the server binary was built with the jemalloc pprof feature enabled.","Use a build/image that includes profiling support (e.g. a debug or profiling-enabled image).","Read the inner jemalloc_pprof_http error for the specific allocator failure.","Fall back to other memory diagnostics (RSS metrics, /metrics endpoint) on unsupported builds."],"exampleFix":"// before\n// request heap dump on a default binary without profiling\ncurl 'http://localhost:8181/debug/heap'  # heap dump failed\n// after\n// run a profiling-enabled build\ncargo build --features jemalloc_replacing_malloc && curl 'http://localhost:8181/debug/heap'","handlingStrategy":"fallback","validationCode":"// only call the heap endpoint when profiling is known-enabled\nif (!buildHasJemallocPprof) return alternativeMemoryDiagnostics();","typeGuard":null,"tryCatchPattern":"try { const p = await fetch(`${host}/debug/heap`); } catch (e) { if (e.message.startsWith('heap dump failed')) return useMetricsFallback(); throw e; }","preventionTips":["Verify your build includes jemalloc pprof support before relying on heap dumps","Document which images are profiling-enabled","Maintain fallback diagnostics (RSS, /metrics) for unsupported builds"],"tags":["heap-dump","profiling","jemalloc","debug-endpoint"],"backgroundTag":"heap-dump-failed","analyzedSha":"06200ef96ba82c5f6727e5038a83af8e722c6875","analyzedAt":"2026-09-19T12:55:30.003Z","contentChangedAt":"2026-09-19T12:55:30.003Z","schemaVersion":2},"datasetVersion":"2026-09-23T08:17:48.524Z"}