Virtuozzo

Virtuozzo is a software virtualisation platform that utilises a shared core operating system between all containers on a physical node. As such, containers are not updated individually but rather the node as a whole is upgraded.

From here you can Start, Stop or Restart the Container, take full server backups, set the Firewall or see Resource Alerts. These tools work best on Linux servers.

Container Rebuild process

The process of rebuilding your container effectively restores it to original settings, erasing all data in the process. If you choose to go ahead with this course of action, I advise you take and ensure you have sufficient relevant backups to restore domains/setting/websites after the rebuild.

Alternatively if you rebuild your VPS you can place specifically requested data in a /old directory however this is not guaranteed and as such confirm you have backups of your data and/or confirm you understand the backup to /old is not infallible and could still lead to data loss.

Maintenance Backups

These are stored off of your VPS onto the physical server/node and are an exact copy of your entire file structure.

A tip for Virtuozzo is if you have accidentally deleted a domain but have got an old backup, take a new backup now.
Then, restore the server from the old backup from when you still had the domain created.
Next, backup your data via FTP or a Plesk backup and save this content to your PC.
Afterwards, restore the new backup you just took, recreate the domain you lost and restore the FTP or Plesk backup to the domain.

Maintenance area not available

If you get this error:

Application Error
The server has encountered an internal error or misconfiguration.
Contact your support representative.

Please report this problem to the technical support

Log into the server and run:

/etc/init.d/sw-cp-server restart

iptables rules needed

Please ensure that you have the following rules in your firewall:

iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables-save

Otherwise pinging and apt commands may not work.

Resource Alerts (Logs)

SLM Memory Limit means you have hit or gone over your allocated RAM into Burstable RAM.

The Container Management > Resources should provide you an accurate display of your disk space. You can navigate from the root directory of the server using File Manager.

Quota UGID Limit

This can mean you have either hit your inode usage or the amount of user/groups you have is too much.

quotaugidlimit is unlikely to cause any performance issues on the container, the values that Virtuozzo sees compared to what is showing within /etc/passwd and /etc/group can differ for a few different reasons, such as:

• if you delete a registered user but some files with their ID continue residing inside your Container, the current number of ugids (user and group identities) inside the Container will not decrease.
• if you copy an archive containing files with user and group IDs not registered inside your Container, the number of ugids inside the Container will increase by the number of these new IDs.

Look at the container to see if it is hitting it's memory limit regularly. This will impact performance, checking power panel should confirm this. Check how much memory the apache process is currently sitting on, as there may not be not much wiggle room there for other processes.

• This is a user/group limit, it's a limit on *tracking* resource usage, not on resource usage itself. If you transfer files from another system which uses different UIDs or GIDs not present on this system then the quota tracking will attempt to track resource usage for these new IDs. Have a look through the vhosts to see if you can find any vast quantities of "foreign" file ownership, but if the ownership has been changed the quota tracking would still be in place for the old IDs.

Notes

• The root password for your server can normally be set in here using the Change Password link.
• Container Services > System Services will normally show incorrect reports for what is running. For a proper check, use SSH or the Container Services > System Processes