Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for DataSphere
    • Resolving project startup errors in DataSphere
    • Resolving the `Failed to deserialize variable` error
    • `Table of Contents` extension is missing in the JupyterLab extension catalog
    • Getting access to GPU g1.1 and higher configurations in DataSphere
    • Resolving issues with long code execution within DataSphere project cells
    • Resolving the `Servant not allocated` error when running code within DataSphere project cells
    • Resolving the `TestsFailure` error
    • Resolving the `Token authentication is enabled` error
    • Resolving errors with project access or login
    • Resolving the `KernelNotResponding The kernel died unexpectedly` error
    • Fixing the `ConnectTimeoutError` error when installing packages through pip
    • Resolving the `Device or resource busy` error

In this article:

  • Issue description
  • Solution
  • If the issue persists
  1. DataSphere
  2. Resolving the `Servant not allocated` error when running code within DataSphere project cells

Fixing the Servant not allocated error when running code within DataSphere project cells

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution
  • If the issue persists

Issue descriptionIssue description

When trying to execute code from Jupyter notebook cells within the DataSphere project, you get one or more error messages:

  • Preparing c1.4 instance
  • Execute error: Servant c1.4 not allocated: Internal Error

SolutionSolution

The Execute error: Servant g1.1 not allocated: Internal Error message may appear due to a temporary lack of free GPUs in DataSphere. Try using another configuration, e.g., c1.8, or execute code in the cell once again later.

If you are using a custom Docker image in your project, check whether you can reproduce the issue on a public image, e.g., on Ubuntu.

Tip

If the issue persists for a while, try opening the project page in private mode of your browser; this will rule out issues on the browser cache side.

If the issue persistsIf the issue persists

If the above actions did not help, create a support ticket.
Provide the following information in your ticket:

  1. Link to the project in DataSphere from the address bar of your browser.
  2. Screenshots of the error and the code snippet that causes the error.
  3. Approximate date and time when the issue occurred.
  4. Information about third-party Docker images used in the project.
  5. Description of the scenario where you need the c1.4 configuration and issues it will help you solve.

Was the article helpful?

Previous
Resolving issues with long code execution within DataSphere project cells
Next
Resolving the `TestsFailure` error
© 2025 Direct Cursus Technology L.L.C.