Error code | Interface message | Brief description | Possible solutions |
---|---|---|---|
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. | |
401 | You are not authorized, or your session has expired, please try to re-authenticate | User is not authorized. | Repeat the authorization procedure. |
403 | Not enough rights to perform the request | The user lacks rights to perform the request. | Contact your program administrator. |
404 | The page you requested was not found | Request for a non-existent interface page. | Return to the previous page using browser tools. |
501 | An internal server error has occurred | Internal server error. | Repeat the request. |
503 | Service temporarily unavailable. Please try sending the request again later | Problem with service operation. | Repeat the request. |
504 | Service is not responding. Please try sending the request later | Problem with service operation. | Repeat the request. |
A socket descriptor is in use | Error of the gomon monitoring service on the cluster node. | Restart the gomon service on the cluster nodes. | |
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. | |
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. | |
Unauthorized | The request was executed without authorization. | Make sure that the request is executed under the authorized user name. | |
User not found | User not found. | Select an existing user. | |
Template not found | The requested OS template is missing. | Select an existing OS template. | |
3005 | Access denied | User access is denied. | Check account access settings. |
Bad request | Error in forming or processing a request. | If the request is executed via API, check the format of the request. | |
Forbidden | No permissions to execute the request. | Check the permission level of the user executing the request. | |
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. | |
5006 | IP address unknown | A non-existent IP address is specified. | Specify an existing IP address. |
5007 | Cluster id unknown | A non-existent cluster is specified. | Specify an existing cluster. |
5008 | Mac id unknown | A non-existent MAC address is specified. | Specify an existing MAC address. |
5009 | Network id unknown | A non-existent network is specified. | Specify an existing network. |
Os id unknown | API request contains the id of the operating system, information about which is not in the platform database. | Check if the operating system with this id is contained in the platform database. | |
5011 | Repository id unknown | A non-existent repository is specified. | Specify an existing repository. |
5012 | Disk id unknown | A non-existent disk is specified. | Specify an existing disk. |
5014 | Can not find proper task table record | Unable to find a suitable task in the task table. | Clarify search conditions and repeat the task search. |
5016 | Recipe id unknown | A non-existent script for a VM is specified. | Specify an existing script. |
5017 | Preset id unknown | A non-existent configuration is specified. | Specify an existing configuration. |
5018 | Network storage unknown | A non-existent network storage is specified. | Specify an existing network storage. |
5019 | Storage tag unknown | A non-existent storage tag is specified. | Specify an existing storage tag. |
5020 | Storage unknown | A non-existent local storage is specified. | Specify an existing local storage. |
5021 | Host id unknown | A non-existent VM is specified. | Specify an existing VM. |
5022 | Account id unknown | A non-existent account is specified. | Specify an existing account. |
5023 | Image id unknown | A non-existent image is specified. | Specify an existing image. |
5024 | Ip pool id unknown | A non-existent IP address pool is specified. | Specify an existing IP address pool. |
5025 | Node id unknown | A non-existent cluster node is specified. | Specify an existing cluster node. |
5026 | Ssh key id unknown | A non-existent SSH key is specified. | Specify an existing SSH key. |
5027 | Os Group unknown | A non-existent OS family is specified. | Specify an existing OS family. |
5028 | Hetzner ip id unknown | A non-existent IP address in a cluster with the "Routing" setting type is specified. | Specify an existing IP address. |
5029 | Hetzner subnet id unknown | A non-existent IP address subnet in a cluster with the "Routing" setting type is specified. | Specify an existing subnet. |
5030 | Virt pool id unknown | A non-existent IP address pool is specified. | Specify an existing pool. |
5031 | Inconsistent params of ippools connect | Incorrect IP address pool parameters. | Check pool parameters. |
5032 | Bad interface index | Incorrect network interface index. | Check the network interface index. |
5033 | Different number of interfaces | The number of network interfaces differs from the required number. | Check the number of network interfaces. |
5034 | Must set interfaces | Incorrect network interface parameters. | Check network interface parameters. |
5035 | Too many interfaces | The number of network interfaces exceeds the maximum allowed. | Reduce the number of network interfaces. |
5036 | Two interfaces no support ipv6 | This configuration does not support IPv6 addressing. | Change the configuration or switch the addressing type to IPv4. |
5037 | Host interface unknown | A non-existent VM interface is specified. | Specify an existing VM interface. |
5039 | Backup location unknown | A non-existent VM backup storage is specified. | Specify an existing storage. |
5040 | Schedule unknown | A non-existent VM backup schedule is specified. | Specify an existing schedule. |
5041 | Platform backup schedule unknown | A non-existent platform backup schedule is specified. | Specify an existing schedule. |
5042 | Platform backup storage unknown | A non-existent platform backup storage is specified. | Specify an existing storage. |
5043 | Platform backup unknown | A non-existent platform backup is specified. | Specify an existing copy. |
5046 | Storage to cluster unknown | A non-existent cluster storage is specified. | Specify an existing storage. |
5047 | Storage unknown | A non-existent storage is specified. | Specify an existing storage. |
5048 | Script variable unknown | A non-existent script variable is specified. | Specify an existing script variable. |
5049 | Recipe param unknown | A non-existent script parameter is specified. | Specify an existing script parameter. |
5050 | Ip network id unknown | A non-existent physical network is specified. | Specify an existing network. |
5052 | Host interface id unknown | A non-existent VM interface is specified. | Specify an existing VM interface. |
5053 | Node interface id unknown | A non-existent virtualization node interface is specified. | Specify an existing virtualization node interface. |
5054 | Node bridge id unknown | A non-existent bridge is specified. | Specify an existing bridge. |
5055 | Node bond id unknown | A non-existent bond is specified. | Specify an existing bond. |
5056 | Ip pool to cluster unknown | A non-existent IP address pool in the cluster is specified. | Specify an existing pool. |
5057 | Vxlan id unknown | A non-existent VxLAN is specified. | Specify an existing VxLAN. |
5058 | Can not find allocated ip in ipmgr | IP address not found. | Check the correctness of the IP address. |
5059 | Disk bus is unknown | A non-existent disk connection type is specified. | Specify an existing connection type. |
5060 | IP address unknown | A non-existent IP address is specified. | Specify an existing IP address. |
5061 | Disk backup unknown | A non-existent disk backup is specified. | Specify an existing copy. |
5063 | Snapshot id unknown | A non-existent VM snapshot is specified. | Specify an existing VM snapshot. |
5064 | Tag id unknown | A non-existent tag is specified. | Specify an existing tag. |
5065 | Preset disk id unknown | A non-existent disk configuration is specified. | Specify an existing configuration. |
Live migration is not available for VMs with Qcow2 format disk snapshots | The live migration of VMs with Qcow2 snapshots is not available. |
| |
5100 | Some IP addresses are occupied by a block | Selected IP addresses intersect with an existing block. | Change the range of selected IP addresses. |
5101 | Network intersects with an existing one | The settings of the network being created intersect with the settings of an existing one. | Change the settings of the network being created. |
5102 | IP address is busy | IP address is busy. | Select another IP address. |
5103 | Network cannot be deleted. There is a dependent IP | The network cannot be deleted because there are dependent IP addresses. | Identify dependent IP addresses and release them. Repeat network deletion. |
5104 | Invalid IP | Access to an incorrect IP address. | Check IP address settings. |
5105 | Invalid IP range | Access to an incorrect IP address range. | Check the IP address range settings. |
5106 | Node cannot be deleted. There is a dependent host | The virtualization node cannot be deleted because VMs are located on it. | Delete VMs from the virtualization node, repeat node deletion. |
5107 | Cluster cannot be deleted. There is a dependent node | The cluster cannot be deleted, there are dependent nodes. | Delete dependent virtualization nodes, repeat cluster deletion. |
5108 | Node cannot be deleted. There is a dependent disk | The node cannot be deleted, because there is a dependent disk. | Delete the dependent disk. |
5112 | Not enough rights on object | Insufficient rights to access the object. | Check object access rights. |
5113 | There is no node in cluster | The cluster does not contain any nodes. | Add a virtualization node to the cluster. |
5114 | Cluster with same name already exists | A cluster with the specified name already exists. | Select a different name for the cluster. |
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. |
| |
5120 | Bad URL | Invalid URL. | Check the URL input for correctness. |
5121 | Source param missed | A parameter for creating a VM is missing, no OS or image. | Check the specified parameters for correctness. |
5123 | Cluster cannot be selected automatically | The cluster cannot be selected automatically. | Select the cluster manually. |
5124 | OS not available on cluster | OS is not available on the current cluster. | Select a different OS or a different cluster. |
5125 | Node check failed | Node cluster check failed. | Check the node server status. |
5126 | Host creation blocked on node | VM creation on the node is blocked. | Allow VM creation on the node. |
5127 | Can't find source location | Failed to find the node containing the image. | Check the availability of the required image on the nodes. |
5128 | Node is not ready | Node is not ready for operation. | Check node operability. |
5129 | Image is not available | Image is unavailable. | Check the image status. |
5130 | Invalid time zone | Invalid time zone. | Change the time zone. |
5131 | OS not available on node | OS is not available on the node. | Check the availability of the required OS on the node. |
5132 | Account cannot be deleted. There is a dependent host | The account cannot be deleted, there are dependent VMs. | Delete dependent VMs, repeat account deletion. |
There is no suitable node in cluster | There is no suitable node in the cluster for creating or migrating a VM. | Check if there are enough free resources on the cluster nodes. | |
5137 | Cluster doesn't have any pools | IP address pools are not connected to the cluster. | Connect the IP address pool to the cluster. |
5138 | Selected pools are not connected to the cluster | The selected IP address pools are not connected to the cluster. | Connect the IP address pools to the cluster. |
5140 | Some ips from this subnet are used in vm | The subnet contains busy IP addresses. | Select another subnet. |
5141 | Ip is active | IP address is used on VM. | Select another IP address. |
5145 | Minimal prefix in hetzner datacenter is 24 | The minimum prefix for the "Routing" network setting type is 24. | Increase the prefix value. |
5146 | Bad ipv6 subnet prefix | IPv6 prefix value is not supported. | Specify a prefix value from 32 to 96. |
5147 | No connected IPv6 subnet on node | There are no IPv6 subnets on the virtualization node. | Create an IPv6 subnet. |
5148 | Not enough free IPv6 blocks on the node | There are no free IPv6 blocks on the node. | Release the used IPv6 address block. |
5149 | Invalid ssh key | Invalid SSH key. | Check the correctness of the SSH key. |
5151 | No disk found for host | No disk found for VM. | Check the correctness of the disk specification. |
5152 | No interface found for host | No interface found for VM. | Check the correctness of the interface specification. |
5153 | ISO count limit exceeded | The number of ISO images has been exceeded. | Delete some ISO images. |
5154 | ISO size is too big | The size of the ISO image exceeds the maximum allowed. | Change the "Maximum size of uploaded ISO images" parameter in the system settings section. |
5155 | ISO is already mounted to host | An ISO image is already connected to the VM. | Disconnect the connected ISO image. |
5156 | ISO check is failed | The ISO image did not pass the check. | Check the integrity of the ISO image. |
5159 | Backup location check failed | Failed to check the backup storage. | Check access to the storage. |
5160 | Operation is not allowed for remotely stored images | The operation is not supported for images stored remotely. | Select an image in local storage. |
5162 | Backup storage connection check failed | Backup storage connection check failed. | Check access to the storage. |
5163 | Platform backup schedule have no connected storage | No storage is selected in the platform backup schedule. | Select storage in the schedule settings. |
5164 | Failed to open platform backup file | Failed to open the platform backup file. | Check the presence and integrity of the file, if necessary, select another file, repeat the operation. |
5165 | Failed to start platform backup process | Failed to start platform recovery from backup. | Check the presence and integrity of the file, if necessary, select another file, repeat the operation. |
5166 | Bad cron expression | Cron record error. | Check the cron record format in the schedule settings. |
5167 | Request to service ipmgr failed | Failed to execute a request in IPmanager. | If integration with an external IPmanager is configured, check the availability of the external IPmanager. |
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. | |
5170 | VM per node limit exceeded | The number of VMs on the node exceeds the limit. | Increase the available number of VMs in the node settings. |
5171 | Live migration from newer to older libvirt version not allowed | Live migration with these libvirt versions is not supported. | Perform migration with VM shutdown. |
5172 | Host is still creating | VM is still being created. | Wait for VM creation. |
5173 | Host is in relocation failed state | VM is still migrating. | Wait for the migration to complete. |
5174 | Bridge already paired with the host interface | VM is already connected to the selected bridge. | Select another bridge. |
5178 | Node network settings already locked | The node's network configuration is locked for changes. | Wait for the node configuration to change. |
5179 | Iface/Bond can't be paired with more than one Vlanless bridge | The interface can only be connected to one bridge without VLAN. | Disconnect the interface from the connected bridge and reconnect to the required bridge. |
5181 | Node already have default bridge | The default bridge already exists. | Uncheck the "Default bridge for new VM" option for the default bridge and set it for the desired bridge. |
5182 | Invalid slave interface for bridge | The selected interface cannot be included in the bridge. | Select another interface. |
5183 | Interface already included to another bond/bridge | The selected interface is already included in a bond or bridge. | Disconnect the interface from the bond/bridge or select another interface. |
5184 | Cannot remove the default node bridge | Impossible to delete the default bridge. | Disable the "Default bridge for new VM" option for the default bridge. |
5185 | Some iface/bond/bridge has already used this name | The selected interface name is already in use. | Select another interface name. |
5190 | Bridge/Bond name matches a reserved pattern | This interface name is reserved and cannot be used. | Select another interface name. |
5195 | Cluster doesn't have any pools | IP address pools are not connected to the cluster. | Connect pools to the cluster. |
5196 | Invalid vxlan network | Invalid VxLAN. | Select another VxLAN. |
5197 | IP is already allocated in panel | IP address is reserved. | Select another IP address. |
5198 | IP address not found | IP address not found. | Check the correctness of the IP address selection. |
5199 | Create ptr record failed | Failed to create PTR record. | Check the DNSmanager 6 integration settings and DNS server availability. |
5200 | Update ptr record failed | Failed to update PTR record. | Check the DNSmanager 6 integration settings and DNS server availability. |
5201 | Delete ptr record failed | Failed to delete PTR record. | Check the DNSmanager 6 integration settings and DNS server availability. |
5202 | PTR with the same IP already exists | A PTR record for this IP address exists. | Delete the PTR record in DNSmanager 6. |
5203 | Specified disk is not linked with the specified host | The selected disk is not connected to the selected VM. | Connect the disk to the VM. |
5206 | Disk limit for the specified bus type has been reached | The number of disks for the selected connection type has been exceeded. | Select another connection type. |
5207 | Cannot unlink last host disk | Impossible to disconnect the only disk from the VM. | Connect an additional disk, make it the main one and disconnect the required disk. |
5209 | Specified host is not on the specified node | Cannot change the prefix of the IPv6 address block allocated for VMs, there are used IPv6 addresses. | Release busy IPv6 addresses. |
5210 | Cannot remove disk which linked to host | Cannot disconnect a disk that is not connected to the VM. | Check the correctness of the disk selection. |
5211 | Cannot unlink main host disk | Impossible to disconnect the main disk from the VM. | Connect an additional disk, make it the main one and disconnect the required disk. |
5212 | Disk already linked with host | The disk is already connected to the VM. | Check the correctness of the disk selection. |
5213 | Blocked for host with mounted ISO | Unavailable for a VM with a connected ISO image. | Disconnect the ISO image. |
5214 | Host and disk have to locate on the same node | VM and disk must be located on the same node. | Select one node for the VM and disk. |
5215 | Disk and host have to belong the same account | The VM and disk must have the same owner. | Select one owner for the VM and disk. |
5216 | Linked disk cannot migrate between nodes | The connected disk cannot be migrated between nodes. | Disconnect the disk from the VM. |
5217 | Migration destination is equal to source | The destination node coincides with the source node. | Select another destination node. |
5218 | Node has dependent host backups | The node has dependent VM backups. | Delete dependent backups. |
5219 | Node already exists | A node with this name already exists. | Select another node name. |
5224 | Suitable storage is not found | No suitable storage found. | Check the status of storages, if necessary, connect additional storage. |
5225 | Can not migrate between clusters with different datacenter type | Impossible to migrate VMs between clusters with different network setting types. | Select a cluster with an identical network setting type. |
5227 | Can not migrate host with vxlan between clusters with Full Mesh vxlan mode | Impossible to migrate VM with VxLAN between clusters with full mesh. | Change the cluster configuration or select another cluster. |
5228 | Can not migrate host with vxlan between clusters with different vxlan mode | Impossible to migrate VM with VXLAN between clusters with different virtual network types. | Change the cluster configuration or select another cluster. |
5231 | Several interfaces are not supported for the datacenter with the routing network model | For the "Routing" network setting type, nodes with two interfaces are not supported. | Use one node interface when connecting. |
5233 | Task registration error | The task cannot be registered. | Repeat the operation that caused the error. If the error occurs again, contact technical support. |
5236 | Node has libvirt errors | Problems with libvirt daemon on a cluster node. | Check libvirt using the instructions in the Basic diagnostics article. |
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. |
| |
Given IP does not belong to any IP-pool assigned to cluster | An error can occur when:
| Use an IP address from a pool that belongs to the cluster. | |
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. | |
5302 | Invalid network mask | Invalid network mask. | Check the correctness of the network mask input. |
5303 | No suitable network | No suitable network. | Add a network with the required parameters. |
5305 | IP busy | IP address is busy. | Select another IP address. |
5306 | Not enough free IP in selected pools | No free addresses. | Add an IP address pool. |
License expired | License expired. | Check the license expiration date. If the license is valid, activate it. | |
5309 | Empty license | License data is missing. | Check the license status. |
5310 | Invalid license | License data is corrupted. | Re-activate the license. |
5314 | Image Limit Exceeded | The limit on the number of images has been reached. | Delete unused images. |
5315 | License file expired | License data has expired. | Check the license status. |
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. | |
5320 | New disk size incorrect | Incorrect new disk size. | Specify the correct disk size. |
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. | |
5322 | Image limit exceeded for host | The number of available images for this VM has been exceeded. | Delete unused images. |
Host is crashed | VM is crashed. | Examine the actions that led to the damage to the VM. | |
5339 | Ippool has used IP | Impossible to delete the pool, there are used IP addresses. | Release used IP addresses. |
5342 | Empty params for run recipe | Empty parameters for running the script. | Specify the required parameters to run. |
5343 | Not enough CPU in node | Not enough CPU on the node. | Reduce the number of vCPUs consumed by the VM, or delete unused VMs. |
5344 | Not enough free RAM in node | Not enough RAM on the node. | Reduce the amount of RAM in VM resources, delete unused VMs or increase the amount of RAM on the node. |
5345 | The network exists but the gateway does not match | The network exists, but the gateway does not match. | Specify the correct gateway for the network. |
5349 | Can not connect with node | No connection to the virtualization node. | Check access to the virtualization node from the platform server. |
5350 | Could not delete running task | Only deferred tasks or those in the queue can be deleted. | Wait for the task to complete. |
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. | |
5353 | KVM virtualization support is disabled in BIOS settings | Hardware virtualization support is disabled in BIOS. | Check virtualization settings in the virtualization node's BIOS/UEFI. |
Сan not get node info | Unable to get cluster node information. | Check the connection to the cluster node via SSH. | |
5355 | Such a hostname is already used for another node in the cluster | A node with this name already exists. | Select another node name. |
5356 | Can not migrate hosts from different clusters | Bulk migration for VMs from different clusters is not possible. | Perform VM migration from each cluster in turn. |
5359 | Can not add the node with active SELinux | Impossible to connect a node on which SELinux is running. | Disable the SELinux service on the virtualization node, repeat adding the node. |
5360 | Can not add the node with SELinux enabled in /etc/selinux/config | Impossible to connect a node on which SELinux is not disabled in the /etc/selinux/config file. | Disable the SELinux service in the /etc/selinux/config file on the virtualization node, repeat adding the node. |
Release data unavailable | No access to Changelog messages. | Check access to the Changelog files. If the platform uses a proxy server, check its settings. | |
5362 | Disk too small for selected OS | Insufficient disk size specified for the selected OS. | Increase the VM disk size. |
5363 | Disk too small for selected image | Insufficient disk size specified for the selected VM image. | Increase the VM disk size. |
5364 | No email params in license | The license does not contain information about default email settings. | Check the license status. |
Unsupported operating system on node | An unsupported OS is installed on the connecting cluster node. | Install a supported OS and reconnect the node. | |
5375 | Week day is not set for weekly schedule | No day of the week is selected to run the schedule. | Select a day of the week. |
5376 | Month day is not set for monthly schedule | No day of the month is selected to run the schedule. | Select a day of the month. |
5377 | Hosts or clusters are not set for schedule | VMs or clusters are not selected in the schedule. | Select VMs or clusters. |
5366 | Connection timeout | Failed to connect to the node. | Check access to the virtualization node from the platform server. |
5371 | VM is in rescue mode | VM is in recovery mode. | Disable recovery mode. |
5378 | Start time is not set for schedule | No start time is selected in the schedule. | Select a start time. |
5379 | VM is unavailable | VM is unavailable. | Check the VM status. |
5382 | vCPU number is not set | The number of vCPUs is not specified. | Specify the number of vCPUs. |
5383 | RAM is not set | The amount of RAM is not specified. | Specify the amount of RAM. |
5384 | Disk size is not set | The disk size is not specified. | Specify the disk size. |
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. | |
5389 | Invalid resource value | Invalid resource value. | Specify a valid value. |
5391 | Recipe param must have a value | No value is specified for the script parameter. | Specify the parameter value. |
5392 | Unsupported preset of vm on cluster | Unsupported VM configuration in the cluster. | Select a supported configuration. |
5394 | No recipient were provided | No recipient of the script execution notification is specified. | Specify the notification recipient. |
5395 | Recipient doesn't have language | No language for the script execution notification recipient is specified. | Specify the recipient's language. |
5396 | Recipient doesn't have email | No email for the script execution notification recipient is specified. | Specify the recipient's email. |
5397 | No template was found for specified language | There is no notification template for the selected language. | Select another language or create a template. |
5403 | LVM is not tuned | LVM software is not installed. | Install LVM software in the cluster storage. |
5404 | LVM volume group is not set | LVM volume group not found. | Create a volume group in the LVM software settings. |
5405 | Not found suitable LVM volume group in several VGs | No volume group with a suitable name was found. | Specify a name for one of the volume groups that matches the storage settings. |
5406 | Not found LVM volume group with suitable name | No volume group with a suitable name was found. | Specify a name for one of the volume groups that matches the storage settings. |
5408 | Vm storage path not set | VM storage path not found. | Specify the storage path. |
5409 | Volume group name not set | Volume group not specified. | Specify the volume group in the cluster settings. |
5410 | OS storage path not set | Storage for OS templates is not specified. | Specify storage for OS templates. |
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. | |
5504 | Cpu overselling set lower then 0.5. Try to increase overselling over 0.5 | CPU overselling is below the allowable level. | Set the overselling value to at least 0.5. |
5904 | Main storage not found on cluster | Main storage is not connected to the cluster. | Select one of the storages as the main one. |
5906 | Storage not found on destination node | No storages found on the destination node. | Select another destination node. |
5907 | VM storage path is a required parameter for File storage | For file storage, it is necessary to specify the VM storage directory. | Specify the VM storage directory. |
5908 | Volume group is a required parameter for LVM storage | For LVM, you need to specify a volume group. | Specify a volume group. |
5910 | RBD pool name is a required parameter for Ceph storage | For Ceph, you need to specify the RBD pool name. | Specify the RBD pool name. |
5911 | RBD user is a required parameter for Ceph storage | For Ceph, you need to specify the RBD user. | Specify the RBD user. |
5912 | Storage params is a required parameter for Ceph storage | For Ceph, you need to specify storage settings. | Specify storage settings. |
5913 | IP address is a required parameter for Ceph storage | For Ceph, you need to specify an IP address. | Specify the storage IP address. |
5914 | SSH port is a required parameter for Ceph storage | For Ceph, you need to specify the SSH port. | Specify the storage SSH port. |
5915 | Storage is disabled on cluster | Storage is disabled in the cluster. | Enable storage. |
5916 | Main storage is disabled on cluster | Main storage is disabled in the cluster. | Enable main storage. |
5918 | Cluster does not has storages | Storages are not connected to the cluster. | Connect storages to the cluster. |
5920 | Storage with same params is already attached to cluster | Storage with these parameters is already connected to the cluster. | Check the parameters of the connecting storage. |
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. | |
5922 | Neither ceph nor cephadm utils are not found on the server | Necessary software is not installed in the Ceph storage. | Install the necessary software and configure the storage. |
5923 | Repository with the same name already exists | A repository with this name already exists. | Change the name of the connecting repository. |
5924 | Repository with the same URL already exists | A repository with this URL already exists. | Change the URL of the connecting repository. |
5925 | Failed to get repository metadata | Failed to get repository metadata. | Check the correctness and availability of metadata in the repository. |
Repository metadata validation failed | Incorrect repository description file metadata.json. | Correct the repository description file. | |
5931 | Disk path is a required parameter for Network LVM storage | For Network LVM, you need to specify the disk path. | Specify the disk path. |
5933 | Storage does not support HA cluster | The selected storage type is not supported in an HA cluster. | Select a supported storage type. |
5936 | HA is disabled on cluster | Failover is disabled in the cluster. | Enable failover in the cluster settings. |
5939 | Can not delete node. HA has minimum node count | In an HA cluster, the minimum allowable number of nodes. Impossible to delete a node from an HA cluster.. | Add nodes to the HA cluster before deleting the target node. |
5943 | Range contains in network with empty gateway | No gateway is specified for the IP address range. | Specify the gateway. |
5944 | IP-pool contains network with empty gateway | No gateway is specified for the IP address pool. | Specify the gateway. |
5945 | Default bridge on node not found | Default bridge not found. | Assign one of the interfaces as the default bridge. |
5947 | Cannot delete vxlan if it has allocated IPs | Impossible to delete VxLAN with used IP addresses. | Release busy IP addresses, repeat VxLAN deletion. |
5948 | VxLAN feature disabled on cluster | VxLAN usage is disabled in the cluster. | Set the "Enable virtual networks" option in the cluster settings. |
5951 | Vxlan settings is not set | VxLAN settings are not specified. | Specify VxLAN settings. |
5958 | License token not found | License token not found. | Reactivate the license. |
5959 | Update license failed | License update failed. | Check the license status, reactivate the license. |
5960 | Activate license packet failed | License package activation failed. | Check the license package status, reactivate the package. |
5963 | License packet is already activated. If activated license packet is not listed in settings, try to update license | The license package is already activated. | Reactivate the license, check the package status, reactivate the package. |
5964 | Cannot find node with matching host filter params | Failed to find a node with matching filter parameters. | Change filter parameters. |
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. | |
5972 | Portstart is greater than portend | The start port of the range is greater than the end port. | Change the range settings. |
5973 | Filter expression validation failed | The filter value is specified incorrectly. | Specify the correct filter value. |
5975 | Host params doesn't match with recipe filters | VM parameters do not match the specified filter. | Change filter conditions. |
Ip automation not available | Error can occur when changing the IP address addition model or creating a VM image. |
| |
Qemu guest agent is not available on host |
|
| |
5997 | ISO check timeout is exceeded | ISO image check time exceeded. | Check the integrity of the image file, repeat the download. |
6001 | SPICE is disabled on cluster | SPICE is disabled in the cluster. | Allow SPICE connections in the cluster settings. |
6002 | SPICE is failed on node | Failed to enable SPICE on the virtualization node. | Check the node status. |
6005 | SPICE is disabled on host | SPICE is disabled on the VM. | Allow SPICE connections in the VM settings. |
Operation is blocked. Node is in maintenance mode | Attempting to perform an operation on a node that is in maintenance mode. | Wait for the end of the maintenance mode. | |
Failed to switch the node to maintenance mode | Failed to switch the node to maintenance mode. | Check if there are restrictions that prevent you from switching the node to maintenance mode. | |
Maintenance is in bad state for this handler | The cluster node cannot enter or exit maintenance mode. | Wait for the end of operations that prevent the node from changing state. | |
6022 | Only NAS storage is supported for current operation | The operation will only be available when selecting NAS storage. | Select NAS storage for the operation. |
6023 | Only local storage is supported for current operation | Copying and migration are not available for an image created in NAS storage. | Select local storage for copying or migration. |
6024 | Only same NAS storage is supported for current operation | The operation will only be available when selecting NAS storage in which the VM image was created.. | Select NAS storage with the VM image. |
6026 | Nas storage path is a required parameter for Nas storage | The "Path to directory on the nodes" parameter is not specified.. | Specify the parameter value. |
6027 | EFI boot can be set only for NoOS | The OS bootloader cannot be started. | Create a VM without an OS to run the bootloader. |
6029 | Only unique NAS storage path can use | The value of the "Path to directory on the nodes" field must be unique. | Specify a unique parameter value. |
6052 | Unsupported linked-clone main disk storage type | Unsupported storage type for a linked clone operation. | Select file or NAS storage. |
6054 | The image is used by linked-clone | Impossible to delete the VM image due to created linked clones. | Delete the linked clones created based on this image, and repeat the operation. |
6056 | Linked-clone inter cluster migration not available | Linked clone migration between clusters is prohibited. | Perform migration without changing the cluster. |
User already exists | A user with this email already exists. |
| |
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. | |
Host limit exceeded | The license limit for the number of virtual machines has been exceeded. | Increase your license limit or delete some VMs. | |
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. | |
Getting license from server error | Licensing service error. | Examine the licensing service logs. |
Errors list
The article was last updated on 08.06.2025. The article was prepared by technical writers of ISPsystem