The user interface for the Edge Processor Control Plane appears to be failing within on-premises Splunk version 10.2 environments.

Applicability

Description

A new Splunk Enterprise server was configured with Edge Processor, and navigation to the Data Management page fails with an error.

Investigation

Navigating to Apps > Data Management displays errors. 



Below is the detailed error message: 




1] This issue was reported after a fresh start of Splunk Enterprise version 10.2 

2]The Edge Processor functioned properly on Splunk Enterprise version 10.0.1, so the issue appears to be specific to version 10.2.

3]The Edge Processor reports a successful connection to Postgres:

{"traceId":"cf610a9baa3ffe3","@timestamp":"2026-01-26T18:15:03.794Z","dbUser":"acc.dbuser","log.level":"INFO","id":"3e38c0da45ad32a","message":"USING_PROVIDED_CREDENTIALS","log.logger":"stevlog","parentId":"5bc1c99dcdcfbeb","dbUrl":"jdbc:postgresql://localhost:5432/acies_config_service","process.thread.name":"main"}
{"traceId":"cf610a9baa3ffe3","@timestamp":"2026-01-26T18:15:03.813Z","dbUser":"acc.dbuser","log.level":"INFO","id":"46ec885c8522823","message":"DB_CONN_CHECK_SUCCESS","log.logger":"stevlog","durationMs":"18","parentId":"5bc1c99dcdcfbeb","dbUrl":"jdbc:postgresql://localhost:5432/acies_config_service","startTimestamp":"2026-01-26T18:15:03.794492Z","process.thread.name":"main"}

Resolution

Based on the review of the non-working data edge processor, it was observed that Java tracing could not reach the REST endpoint called "orchestrator."

The Splunk instance is deployed on RHEL 8 with Splunk version 10.2, which has a known issue involving an incorrectly compiled SPL2 sidecar (data orchestrator). The logs show errors related to GLIBC_2.32, indicating a "minimum required version" problem. The Postgres sidecar is not tracing but displays a healthy status with no errors. This known issue is resolved in version 10.2.1, although the release date has not yet been announced.