Errors list

0

Unknown Error

An error has occurred that cannot be determined by the platform.

Study the logs of the service that was accessed when the error occurred. Contact the technical support.

1001

Check the node_id parameter correctness.

1003

A socket descriptor is in use

Error of the  gomon  monitoring service on the cluster node. 

Restart the  gomon  service on the cluster nodes.

1011

Error occurs when:

• reconnecting a storage system to a node or cluster;
• deleting a storage system with active connections or attached volumes.

• Before connecting, make sure the storage system is not already connected to the specified node or cluster.
• Before deletion, disconnect the storage system from all nodes and clusters.

1111

Unexpected Error

An error has occurred that cannot be detected by the platform.

Study the logs of the service that was accessed when the error occurred. Contact the technical support.

1352

Platform movement already in progress

The platform migration to the virtual machine is already running.

Wait for the platform to be migrated to the virtual machine. 

1354

Platform not moved to VM: Supported OS is not available in the selected cluster

Failed to move the platform to the VM. There is no suitable OS template in the selected cluster.

• In the cluster settings, add the OS that matches the OS on the platform server.
• If you use your own OS templates, make sure that their names meet the conditions given in the article  Moving platform to VM.

2005

• Make sure the filter contains no syntax errors.
• Make sure the filter and the field it is created for exist.

3001

Unauthorized

The request was executed without authorization.

Make sure that the request is executed under the authorized user name.

3003

User not found

User not found. 

Select an existing user.

3004

Template not found

The requested OS template is missing.

Select an existing OS template.

The user does not have permission to perform the operation.

• Check account access settings.
• If the error occurs when attempting to delete a user, verify that the request is from the Administrator role.
• If an error occurs when attempting to create a VM with SPICE access, verify that the request is from the Administrator or Advanced user role.

3008

Bad request

Error in forming or processing a request.

If the request is executed via API, check the format of the request. 

3009

Forbidden

No permissions to execute the request.

Check the permission level of the user executing the request.

3021

Error response from telegram-srv: Bad request: chat not found

No Telegram chat found to send notification.

Check the notification settings for Telegram. Add chat for notifications if necessary.

3106

Log in under another administrator account and delete your account.

5010

Os id unknown

API request contains the id of the operating system, information about which is not in the platform database.

5013

Check the specified id.

5015

Check the specified id.

5044

No record found in vm_ip_fabric_settings table for the selected cluster. The error may occur due to:

• calling cluster/{cluster_id}/routing/update or node/{node_id}/routing/update for a cluster with "Switching" or "Routing" configuration type. In this case the error value is "Only IP-Fabric type supported for this handler";
• inconsistent database state.

• Do not use the called methods.
• Contact technical support.

• Specify an existing network.
• Check the ipnet_id parameter correctness.

5051

Check the dc_network_id parameter correctness.

5062

Attempt to get an import history record by id when the record is missing in the database.

• Make sure the passed id is correct.
• View existing ids using the /vm/v3/import_history method.

5066

Error occurs when working with migration history from IPmanager 5 if the record is not found.

Make sure the passed id is correct.

5067

Get checker service logs and contact technical support.

5069

• Check the list state using the host/{host_id}/snapshot method. Examine the state field value:
  • fail — create another snapshot;
  • creation — wait for the snapshot to be created;
  • unknown — contact technical support.

5072

Live migration is not available for VMs with Qcow2 format disk snapshots

The live migration of VMs with Qcow2 snapshots is not available.

• Stop the VM before migration.
• Delete VM snapshots before migration.

5074

Attempt to migrate a VM that has a snapshot in LVM storage with saved RAM state.

Remove snapshots from LVM storage.

5079

5080

• Create the required bridge on the cluster node.
• Check the request correctness — bridge name and id.

5081

5082

5088

• Recreate the interface with the desired bridge.
• Check that the host_id and iface_id parameters are specified correctly in the request.

5090

5091

• Disconnect the interface from the bridge or bond.
• Use a different interface.

5092

• The IP address is already used by another network interface.
• The IP address overlaps with other addresses or subnets that do not belong to this interface.
• IPmanager service error.

5093

Occurs when saving the OS list when the CPU mode for the OS is not supported.

5097

5098

5111

Failed to get data from the OS templates repository, or no suitable OS found in the repository metadata.

• Check the repository address availability and network connectivity between the repository and the platform.
• Check the metadata.json file in the OS repository. After changing the file, update the repository in the platform interface.

• Check object access rights.
• If the error occurs during an API call, check if the object ID is specified correctly.
• Perform the action under a user with the Administrator role.

5115

5116

• In methods node/{node_id}/metrics, host/{host_id}/metrics, master/metrics the target request parameter is missing.
• In the ssh_address method, ip or id is missing.
• In the host/{host_id}/validate_hot_plug_resources method, the cpu_number or ram_mib parameter is missing.

5117

The VM is blocked

The error can occur if the administrator stopped the user's VM and then the VM was started by non-platform means. 

• For users: contact the platform administrator.
• For administrators: enable the VM using the platform means.

5133

• Restart the vault service with the command docker restart vault
• Contact technical support.

5134

There is no suitable node in cluster

There is no suitable node in the cluster for creating or migrating a VM. 

5135

Node has a bad state

Attempt to perform an action with a node in crashed or unavailable state, or libvirt and lxd services are unavailable on the node.

• Reboot the cluster node.
• Check SSH connection and node availability from the platform side.
• Check the status of libvirt and lxd services on the node.
• Follow the instructions in the  If the cluster node is unavailable  article.

5136

5139

Remove the hetzner_ip parameter from the request.

5142

Delete the entire subnet.

5143

Use an IPv6 subnet.

5144

• Perform the action with the Administrator role.
• Increase the  Maximum size of uploaded ISO images  parameter in the global system settings. See the article  Mounting an ISO image  for details.

5157

Backup location check failed

5161

• Examine the logs — on the platform server run the command docker exec vm_box bash -c grep -r 'Failed to delete host ' /var/log
• Contact technical support.

5169

CPU cores number on node exceeds license limit

The number of CPU cores available under the license has been exceeded.

Follow the instructions in the article CPU core number exceeded.

5175

5176

Incorrect relationship between network interfaces.

5177

• Create a new interface.
• Contact support.

5186

Select an allowed value.

CdromLimitExceeded

Disconnect any unused ISO images from the virtual machine.

5223

Specify a unique value for the boot_order parameter.

5229

• Check the node connection parameters.
• Check node network availability.
• Reconnect the node.
• If the platform version is 2026.02.1 or higher, collect logs /var/log/node_info.log and /var/log/node_create/node_*.log in the vm_back container and contact technical support.
• If the platform version is lower than 2026.02.1, collect logs /var/log/node_info.log and /var/log/node_create/node_*.log in the vm_box container and contact technical support.

5232

Task registration error

The task cannot be registered.

Repeat the operation that caused the error. If the error occurs again, contact technical support.

Node has libvirt errors

Problems with  libvirt  daemon on a cluster node. 

Check  libvirt  using the instructions in the  Basic diagnostics  article.

• Check the node network configuration and the presence of bridges.
• Create the required bridge.

5242

Failed to put SSH-key on node. Check your password or ~/.ssh/authorized_keys on node

An error occurs when trying to copy the platform SSH key to a cluster node or Ceph storage.

• Check if you can connect to the cluster node or Ceph storage via SSH from the platform server.
• Check if the following SSH connection settings are correct: server IP address, port and password.

• Check the node's network configuration and verify bridge availability.
• Migrate VMs from this node to others or delete them.

5244

Deleting such a node is not supported.

5246

Given IP does not belong to any IP-pool assigned to cluster

An error can occur when:

• attempting to issue an IP address from a network that does not belong to the cluster;
• receiving information about an IP address that is not found in the database.

Use an IP address from a pool that belongs to the cluster.

5248

The specified amount of RAM is less than minimal requirement for this OS

The VM does not have enough RAM to install the selected OS. 

Increase the amount of RAM on the VM. 

5249

5251

5253

5255

• Perform a GET request /vm/v3/host/{id} and examine the values of the parameters iso and iso_data.
• Reattach the image.

5256

Attempt to detach an ISO image that is not in the mounted state.

5260

The ISO image in the vm_os table has no link to a repository (repository_id is missing), but the operation requires a repository.

• Use an OS from the repository returned by the GET request /vm/v3/os
• Connect an ISO image repository.
• Upload a local ISO image file.

5264

The repository does not belong to any storage.

5265

Attempt to create an ISO image download task from a repository when task creation is impossible due to incorrect configuration.

• Make sure the ISO image is attached from a repository.
• Make sure the repository is linked to a storage.

5266

The ISO image has not yet been downloaded or has been deleted.

• Wait for the download to complete.
• Download the ISO image again.

5268

Contact technical support.

5270

5271

5272

5275

5277

5279

5280

Migration of VMs with snapshots between different Network LVM is not allowed.

Migration of VMs with snapshots between different Network LVM is not allowed.

Delete VM snapshots before migration. For more information about migrating VMs with snapshots, see the  Snapshots of virtual machines  article.

5307

5308

License expired

License expired.

Check the license expiration date. If the license is valid, activate it.

5312

• Repeat the request.
• Collect platform logs using the command vm collect-logs and contact technical support.

5317

5318

5319

Nothing to change

The POST request parameters do not change anything. 

Check if the POST request is necessary. If the request is necessary, change its parameters.

5321

Insufficient space in the storage. Clear space or delete the virtual machines that you don't need

There is not enough free space in the storage.

Delete unnecessary files or virtual machines in this storage.

5330

Host is crashed

VM is crashed.

Examine the actions that led to the damage to the VM.

5333

Attempt to delete limits when there is no information about the limits of this role or account.

5334

License or user account limit reached. The parameter for which the limit is reached is indicated in the error text. For example, number of users, nodes, VMs, CPUs, IP addresses.

• For a user: ask the administrator to increase the limit or delete unused resources.
• For an administrator: increase the license limits or delete unused resources.

5337

Use the special POST requests vm/v3/settings/max_user_iso_size and vm/v3/settings/send_vm_messages

5341

5352

No KVM virtualization support on node

The connected cluster node does not support hardware virtualization.

Enable hardware virtualization support in the BIOS/UEFI of the cluster node. 

5354

Сan not get node info

Unable to get cluster node information.

Check the connection to the cluster node via SSH.

5361

Release data unavailable

No access to Changelog messages.

Check access to the Changelog files. If the platform uses a proxy server, check its settings.

5365

Unsupported operating system on node

An unsupported OS is installed on the connecting cluster node.

Install a supported OS and reconnect the node.

5367

5372

Attempt to add a node without the nf_conntrack kernel module.

5380

5381

When selecting custom mode for CPU, no custom CPU model (cpu_custom_model) is specified.

5387

IP fabric cluster doesn't support the OS

An unsupported OS is installed on the connecting IP-fabric cluster node.

Install a supported OS and reconnect the node.

• Add an email template in the missing language.
• Delete the recipient of the e-mail from the list.
• Disable sending of the e-mail.

5398

5399

5400

5401

5402

Attempt to edit an OS using methods for editing an ISO image.

5413

Editing node network settings is not allowed in a cluster with an IP fabric

Changing the network settings of a node in an IP-fabric cluster is not supported.

The operation is not supported.

Unable to find a suitable IPv6 subnet for the virtual machine (VM).

• Add IP addresses to the pools from which the subnet is allocated.
• Increase the subnet prefix value. 

5501

5601

Relocating a virtual machine to another node without disk migration is only possible for network storages.

5602

Use migration to move VMs from a working node. Relocation is only available for failed nodes.

5705

5710

Failed to enable high availability in the cluster. Possible reasons:

• node access issues;
• storage configuration issues;
• network configuration issues;
• insufficient resources to enable high availability.

• If the platform version is 2026.02.1 or higher, examine the logs /var/log/vm_writer.log in the vm_back container.
• If the platform version is lower than 2026.02.1, examine the logs /var/log/vm_writer.log in the vm_box container.

5801

ZFS utilities (zpool, zfs) are not installed on the node in the LXD cluster.

5919

5921

Storage on destination node is not active

The error may occur when selecting a storage with a status other than "Active".

Check the status of the storage. If it is out of service, select another one.

5926

Repository metadata validation failed

Incorrect repository description file  metadata.json . 

Correct the repository description file. 

5928

5930

5935

It is forbidden to use users named admin and bootstrap for CephFS.

5937

• Enable high availability on the cluster node.
• Make sure the cluster nodes are connected to network storage.

5942

Failed to find the default bridge on the node selected to create the VM.

Check if there is a default bridge for the selected network type on the node — primary or secondary.

5946

Attempt to change network settings on a cluster for which modification is not supported.

5949

5955

5956

The "Integration with PowerDNS" module is not supported. Use the Integration with DNSmanager 6 module.

5957

5966

IP address busy

Unable to assign an IP address to the virtual machine.

Change the IP address assignment settings: select a different IP address or address pool. If the address is assigned via DHCP, check the DHCP server settings.

5971

5974

5978

• Check the availability of the auth service.
• Check if the user session is active.
• Check if the user is authorized.

5979

• Examine the error message. It contains the cause of the problem.
• Check the correctness of the data, access rights, and availability of the authorization service.
• If the platform version is 2026.02.1 or higher, examine the logs /var/log/vm_writer.log in the vm_back container.
• If the platform version is lower than 2026.02.1, examine the logs /var/log/vm_writer.log in the vm_box container.

5981

• Examine the error message. It contains the cause of the problem.
• If the platform version is 2026.02.1 or higher, examine the logs /var/log/vm_writer.log in the vm_back container.
• If the platform version is lower than 2026.02.1, examine the logs /var/log/vm_writer.log in the vm_box container.

5982

This action is not supported in a VMmanager 5 cluster.

5983

The VM is not ready for migration from a VMmanager 5 cluster.

• Examine the error message. It contains the cause of the problem. Possible options:
  • nat_or_extra — the VM has a network interface connected to NAT;
  • net_iface_count — more than one VM network interface is connected to the same network bridge.
• Change the VM network configuration.
• Remove the VM interface or connect it to a free network bridge.

5984

• Detach ISO images from the VM.
• Remove VM snapshots.
• Move VM disks to supported storage types.

5987

The QEMU Guest Agent version on the source node is outdated, the minimum supported version is indicated in the error message.

5988

5990

5991

Error can occur when changing the IP address addition model or creating a VM image. 

• Add missing network interfaces to the guest OS.
• Add missing IP addresses to the guest OS.
• Wait for the migration from VMmanager 5 to complete.

5992

• QEMU Guest Agent on the VM is not responding.
• VM migration with automatic IP address addition failed.

• Perform QEMU Guest Agent diagnostics following the instructions in the article  How to check and restore QEMU Guest Agent?
• Disable automatic IP address allocation for the VM for the migration period.

5993

QEMU Guest Agent installation is not supported on FreeBSD OS.

5994

5995

5998

Migration cannot be performed if the source and destination nodes have OS from different Linux families. For example, the source node has a Red Hat family OS, and the destination node has a Debian family OS.

6003

6007

6008

6010

6011

Failed to switch the node to maintenance mode.

6012

Maintenance is in bad state for this handler

The cluster node cannot enter or exit maintenance mode. 

6013

The maintenance mode status is different from evacuation or return.

Use delete maintenance mode instead of cancel.

6014

6016

6034

Error occurs when trying to migrate a VM with the selected IPv4 address addition model from a VMmanager 5 cluster to a cluster with IP-Fabric configuration type when the network is not synchronized.

6035

Error occurs when trying to automatically determine the network bridge for a VM interface in a cluster with IP-Fabric configuration type.

6053

6055

6057

Use a backup of a full VM, not a linked clone.

6061

6066

User already exists

A user with this email already exists. 

• Specify a different email for the user.
• If the account is created via user invitation, add the user via the  Re-invite  function (POST request  /reinvite).

6067

User does not exist

The user with this email does not exist. 

Check if the email in the request is correct and repeat the request.

6068

Host limit exceeded

The license limit for the number of virtual machines has been exceeded.

Increase your license limit or delete some VMs.

6070

6072

6073

• Examine the logs /opt/ispsystem/vm/install.log on the platform server.
• Make sure the target VM supports increasing CPU, RAM, and disk size without rebooting.

6075

No free MAC addresses available (adapter limit USHRT_MAX = 65535).

6076

Using the vm/v3/setting method with request parameters

{
  name: qemu_reserve_mac_bytes,
  value: 52:54:00
}

set the qemu_reserve_mac_bytes value.

6077

6080

• Restart the platform migration process.
• Check if the process /usr/local/bin/vm web is running on the platform server. If not, start it with the command vm web.
• Examine the error text and the log /opt/ispsystem/vm/install.log on the platform server.

6081

6082

• Restart the platform migration process.
• Check if the process /usr/local/bin/vm web is running on the platform server. If not, start it with the command vm web.
• Examine the error text and the log /opt/ispsystem/vm/install.log on the platform server.

6083

6084

6085

6086

6087

6103

6112

Adding a node with a non-root account is not available for this OS

When   connecting  a  node   with  AlmaLinux  or   Ubuntu   OS , a  user   name  other  than   root  is  specified .

Reconnect  the  node .   Specify  the  root   username .

6116

6119

6127

Attempt to assign both a custom and a predefined role to a user simultaneously.

Check the data passed in the request: the rbac_list parameter must be absent or empty when using predefined roles.

6139

6140

6141

6142

• Make sure the SAN service is running and available.
• Examine the error details in the SAN service logs.
• Make sure the specified storage id (external_storage_id) exists.
• Restart the SAN service.

6143

• Contact the network administrator to check the correctness of SAN storage settings and the presence of disks.
• Check the presence of dss, dss_type fields in the request.
• Make sure you use a supported storage type in the request: iscsi or fc.
• Make sure the selected volume contains disks.
• Check that the response conforms to JSON format.

6144

6145

6146

6147

6148

6149

6150

6151

6156

6157

6158

6159

6160

666009

Getting license from server error

Licensing service error. 

Examine the licensing service logs.