Lik`s forum

How can we change a VPS servers resource plan after it has been created?

One thing that needs to be understood is the way resource plans are treated in FluidVM. A resource plan is not attached to VMs, rather it is attached to users. For example, you can create a user with a resource plan that allows for 2 VPSs, 40G memory and 120G storage. The user can now create up to 2 VMs and ...

My management server hardware crashed! How can I move FluidVM to another server?

The steps are simple:
1. Install the base OS
2. Install the latest version of FluidVM
3. Reboot
4. Update your copy by running "update_fluidvm.py" from the management node.
5. Stop management server (/etc/init.d/vkarma stop)
3. Copy the database from the old system to the new one. The file in question is /var/cache/vkarma/fluidvm_development.db
4. Copy all additional OS templates (OpenVZ and Xen) ...

What services must be run for FluidVM?

The physical machine hosting the FluidVM Management server typically runs the management server and the services for the FluidVM browser based interface. It does not have to be this way, depending on the load, it is possible to move the interface services to another system.

On the FluidVM Management server:

Code: Select all

/etc/init.d/vkarma

This is the main back-end server

Code: Select all

/etc/init.d/webkarma

This is the front-end core server

Code: Select all

/etc/init.d/nginx

This ...

From /var/log/vkservices.log on the compute node:
##########################
2009-08-07 12:12:54,917 471 INFO started
2009-08-07 12:12:57,543 471 ERROR stopping with an exception
Traceback (most recent call last):
File "./daemon.py", line 189, in start
File "./start-services.py", line 64, in run
File "./start-services.py", line 49, in start_server
File "./XMLRPCServer.py", line 154, in __init__
File "/usr/lib64/python2.4/DocXMLRPCServer.py", line 253, in __init__
SimpleXMLRPCServer.__init__(self, addr, requestHandler, logRequests)
File "/usr/lib64/python2.4/SimpleXMLRPCServer.py", line 473, in __init__
SocketServer.TCPServer.__init__(self, addr, requestHandler)
File "/usr/lib64/python2.4/SocketServer.py", line 330, in __init__
self.server_bind() ...

Which ports must be left open for FluidVM to work properly?

Management server API port - 8080
Web interface core port - 8282
Web interface web server port - 8086
FluidVM Agents (Running on the Compute Nodes) - 8181
VNC ports - 5900+

If the disk space occupied by the template after uncompressing is greater then 1G, the VPS will not get created. This is confirmed by FluidVM staff by creating a large template with lots of junk in it. All of the built-in profiles in FluidVM have this limitation, since they are based on "vps.basic" supplied by OpenVZ. However, fixing this is simple. On the compute node, delete all the configs that have "Guaranteed" in their name ...

Make OPENVZ templates visible in web interface

Once you have copied the templates across to /openvz-templates folder on the MANAGEMENT server you need to press the Sync Templates button in Virtual Cockpit->Templates-> (Top right and corner there should be a button).

Following lines should be added to ".htaccess":

Code: Select all

<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>

On FreeBSD server with cPanel control panel Exim restart lead us to the following errors:

Code: Select all

root# /scripts/restartsrv_exim
info [restartsrv_exim] BSD::Resource not available.  Resource Limits not adjusted
/libexec/ld-elf.so.1: Shared object "libperl.so" not found, required by "exim"
/libexec/ld-elf.so.1: Shared object "libperl.so" not found, required by "exim"
root#

This error may be caused by recent cpanel upgrade (upcp) and other 'perl-involved' maintenance on the server. First part of error message can be fixed by installing CPAN modules manually: ...

Add following line to ~/.bash_profile:

Code: Select all

echo -e 'ALERT - Root Shell Access on:\n' `who -m` '\n' `date` | mail -s "Successfull Root Login" [email protected]