Model Gallery FAQ

Updated at:

Troubleshoot model deployment, training failures, service errors, and debugging issues in PAI Model Gallery.

Ask PAI Agent first

The PAI AI assistant (Xiao PAI) covers the full PAI product suite — providing usage guidance, and offering diagnostic capabilities for DSW instances, DLC jobs, and EAS services. It automatically identifies failure causes and recommends next steps and tools.

image

Q: How do I check whether deep thinking is enabled for a model evaluation?

Check the default deployment configuration on the model description page. All models are evaluated using their default deployment settings.

Q: How do I deploy a model after training?

  1. Go to PAI-Model Gallery > Task Management.

  2. Find the completed training task and click it to open the details page.

  3. Click Deploy in the top-right corner.

image

Q: How do I troubleshoot a failed training task?

When a training task fails, check the task diagnostics or logs. A common cause is incorrectly formatted dataset.

Two ways to find the error details:

  • Task diagnostics: In PAI-Model Gallery, go to Task Management > Training Tasks. Click the failed task to open its Task Details page. Hover over the Failed status to view an error summary.

    image

  • Task logs: On Task Management > Training Tasks, select the Task log tab to view the full error message.

    image

    Common error messages and solutions:

    Error type

    Error message

    Solution

    Input/output errors

    ValueError: output channel ${your OSS uri} must be directory

    Verify that the output path is a directory and not a file.

    ValueError: train must be a file

    Verify that the input path points to a file and not a directory.

    FileNotFoundError

    Ensure that a valid file exists at the specified input path.

    JSONDecodeError

    Verify that the JSON file is formatted correctly.

    ValueError: Input data must be a json file or a jsonl file!

    Ensure that the file is in JSON or JSONL format.

    KeyError: ${some key name}

    Review the model documentation and verify that all key-value pairs in your dataset match the required format. This error often occurs with JSON datasets.

    ValueError: Unrecognized model in /ml/input/data/model/.

    PyTorch does not recognize the model file format.

    UnicodeDecoderError

    Verify that the file uses the correct character encoding.

    Input/output error

    Ensure that you have read permission for the input path and write permission for the output path.

    NotADirectoryError: [Errno 20] Not a directory:

    Verify that the specified path is a directory.

    Hyperparameter settings

    ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: -9) local_rank: 0 (pid: 51) of binary: /usr/bin/python (and there are no related subprocess logs)

    Insufficient RAM causes an out-of-memory (OOM) error when loading the model. Select an instance type with more memory.

    torch.cuda.OutOfMemoryError: CUDA out of memory

    Insufficient GPU memory. Choose a GPU instance with more VRAM, or reduce memory-intensive hyperparameters like lora_dim or batch_size.

    ValueError: No closing quotation

    system prompt or another string parameter contains an unclosed quotation mark ("), preventing training command generation. Ensure all quotation marks are properly paired.

    Resource configuration of an instance type

    Exception: Current loss scale already at minimum - cannot decrease scale anymore. Exiting run

    Precision issue. The model uses BF16 format, which requires a GPU with Ampere or newer architecture (e.g., A10, A100). Training on older GPUs converts parameters to FP16, which can cause this underflow error.

    RuntimeError: CUDA error: uncorrectable ECC error encountered

    Hardware fault on the GPU instance. Retry the training task. If it fails again, try a different instance type or region.

    MemoryError: WARNING Insufficient free disk space

    Disk is full. Select an instance type with more disk space.

    User limit errors

    failed to compose dlc job specs, resource limiting triggered, you are trying to use more GPU resources than the threshold

    GPU quota exceeded. Training tasks are limited to 2 concurrent GPUs by default. Wait for a running task to complete, or submit a ticket to request a quota increase.

Q: How do I perform online debugging for a deployed model?

After deploying your model as a service on PAI-EAS, use the built-in online debugging tool.

  1. Find the deployed service: Go to PAI-Model Gallery > Task Management > Deployment Tasks. You are redirected to the PAI-EAS console where you can view the deployed service.

    image

  2. Open the debugging tool: On the PAI-EAS page, locate your service. In the Operation column, click Online Debugging.

    image

  3. Configure and send a request:

    1. Find the required request format on the model description page in PAI-Model Gallery. For example, a model deployed using BladeLLM might expect a POST request to /v1/chat/completions with a specific JSON body.

      image

      image

    2. In the Online Debugging UI, append the path (e.g., /v1/chat/completions) to the Request URL.

      image

    3. Populate the Request Body using the example from the model's description page and click Send Request.

Q: Why am I getting a "503 no healthy upstream" error when calling my deployed model?

A 503 Service Unavailable error with message no healthy upstream indicates the service instance is out of resources and cannot process new requests.

image

  • Cause: Instance resources (CPU, memory, or GPU memory) are fully utilized, leaving no capacity for new requests.

  • Solution: The correct action depends on your resource type:

    • Public Resources: The shared resource pool is temporarily overloaded. Try again during off-peak hours, or redeploy to a different region or instance specification.

    • Dedicated Resources (EAS Resource Group): Your resource group is underscaled. Ensure the group has sufficient CPU, memory, and GPU memory. Maintain at least 20% resource buffer.

Q: Why do I get "SupportsDistributedTraining false, please set InstanceCount=1" error during training?

  • Cause: The selected model does not support distributed training, but the task was configured to run on multiple nodes (InstanceCount > 1).

  • Solution: Set Number of Nodes to 1 in your training task configuration and restart the task.

    image

Q: Model API returns 404 - {'detail': 'Not Found'}

Possible causes:

  1. The model service does not support API calls. Some models deployed from Model Gallery only support web-based interaction through the Web App button on the service details page. These models do not provide OpenAI-compatible API endpoints and cannot be called by using the OpenAI SDK. For example, PAI-DistilQwen2.5-7B-Instruct.

  2. The request path is incomplete or incorrect. For example, the chat API endpoint is typically in the format of {domain}/api/predict/{service_name}/v1/chat/completions.

Model Selection FAQ

Q: What is the difference between PAI-DistilQwen2.5-7B-Instruct and DeepSeek-R1-Distill-Qwen-7B?

Both PAI-DistilQwen2.5-7B-Instruct and DeepSeek-R1-Distill-Qwen-7B are distilled from Qwen2.5-7B, but they serve different scenarios:

Dimension

PAI-DistilQwen2.5-7B-Instruct

DeepSeek-R1-Distill-Qwen-7B

Base model

Qwen2.5-7B-Instruct

Qwen2.5-7B + DeepSeek-R1

Distillation method

Black-box data distillation + white-box logits distillation

Knowledge distillation (reasoning capability transfer)

Use case

General instruction following

Math and reasoning tasks

Key feature

Significantly improved instruction following capability compared to the original model.

For math problems, include step-by-step reasoning instructions in the prompt.

Q: What is the difference between Fun-CosyVoice and the legacy CosyVoice?

Fun-CosyVoice 3.0 is an advanced text-to-speech (TTS) system based on large language models (LLMs). It outperforms its predecessor CosyVoice 2.0 in content consistency, speaker similarity, and prosody naturalness.

Q: What are the differences between Qwen3 Embedding models?

The following table compares the Qwen3 Embedding models:

Model

Model weights

VRAM usage

Max embedding dimension

Use case

Qwen3-Embedding-0.6B

1.12 GiB

2-4 GB

1024

Lightweight retrieval, memory-sensitive

Qwen3-Embedding-4B

7.55 GiB

10-14 GB

2560

Standard semantic search

Qwen3-Embedding-8B

14.11 GiB

18-24 GB

4096

High-precision, complex semantics

Choose the appropriate model and GPU based on your use case:

Scenario

Recommended model

Recommended GPU

Budget

Individual development/POC

0.6B

RTX 3060 / Laptop

Low

SME API

4B

A10 (24G)

Medium

Enterprise production

8B

A100 40G/80G

High

Ultra-large-scale vector database

0.6B or 4B

A10 x multi-instance

Medium

High-precision semantic search

8B

H100 (80G)

Very high

Model Gallery supports one-click deployment of Qwen3-Embedding models. Note the following:

  • When --max-model-len is not specified, vLLM reads max_position_embeddings from the model's config.json by default. This parameter directly limits the maximum number of input tokens. Input that exceeds the limit is truncated or causes an error.

  • Embedding models do not perform autoregressive generation, but vLLM still pre-allocates the full KV Cache, which wastes VRAM. We recommend that you explicitly set a smaller --max-model-len based on your actual business requirements. This significantly reduces VRAM usage and improves concurrency while avoiding resource waste caused by over-allocation.