10.4. CUDA accelerator errors
You might experience a
self.graph.replay()error when running a model using CUDA accelerators.If vLLM crashes and the error trace captures the error somewhere around the
self.graph.replay()method in thevllm/worker/model_runner.pymodule, this is most likely a CUDA error that occurs inside theCUDAGraphclass.To identify the particular CUDA operation that causes the error, add the
--enforce-eagerserver argument to thevllmcommand line to disableCUDAGraphoptimization and isolate the problematic CUDA operation.You might experience accelerator and CPU communication problems that are caused by incorrect hardware or driver settings.
NVIDIA Fabric Manager is required for multi-GPU systems for some types of NVIDIA GPUs. The
nvidia-fabricmanagerpackage and associated systemd service might not be installed or the package might not be running.Run the diagnostic Python script to check whether the NVIDIA Collective Communications Library (NCCL) and Gloo library components are communicating correctly.
On an NVIDIA system, check the fabric manager status by running the following command:
$ systemctl status nvidia-fabricmanagerOn successfully configured systems, the service should be active and running with no errors.
-
Running vLLM with tensor parallelism enabled and setting
--tensor-parallel-sizeto be greater than 1 on NVIDIA Multi-Instance GPU (MIG) hardware causes anAssertionErrorduring the initial model loading or shape checking phase. This typically occurs as one of the first errors when starting vLLM.