The control panel registers many common problems, fixes them and tracks their current statuses. Navigate to System Status → Notifications.
Click on Log to view the detailed information.
Click on Parameters to view the additional information about a certain error.
Click on Resolve to make the system try to resolve the issue automatically. The button is available only if the automatic solution is supported.
Notification settings
Click on Settings to enable the notifications:
- Keep old notifications (days) - information about notifications that did not occur during a selected period will be deleted automatically;
- Keep resolved issues (days) - information about issues that were resolved this number of days ago, will be deleted automatically;
- Show user notifications - select the checkbox to display users' notifications;
- Send Email notifications - select the checkbox to send error notifications to the selected mailbox;
- SMTP-server - enter the SMTP server for sending notifications;
- SMTP-server port - enter an SMTP port for sending notifications;
- Email for notifications;
- Sent from;
- Notification message language.
Issues registered in VMmanager:
- An error occurred when importing a VM;
- The maximum execution time specified in the temple has been exceeded when installing the operating system on the virtual machine. Make sure there are no issues with the cluster node;
- VMmanager cannot connect to vemini on the node. Possible causes: incorrect configuration of ihttpd on the cluster node (check the IP address and port in the file etc/ihttpd.conf), or the core process on the cluster node doesn't respond, you need to restart it;
- The maximum execution time specified in the temple has been exceeded when requesting the configuration file by OS installer on the virtual machine. Make sure there are no issues with the cluster node;
- An error occurred when executing the recipe:
- no IP addresses are assigned to the virtual machine;
- error connecting to a virtual machine via SSH;
- failed to execute the recipe;
- execution method is not supported;
- internal error.
- The recipe on the virtual machine has reached the timeout;
- An error occurred while trying to connect via ssh to the cluster node;
- VMmanager KVM detected a replication error of the main database on the node;
- The virtual machine has been successfully recovered from the snapshot;
- Backup recovery was running while trying to start the migration of the virtual machine. The operation was terminated ;
- Error restoring an IP address;
- Cannot restore the container IP address;
- Backup is prohibited during VM migration;
- An attempt to start the backup process during installation/ reinstallation;
- Backup is prohibited during VM installation or reinstallation;
- VM snapshot has been made successfully;
- Failed to make a VM snapshot;
- An error occurred when trying to connect libvirt to the cluster node;
- Error accessing the NFS storage on the cluster node;
- Creating a TCP-filter;
- An error occurred when libvirt was trying to create a filter on the cluster node;
- The storage does not exist on the cluster node. Cannot create virtual machines that use this node;
- An error occurred while getting information from the storage on the node. If you run the network storage, check connection;
- The node is out of the cluster. All cloud services on it are stopped;
- MySQL replication has been stopped. Restore replication to ensure cluster stability;
- Failed to recover the virtual machine when recovering the cluster node. One or several disks of the virtual machine are located in the local storage. ;
- An error occurred when migrating the virtual machine between the nodes;
- An error occurred when rolling back migration of the virtual machine from one node to the other. Perhaps this VM is already running on another node or there are redundant virtual disks on the node;
- The virtual machine is not present on the node. Perhaps this VM is running on another node;
- Error adding the IP address;
- Cannot add the IP address when importing the virtual machine;
- A critical error occurred during OS template synchronization;
- The system failed to start the virtual machine. The virtual machine was suspended. Perhaps, its disk was damaged, or has insufficient space;
- On the cluster node:
- the package manager returned the error when updating the packages;
- an error occurred when updating the network filter;
- an error occurred during synchronization of files;
- an error occurred when updating the Firewall rules;
- a fatal error occurred during the update;
- an unknown error occurred during the update ;
- Service monitoring error:
- vmwatch-node is not running on the master server;
- could not start vmwatch-master on the master server;
- the vmwatch-node service is not running on the node;
- could not start vmwatch-node in the cluster node;
- critical error.
Issues registered in COREmanager
VMmanager is based on COREmanager. The following issues and events are also registered in the control panel:
- Errors occurred while making a backup copy based on the backup plan;
- Non-critical errors occurred while making a backup copy based on the backup plan;
- Backup completed successfully;
- Errors occurred while restoring the backup copy;
- Non-critical errors occurred while restoring the backup copy;
- Backup restore has been completed successfully;
- The backup and recovery functions modified the behavior, that's why we have deleted the information about previous backups;
- The user has requested data export in CSV;
- The user has requested deletion of personal data;
- The user has requested obliteration/limitation of usage of personal data;
- Error executing a command via cron;
- Error managing the secondary DNS server;
- failed to delete the domain;
- failed to update the domain information;
- failed to create a domain;
- domain has invalid serial. Perhaps, your DNS server processes domain update queries too slow;
- The plug-in failed or returned invalid XML ;
- Authentication token has not been added;
- An error occurred while unassigning the IP address;
- Error allocating IP address. Reason;
- No available IP addresses in IPmanager;
- An error occurred in IPmanager while allocating the IP address;
- IPmanager returned an empty address;
- the IP address does not correspond to the selected version of IP addresses;
- you have insufficient permissions for allocating the selected IP address or it is already assigned;
- no available IP addresses of the specified type in the subnet;
- The operation was terminated. The cause of the error:
- executable file not found;
- script of the service not found;
- Failed to locate the configuration file;
- Failed to create the user database for;
- failed to locate a path to the database directory;
- failed to locate a path to the file;
- the application not found;
- an error occurred while creating the MySQL user;
- operating system not supported;
- software not supported;
- software not available;
- application name is not specified in the installer parameters;
- failed to complete the operation;
- failed to locate the path to domain zone directory;
- failed to change the owner;
- failed to change access privileges;
- Failed to get information about the file/directory;
- failed to locate the socket file;
- Failed to start the MySQL server with the --skip-grant-tables parameter;
- failed to change the MySQL administrator password;
- Failed to start the service;
- Failed to connect to the server;
- the object is missing in the storage;
- configuration file has an invalid format ;
- an error occurred when registering the application;
- an error occurred when updating the application;
- an error occurred when deleting the application;
- no information about the current version of the application;
- fstab has an invalid format;
- Failed to define the mount point for the directory ;
- an error occurred when writing the parameter;
- failed to start (restart) the application;
- Path to is not specified in the configuration file;
- failed to define name or group of web-server's internal users;
- the control panel requires software product;
- the software product cannot be deleted as it will delete depended packages;
- A fatal error occurred in the module while installing the software. The installation process is not completed;
- A fatal error occurred in the module while configuring the software. The installation process is not completed;
- A fatal error occurred in the module while completing configuration. For more information consult the installer log;
- A fatal error occurred in the module when deleting the software. The process is not completed;
- Executable file is missing;
- Install the cron package to be able to use the scheduler;
- A critical error occurred during OS template synchronization;
- An error occurred when signing the DNSSEC domain. Recent changes were canceled. For more details see zonesigner;
- An error occurred when re-signing the DNSSEC domain. Recent changes were canceled. For more details see zonesigner.