Other Possible Issues

This article provides recommendations for troubleshooting possible issues with virtual servers. Here you will find instructions for trying to solve problems on your own and for collecting the diagnostic information that will help us resolve the issue faster.

Disk size did not increase

In most cases, partitions are expanded automatically after the disk size is increased. The exception is when you have changed the disk layout yourself and created two or more logical partitions.

In this case, you need to repartition the disk manually by following our guide.

If the problem persists after these steps, run the following commands (as root) for diagnostics:

df -h

fdisk -l

The first command shows the sizes of your partitions, and the second lists the existing partitions and disks.

When you open a support ticket, attach the output of these commands, and our specialists will carry out the necessary diagnostics.

Depending on the information you provide, fixing the problem may require shutting down the server for 15-20 minutes. Let us know which time window works for you.

RAM size did not increase

If you notice that the actual amount of RAM has not increased after a RAM upgrade, open a support ticket and attach the output of the following command (run as root):

free -m

This command shows RAM usage in megabytes.

Depending on the information you provide, fixing the problem may require shutting down the server for 15-20 minutes. Let us know when such a shutdown would be convenient for you.

The operating system does not boot

To fix an operating system boot problem, boot into recovery mode from the boot disk, and then switch back to normal mode.

If the problem is still not solved, contact us for diagnostics.

The server is unstable and freezes

Most often, this behavior is caused by high load. Check the load graphs in the control panel and, if you see any spikes, take steps to reduce the load. You can also analyze server load with the top or htop utilities.

If there are no signs of excessive load, contact us for further diagnostics.

The site is still unavailable after a server reboot

If your site is still unavailable after a server reboot and you see an error message such as "This site can't be reached. The connection was reset", the cause may be a kernel panic, a critical error in the operating system kernel. In this case, you may also notice that you cannot do anything in the server console through the control panel.

To fix this, reboot the server and then click the "Force reboot" button. This restarts the virtual machine and brings it back to working order.