Troubleshooting

Find your symptom below, then follow the linked fix. For CLI syntax, see Run a Benchmark.

Debug logging

Enable debig output to inspect request handling and worker startup:

GUIDELLM__LOGGING__CONSOLE_LOG_LEVEL=DEBUG guidellm run ... --disable-progress

Run guidellm env to confirm the settings are being applied. The --disable-progress call is optional, but the interactive progress console can overwrite console log messages. Alternatively, you can use a file log as mentioned in the logging guide .

For all logging options (file output, log levels), see Logging in the development guide.

Tokenizer: trust_remote_code

Symptom

You get an error that looks like:

The repository moonshotai/Kimi-K2.6 contains custom code which must be executed
to correctly load the model. You can inspect the repository content at
https://hf.co/moonshotai/Kimi-K2.6.
You can avoid this prompt in future by passing the argument `trust_remote_code=True`.

Fix

If you fully trust the model, pass trust_remote_code through --tokenizer load_kwargs:

--tokenizer '{"kind":"huggingface_auto","load_kwargs":{"trust_remote_code":true}}'

Do not use this if you do not trust the model, as this allows code execution on your machine.

See Datasets: Tokenizer for other tokenizer options.

macOS worker crash (signal 11)

Symptom

RuntimeError: Worker process group startup failed: Worker process <pid> died
unexpectedly (signal 11). Check system logs for details

You may also see repeated log lines such as:

Worker process <pid> died unexpectedly (signal 11)

Fix

GuideLLM defaults to fork multiprocessing, which can segfault on macOS. Use spawn instead:

GUIDELLM__MP_CONTEXT_TYPE=spawn guidellm run ...