Plesk 12.5 for Linux
# service sw-engine start /usr/sbin/sw-engine-fpm: error while loading shared libraries: libxmlrpc_cpp.so.4: cannot open shared object file: No such file or directory
3. Library libxmlrpc_cpp.so.4 is missing from the server:
# ls -l /usr/lib64/libxmlrpc_cpp.so.4* #
# rpm -qa | grep xmlrpc xmlrpc-c-1.16.24-1210.1840.el6.x86_64 xmlrpc-c-1.16.24-1210.1840.el6.i686 plesk-php70-xmlrpc-7.0.9-centos6.16072211.x86_64 xmlrpc-c-c++-1.16.24-1210.1840.el6.i686
Missing libxmlrpc_cpp.so.4 library.
# wget ftp://fr2.rpmfind.net/linux/centos/6.8/os/x86_64/Packages/xmlrpc -c-c++-1.16.24-1210.1840.el6.x86_64.rpm
# rpm -ivh xmlrpc-c-c++-1.16.24-1210.1840.el6.x86_64.rpm
# service sw-engine start
How to install Plesk additional components (like Backup Manager, PHP etc.) with autoinstaller?
Plesk Control panel->tools and Settings->Updates and Upgrades button. Please make sure that port 8447 is opened. It is used by autoinstaller, please refer to this article for information at (Updates and Upgrades page cannot be opened: it just loads continuously I have already written).
Login to the server by SSH and launch autoinstaller:
Just follow instruction on the screen and you will be able to install additional components.
Block Storage and Object Storage are two methods of data storage. Let’s see in detail what it is and what services they offer.
It is very important to understand what the Block storage and Object storage is as they play a key role when it comes to optimizing the use of Cloud services, particularly in storage and the creation of local infrastructure projects. See below what it is in the detail.
The block storage is a storage type of data used in environments of Storage Area Network (SAN), which provides data storage volumes in those blocks. Each block is configured as a single hard disk and is configured as a single hard disk and is configured by the administrator. These blocks are controlled by the operating system and are generally called by the Fibre Channel (FC), Fibre Channel over Ethernet (FCoE) or iSCSI protocols.
Because volumes are treated individually as hard drives, the Block Storage works well by storing a variety of applications such as file systems and databases. While storage devices tend to be complex and expensive, the Block Storage tends to be more flexible and provides better performance.
The block storage devices offer a storage capacity fixed. Each volume can be treated as an independent disk drives controlled by an external source. This device can be mounted by the host operating system as if it were a physical disk. The most common examples of Block Storage are San, iSCSI and local disks. They system of Block Storage is the one most commonly used for most applications and can be local or via the network. The devices are usually formatted with a file system FAT32, NTFS, EXT3 and EXT4.
The block storage is ideal for databases as they require high I/O performance and low latency connections feature. It can be used for RAID volumes where multiple disks are combined. Each application that needs processing as Java, PHP and .Net need of Block Storage, ditto for critical applications such as Oracle, SAP, Microsoft Exchange and Microsoft SharePoint.
The object storage is a tool for archiving data between cloud computing.
Object storage and block storage represent the two storage services in the cloud. Above we focused on the Block storage; we have seen how it works and what the solutions available in the Cloud are. Now, we will focus, instead, on the object storage.
The Object Storage is an architecture that manages the data as objects, in contrasts to other storage architecture like file system, which provides the management of data according to a hierarchy of files treated as blocks within individual sectors. Each Object typically includes the data, a variable amount of metadata and a globally unique identifier. The Objet Storage can be implemented in multiple levels and includes the device level, the system level and the interface level.
The data held on devices Object Storage can be accesses directly through the API or http/https, can store any type of data, photos, videos and log files. This type of storage ensures that data is not lost. Data stored in this way can be replicated across multiple data centers and offer simple interface for Web access.
A simple to use the Object Storage may be represented by the use of service as a means of storage for developers who work with large quantities of media and need unlimited storage. The Object Storage, in fact, become gradually more and more attractive as soon as the data to be archived increased dramatically, as happens to with eNlight Cloud Services that allow users to upload media files (especially video).
Storage of unstructured data such as music, pictures and video, but also backup, database dump and log files are the most common cases of use of the Object Storage.
Today, we will see two performance models in eNlight Cloud, these two different models means that you can choose an option that going to be most suiting to your requirements.
In eNlight each performance model is based around the way that cache memory and RAM are used (Read More: How many types of Cache do you know?). Cache memory can be seen as being an extension to RAM, which is primarily used by computers to access information more quickly that can be done so from disk.
Under some circumstances the cache memory can grow unhealthily large and the result of this is that a majority of the RAM ends up being reserved for cache purposes; this is the main design of most Linux distributions because it improves the execution speeds of certain commands that have been executed previously.
The amount of RAM that is used for the purpose of cache memory can have huge implications on the performance of a Virtual Machine. The two performance levels that we offer so that you are able to fully enjoy the high levels of performance that eNlight offers are:
There are certain scaling limitations for you to be aware of:
Auto-scalability is one of the flagship features of eNlight Cloud is designed to provide Cloud Virtual Machines with additional resources when their base specifications begin to get exhausted under the loads that they are placed under.
With eNlight the computing resources that you’ve allocated to your Cloud VMs can be automatically increased when the performance of the VM could be called into question, with CPU and RAM being two examples of resources that can be managed in this way. So that you don’t end up with any unexpected huge bills, limits can be placed on the level to which resources are automatically scaled so that you don’t go over your budget.
The best thing about auto-scaling from eNlight is that all of this is done without the need to reboot the VM so not downtime is ever incurred! The platform is one of the most intelligent around and when it detects that a VM is in need of extra power, more resources will be pulled from the central pool that all VMs in the Cloud take their power from. As auto-scaling responds automatically to demand, you will only be billed for periods of high-usage, as the specifications of your VMs will return to their pre-determined level once the load decreases.
Resources are scaled up and down by eNlight as a percentage of resource consumption patterns. Scaling is done steadily, but is also fast and effective at the same time, as is the scaling down. As the scaling down is performed, the resources allocated originally are moved off your VMs and allocated elsewhere, often during off-peak hours as this is when demand is going to be at its lowest. This has proven to be popular because it means that businesses using eNlight are truly only ever paying for what they are using and ensures that redundant resources aren’t costing them money.
Although disk scaling isn’t available in eNlight Cloud, but we do offer a feature known as Elastic Storage that means you can add multiple disks to a single VM. These disks can be attached and detached on the fly and between VMs, without any data loss. This is why we believe that eNlight is one of the best options available options available for Disaster Recovery hosting.
Stay tuned, as we will discuss Performance Models in eNlight Cloud next week!