Stuck with SolusVM error : ‘command not found’? We can help you.

Here at Bobcares, we handle requests from our customers to fix similar errors as a part of our Server Management Services.

Today we will see how our Support Engineers fix this for our customers.

SolusVM error : ‘command not found’

Usually, while starting SolusVM OpenVZ VPS you may see the error “command not found”.

What causes ‘command not found’ error?

• Excessive whitespaces in DISTRIBUTION declaration in the VPS config file /etc/vz/conf/101.conf:
  DISTRIBUTION = “debian”
• libvirt packages are not installed on the KVM node.

How to resolve it?

Today, let us discuss each case and see the fix the provided by our Support Techs.

Whitespaces in DISTRIBUTION declaration

Typical error might look as below when to try to restart manually:

# vzctl restart 101
<…>
/etc/vz/conf/101.conf: line 56: DISTRIBUTION: command not found

Resolution:

• Firstly, connect to OpenVZ node via SSH
• Then, modify the VPS config file /etc/vz/conf/101.conf by changing the following line:

DISTRIBUTION = “debian”

to

DISTRIBUTION=”debian”

libvirt packages are not installed

Unable to start KVM VPS. When rebooting the VPS at SolusVM > Virtual Servers > VPS > Reboot(Debug) you will see the below error:

sh: virsh: command not found
sh: virsh: command not found

Resolution

• Firstly, connect to KVM node via SSH
• Then, install the missing packages with the command:

# yum install libvirt libvirt-client libvirt-python libvirt-bash-completion

• Finally, enable and start libvirtd service:

# systemctl enable libvirtd
# systemctl start libvirtd

[Need assistance with SolusVM error?We can help you]

Conclusion

In short, today we saw how our Support Techs resolved SolusVM error : ‘command not found’.