Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Unable to find ostemplate – Let us fix the SolusVM error

by | Jun 5, 2021

Stuck with the SolusVM error, Unable to find ostemplate? We can help you.

We may come across this error when we try to reinstall OpenVZ VPS on the SolusVM localhost node.

As part of our Server Management Services, we assist our customers with several SolusVM queries.

Today, let us see how to fix this error.


Unable to find ostemplate

Recently, while one of our customers tried reinstalling OpenVZ VPS on SolusVM localhost node, he came across the error, “Unable to find ostemplate”

The major symptoms of the error include:

  • Unable to reinstall a container on localhost in Virtual Servers > VPS > Reinstall
  • We can find the below error in /var/log/vzctl.log:
Opening delta /vz/private/VEID/root.hdd/root.hds
vzctl : CT VEID : Error: Unable to find ostemplate: 1
vzctl : CT VEID : Destroying Container private area: /vz/private/VEID
vzctl : CT VEID : The ploop image /vz/private/VEID/root.hdd has been successfully unregistered
  • If we attempt to enter this container, the following error occurs:
# vzctl enter 101
enter into CT 101 failed
Unable to open pty: No such file or directory
  • It is possible to reinstall a new VPS using the Client area:

Unable to find ostemplate

The cause of this error can be the Bug #SVM-1831 that is planned to fix in future SolusVM versions.

In order to fix this, our Support Techs suggest the below steps.

However, until the fix becomes available, we can use the native reinstall tool:

  1. We connect to the SolusVM Master via SSH
  2. Then we stop the container
    # vzctl stop CTID
  3. Re-install OS
    # vzctl reinstall <CTID> –ostemplate <template_name>

Here, we replace <CTID> with the actual VPS CT ID, and <template_name> with the template name without the “.tar.gz” part.

Suppose, the container was already reinstalled from the SolusVM Admin area. In such a case, the only solution is to completely remove the container and create a new one.


Unable to create OpenVZ VPS in SolusVM

Apart from the error above, we may also notice the error “Unable to get appcache tarball name” while creating OpenVZ VPS in SolusVM.

The symptoms of this can be as follows:

  • Unable to create an OpenVZ VPS in SolusVM – VPS stays offline.
  • In /var/log/vzctl.log we can see the error:
    vzctl: CT 101: Unable to get appcache tarball name for ve-vswap-solus.conf-sample with ostemplate centos-6-x86_64-minimal
  • The /var/log/vztt.log shows the below error:
    Error: package_manager file for centos-6-x86_64 EZ os template should be filled

The cause of this error can be a necessary package missing.

In order to fix this, our Support Techs suggest:

  1. Initially, we connect to the slave server over SSH.
  2. Then we install the template and vzpkg packages:
    # yum install vzpkg* centos-6-x86_64-ez -y
  3. Eventually, we update the package_manager file:
    # echo “rpm47x64” > /vz/template/centos/6/x86_64/config/os/default/package_manager

[Couldn’t fix the error? We can help you]



In short, we saw how our Support Techs fix the SolusVM error for our customers.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.