SRM-RIB Service Fails to Start After Linux Patching or Java Upgrade

Products

• Network Observability
• Spectrum

Issue/Introduction

The SRM-RIB (NetOps Report Manager) service fails to start or stops immediately after Linux OS patching or a Java upgrade on the server․

In the shell we see:

Oct 01 08:39:38 xxxxx systemd[1]: Starting NetOps Report Manager Service...
Oct 01 08:39:38 xxxxx srm-rib.sh[892274]: /opt/SRM/srm-rib/bin/srm-rib.sh: line 459: /usr/lib/jvm/java-17-openjdk-17.0.15.0.6-2.el8.x86_64/b>
Oct 01 08:39:38 xxxxx srm-rib.sh[892248]: Starting Jetty:
Oct 01 08:39:38 xxxxx srm-rib.sh[892276]: /opt/SRM/srm-rib/bin/srm-rib.sh: line 524: /usr/lib/jvm/java-17-openjdk-17.0.15.0.6-2.el8.x86_64/b>
Oct 01 08:39:38 xxxxx srm-rib.sh[892248]: ok Wed Oct  1 08:39:38 EDT 2025
Oct 01 08:39:38 xxxxx srm-rib.sh[892307]: /opt/SRM/srm-rib/bin/srm-rib.sh: line 459: /usr/lib/jvm/java-17-openjdk-17.0.15.0.6-2.el8.x86_64/b>
Oct 01 08:39:38 xxxxx srm-rib.sh[892280]: Stopping Jetty: OK
Oct 01 08:39:38 xxxxx systemd[1]: srm-rib.service: Succeeded.
Oct 01 08:39:38 xxxxx systemd[1]: Started NetOps Report Manager Service.

SYMPTOMS:

• Service status shows "Active: inactive (dead)" shortly after starting

• Log entries indicate "No such file or directory" for the Java binary

• systemctl status srm-rib may initially report "Succeeded" but the process dies

Environment

• Dx NetOps Spectrum 24.3, 25.4
  
  
• Java OpenJDK 17

Cause

The JRE on the system was upgraded and as a result the java path pointed to in srm-rib-jetty.conf broke.

Resolution

ROOT CAUSE: The srm-rib-jetty.conf file uses a hardcoded path to the Java executable that includes the specific minor version number․ When RHEL patching
   updates the java-17-openjdk package, the directory name on the filesystem changes, breaking the path reference

 

 

STEPS:

1. VERIFY JAVA PATH

   Check the JAVA_EXECUTABLE_PATH in the current configuration․

   Command: grep -i JAVA_EXECUTABLE_PATH /spectrum/SRM/srm-rib/conf/srm-rib-jetty.conf

   Verify if this path exists on the disk: ls -la [path_from_command]

   EXPECTED: The command returns "No such file or directory"․
   
   

2. LOCATE NEW JAVA BINARY

   Find the correct path for the currently installed Java version․

   Command: ls -d /usr/lib/jvm/java-17-openjdk-*/bin/java

   NOTE: Note the full path returned (e.g., /usr/lib/jvm/java-17-openjdk-17.0.17.0.10-1.el8.x86_64/bin/java)․
   
   

3. BACKUP CONFIGURATION

   Create a backup of the Jetty configuration file before editing․

   Command: cp -p /spectrum/SRM/srm-rib/conf/srm-rib-jetty.conf /spectrum/SRM/srm-rib/conf/srm-rib-jetty.conf.backup



4. UPDATE CONFIGURATION

   Edit the configuration file to point to the new Java path․

   Command: vim /spectrum/SRM/srm-rib/conf/srm-rib-jetty.conf

   Action: Update the JAVA_EXECUTABLE_PATH variable with the new path found in Step 2․

   Example: JAVA_EXECUTABLE_PATH=/usr/lib/jvm/java-17-openjdk-17.0.17.0.10-1.el8.x86_64/bin/java
   
   

5. RESTART SERVICE

   Stop and restart the SRM-RIB service to apply changes․

   Commands:
       systemctl stop srm-rib
    systemctl start srm-rib
   
   

VERIFY SUCCESS:

• Check the service status: systemctl status srm-rib

• EXPECTED: Status shows "Active: active (running)"

• Verify logs show successful startup without Java path error