After a server patching activity or server maintenance reboot, the Telemetry java process of the Univiewer Management Server(UVMS) fails to start automatically.
Additional information:
-The service remains in a stopped state.
-Manual attempts to start the service fail.
-Other processes start normally, but the Telemetry process remains missing.
Product: Univiewer Management Server version 7.x
Defect DE183500: A stale RUNNING_PID file remains in the Telemetry bin directory after an unplanned shutdown or reboot. The presence of this file prevents the Java process from initializing as it falsely indicates the process is already active.
This issue is identified as a product defect and is tracked under DE183500.
Subscribe to this article to be updated on the fix status. See .
To restore the Telemetry process manually:
-Shut down the UVMS services.
-Navigate to the Telemetry bin directory (e.g., /var/opt/AUTOMIC/univiewer_server/<node>_mgtserver/telemetry/bin).
-Delete the RUNNING_PID file.
-Start the UVMS services.