Diagnostics#

Use this page to check VSR NIM readiness and to investigate common compressed-video workflow issues.

Check HTTP Readiness#

curl -sf http://localhost:8000/v1/health/ready

If the endpoint returns HTTP 503, the NIM might still be initializing. Retry after a few seconds. If the endpoint continues to return 503, inspect the container logs.

View Logs#

View NIM logs:

docker logs vsr-nim

The reference client runs in the foreground and prints logs directly to the terminal. The script removes the previous client container at startup, so inspect terminal output before re-running it.

Common Issues#

Issue	Action
GPU not found	Verify NVIDIA Container Toolkit is installed and the host has a compatible NVIDIA driver.
Port already in use	Change the host-side `-p` mapping, or change `NIM_HTTP_API_PORT` and `NIM_GRPC_API_PORT` and publish the matching ports. Do not override `NIM_DISABLE_MODEL_DOWNLOAD` or `NIM_DISABLE_GRPC_STARTUP`; refer to Reserved Environment Variables.
Target resolution rejected	Reduce `target_resolution` so it stays within the 4x per-dimension limit and the encoder limit for the selected codec.
Input fails to decode	Verify that the host GPU supports NVDEC for the selected codec and chroma format.
Audio-only input rejected	VSR expects video input. Audio-only Cloud File inputs such as MP3, AAC, WAV, or AC3 are rejected with a gRPC error; the container continues to run.
RTP error about unset environment parameters	The NIM image provides default RTP values. If this error appears, verify that variables such as `MY_POD_IP`, `PARSER_TOGGLE_IN`, `INTERNAL_UDP_PORT_START`, `EXTERNAL_UDP_PORT_START`, `NUM_OF_UDP_PORTS`, and `MAX_UDP_PORTS_PER_STREAM` were not cleared, or set them explicitly for your RTP network configuration.

Metrics#

The VSR NIM compressed-video workflow documentation does not define a Prometheus metrics endpoint for the media function. Do not configure monitoring based on generic AI for Media metrics endpoints unless you have verified the endpoint in the deployed image.