Error: Failed to frame message in DX NetOps NCM Service on SDC 25.4.6
search cancel

Error: Failed to frame message in DX NetOps NCM Service on SDC 25.4.6

book

Article ID: 436654

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

The NCM service fails to start after upgrading or performing a fresh installation of the SDC as a non-root user․​​​​​​​‍

 

ERROR MESSAGE: "io․grpc․StatusRuntimeException: INTERNAL: Failed to frame message"

 

SYMPTOMS:

  • NCM service is unavailable in Spectrum OCE

  • Continuous error messages populate the NCMSERV․OUT log

     

CONTEXT: Occurs on fresh installations and upgrades to SDC version 25․4․6

 

IMPACT: Prevents NCM component from functioning on the SDC

Environment

 

  • OS: RHEL 9․x, Rocky 9

  • Application: Secure Domain Connector (SDC) 25․4․6

  • Component: Network Configuration Manager (NCM)

 

Cause

The installer incorrectly bundles two conflicting versions of the Protocol Buffers library (protobuf-java-3․25․8․jar and protobuf-java-4․31․1․jar)․ This causes the Java classloader to crash the gRPC NCM service during initialization.

Resolution

Step 1․ STOP THE NCM SERVICE

Command: Stop the currently running NCM service

 

EXPECTED: Service halts completely

 

 

Step 2․ LOCATE GRPC JARS DIRECTORY

Path: /bin/grpc_jars/

 

EXPECTED: Directory contains multiple protobuf-java files

 

 

Step 3․ REMOVE CONFLICTING JAR FILE

Command: Move protobuf-java-3․25․8․jar completely out of the directory to a temporary location

 

EXPECTED: Only protobuf-java-4․31․1․jar remains in the directory

 

 

Step 4․ RESTART THE NCM SERVICE

Command: Restart the SDC and NCM service

 

EXPECTED: Service starts successfully without gRPC framing errors

 

 

VERIFY SUCCESS:

  • Check NCMSERV․OUT log for absence of framing errors

  • Verify NCM service shows as available in Spectrum OCE