OpenVZ VPS does not start after migration in SolusVM: Failed to create ploop on root@203.0.113.2

Have more questions? Submit a request

Applicable to:

  • SolusVM

Symptoms 

  • OpenVZ VPS does not start after migration in SolusVM
  • The following error is displayed in the migration log /usr/local/solusvm/log/xxx_migration.log(the exact file name is displayed on the migration page in SolusVM) on destination node:

    CONFIG_TEXT: 1043666: Failed to create ploop on root@203.0.113.2

Cause

DISKSPACE directive is missing in the configuration file of the VPS on the source node.

Resolution

  1. Connect to Source node via SSH
  2. Open the file /etc/vz/conf/CTID.conf in any text editor and add the directive:

    CONFIG_TEXT: DISKSPACE="<size:size>"

    where CTID is actual CT ID of the VPS and <size:size> is the diskspace allocated to VPS in format <softlimit:hardlimit> in kilobytes.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.