influxdata/influxdb · error · Error

Python plugins not enabled on this server

Error message

Python plugins not enabled on this server

What it means

InfluxDB 3's HTTP server returns this error when a request targets the Python plugin / processing-engine endpoints but the server binary was built or started without Python plugin support. It is the `PythonPluginsNotEnabled` variant of `influxdb3_server::http::Error`. The feature is gated at startup (typically a compile feature or launch flag), so any plugin-related API call fails fast with this message instead of reaching the plugin runtime.

Solutions

1. Restart the server with Python plugins enabled: use an image/binary built with the `python` feature and pass `--plugin-dir` (or the equivalent startup flag).
2. Verify with `influxdb3 --help` / server startup logs that the processing engine is available in your build.
3. If the request was sent by mistake, remove or redirect the plugin configuration/trigger calls to a node that supports Python plugins.
4. Pin your client/deployment so plugin endpoints are only called against Python-enabled instances.

Example fix

// before: server started as
// ./influxdb3 serve ...
// after
// ./influxdb3 serve --plugin-dir /var/lib/influxdb3/plugins ...  (Python-enabled build)

// Check server capabilities before calling plugin endpoints
const health = await fetch(`${base}/health`).then(r => r.json());
if (!health.plugins?.python_enabled) {
  throw new Error("Server has no Python plugin support; skip plugin setup");
}

// Rust client
match resp {
    Err(e) if e.to_string().contains("Python plugins not enabled") => {
        warn!("processing engine disabled on this server; skipping plugin setup");
    }
    other => other?,
}

When it happens

Trigger: Calling POST /api/v3/configure/processing_engine_trigger (or write-triggered plugin execution endpoints) against a server started without Python plugin support (e.g. the Docker image or binary compiled without the `python` feature, or `--plugin-dir` / Python support not enabled).

Common situations: Using a slim Docker image or OS package built without Python; upgrading a server and forgetting to enable the processing-engine flag; writing client code against a cluster where only some nodes have Python enabled; running tests with a feature-stripped binary.

Related errors

• Node not configured with plugin directory
• Plugin error
• Authentication error
• Authorization error
• authorization failure

AI-assisted analysis of influxdata/influxdb@06200ef96b (2026-09-19). Data as JSON: /api/errors/ad68d822e5eba6f3. Report an issue: GitHub.

Appendix: source

Thrown at influxdb3_server/src/http.rs:355

    #[error(
        "provided a database in both the parameters ({param_db}) and \
        query string ({query_db}) that do not match, if providing a query \
        that specifies the database, you can omit the 'database' parameter \
        from your request"
    )]
    InfluxqlDatabaseMismatch { param_db: String, query_db: String },

    #[error("Operation with object store failed: {0}")]
    ObjectStore(#[from] object_store::Error),

    #[error("heap dump failed: {0}")]
    HeapPprof(#[from] jemalloc_pprof_http::Error),

    #[error(transparent)]
    Catalog(#[from] CatalogError),

    #[error("Python plugins not enabled on this server")]
    PythonPluginsNotEnabled,

    #[error("Plugin error: {0}")]
    Plugin(#[from] influxdb3_processing_engine::plugins::PluginError),

    #[error("Processing engine error: {0}")]
    ProcessingEngine(#[from] influxdb3_processing_engine::manager::ProcessingEngineError),

    #[error(transparent)]
    Influxdb3TypesHttp(#[from] influxdb3_types::http::Error),

    #[error("Authorization error: {0}")]
    ResourceAuthorization(#[from] ResourceAuthorizationError),

    #[error("Authentication error: {0}")]
    Authentication(#[from] AuthenticatorError),

    #[error("The following Database does not exist: {0}")]

View on GitHub (pinned to 06200ef96b)