You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/usage/troubleshooting.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,7 @@ You can check if this is happening by trying the old defaults with `--generation
35
35
If other strategies don't solve the problem, it's likely that the vLLM instance is stuck somewhere. You can use the following environment variables to help debug the issue:
36
36
37
37
-`export VLLM_LOGGING_LEVEL=DEBUG` to turn on more logging.
38
+
-`export VLLM_LOG_STATS_INTERVAL=1.` to get log statistics more frequently for tracking running queue, waiting queue and cache hit states.
38
39
-`export CUDA_LAUNCH_BLOCKING=1` to identify which CUDA kernel is causing the problem.
39
40
-`export NCCL_DEBUG=TRACE` to turn on more logging for NCCL.
40
41
-`export VLLM_TRACE_FUNCTION=1` to record all function calls for inspection in the log files to tell which function crashes or hangs. Do not use this flag unless absolutely needed for debugging, it will cause significant delays in startup time.
0 commit comments