If you see error like below in “Auto FTP backup” feature

/usr/local/solusvm/tmp/ftpbackup.pid already exists. Is backup already runing?

 

Just delete the file /usr/local/solusvm/tmp/ftpbackup.pid and the SolusVM backup will run fine.

rm -rf /usr/local/solusvm/tmp/ftpbackup.pid

Advertisements

Run this command on solusvm master node.

/usr/bin/php /usr/local/solusvm/includes/autoftpbackup.php –debug=1

Moving the SolusVM Master

1. Preparing the New Master

Install a new master server as explained in the Install Guide.

2. Backing up the Original Database

You can backup your original SolusVM master database by entering the admin area and selecting System Tools > Database and clicking Send to Email or by downloading it directly.

3. Replacing the Encryption Key

Parts of your database are encoded using a unique encryption key stored in /usr/local/solusvm/includes/solusvm.conf. You need to make a copy of the encryption key on the original master and replace it on the new master.

The format of the solusvm.conf is as follows:

example: <DATABASENAME>:<USER>:<PASSWORD>:<HOST>:<the key is the last entry>

Icon

If you miss this step, non of your passwords or slave connections will work.

4. Restoring the Database

Upload the database backup to the new master server.

You can get the new database details from /usr/local/solusvm/includes/solusvm.conf, they are seperated with  ” :”.

example: <DATABASENAME>:<USER>:<PASSWORD>:<HOST>:<the key is the last entry>

Run this code in SSH on the new master to restore the database:

/usr/bin/mysql --user=USER --password=PASSWORD DATABASENAME < database.sql

If you change the IP of the master, you might need to reissue the license in solusvm.

5. Slave Configuration

Each slave in your cluster needs to know the new masters ip address (only if the masters ip is changed).

On each slave add the ip of your master to /usr/local/solusvm/data/allow.dat OR delete /usr/local/solusvm/data/allow.dat so it can be re-written.

6. OS Templates

Don’t forget to FTP, RSYNC etc. your OS templates to the new master.

 

Source: https://documentation.solusvm.com/display/DOCS/Moving+the+SolusVM+Master

Change to Standard Web Ports

** This method will not work if you have any other services running on standard web ports, such as Apache, as SolusVM will be unable to bind to the needed ports.

Many users prefer to have SolusVM running on the standard web browsing ports such as port 80 for http and 443 for https. This enables users behind firewalls that block non-standard ports, like the ports SolusVM uses, to access the control panel.

1. Backup the lighttpd configuration file in case of process failure:

cp /etc/lighttpd/lighttpd.conf /etc/lighttpd/lighttpd.conf.bak

2. Open the lighttpd configuration file in the editor:

nano /etc/lighttpd/lighttpd.conf

3. Scroll to the bottom of the file to find the server section. It will look the following way:

server.port                = 5656 server.pid-file            = "/var/run/lighttpd.pid" server.username            = "solusvm" server.groupname           = "solusvm"  $SERVER["socket"] == "0.0.0.0:5656"{  ssl.engine = "enable"  ssl.pemfile = "/usr/local/solusvm/ssl/cert.pem"  }

4. Change the following sections to reflect the new ports (note the port changes):

server.port                = 80 server.pid-file            = "/var/run/lighttpd.pid" server.username            = "solusvm" server.groupname           = "solusvm"  $SERVER["socket"] == "0.0.0.0:443"{  ssl.engine = "enable"  ssl.pemfile = "/usr/local/solusvm/ssl/cert.pem"  }

5. Add the section below to the END of your lighttpd.conf file to ensure your SolusVM Master can still communicate with your slave nodes:

$SERVER["socket"] == "0.0.0.0:5656"{ server.document-root = "/usr/local/solusvm/www/" ssl.engine = "enable" ssl.pemfile = "/usr/local/solusvm/ssl/cert.pem" }

6. Save your new lighttpd.conf file and then restart lighttpd to access it on standard ports:

service lighttpd restart

You can now access your SolusVM Control panel using standard web ports:http://[ip_address]/ and https://[ip_address]/. You will still be able to access the original port too https://[ip_address]:5656/

 

Source: https://documentation.solusvm.com/display/DOCS/Change+to+Standard+Web+Ports

yum install system-config-network-tui
system-config-network

To fix Windows 10 cannot do left click at start button.

Right click at Start button > select Command Prompt (Admin) > type powershell > press Enter > wait a bit until you see….
PS C:\windows\system32>

At the flashing prompt, copy and paste this( please use Copy and paste to avoid typo)

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml“}

> press Enter.

Ignore any error in red.

When finished, try Start button again.

Good luck

To install cPanel & WHM on your server, run the following command:

cd /home && curl -o latest -L https://securedownloads.cpanel.net/latest && sh latest

 

WHMxtra Install Instructions
Installation notes: Please ensure the following prior to running any installer:

1. Run the below command:

rm -rf xtra.sh;rm -rf cpx.sh;rm -rf pro.sh;rm -rf basic.sh;rm -rf xlite.sh

This will remove any old installer files laying around.

2. Turn off any firewall you may be using, or the installer may not be able to connect to our server to retrieve the proper files.

3. Run the following command to install

Install: wget http://whmxtra.com/pro/pro.sh;sh pro.sh

 

Attracta’s Powerful Tools to Your Customers
wget -N http://www.attracta.com/static/download/cpanel-install
sh cpanel-install

While managing DirectAdmin server  you might sometime want to change the php handler to suphp instead of default mod_php. Because suphp provides better protection to server than mod_php because it runs the php scripts under the user account instead of default user apache. DirectAdmin custombuild provides a very easy way to do it.

cd /usr/local/directadmin/custombuild/
./build set php5_cgi yes
./build set php5_cli no
./build set ioncube yes
./build all d
./build rewrite_confs

Note: If you just want to upgrade PHP
./build set php5_ver 5.5
./build update
./build php n

service httpd restart

Note: If you just want to build ioncube
cd /usr/local/directadmin/custombuild
./build update
./build ioncube
./build php-ini
service httpd restart

Now after suphp is installed on the server. You will need to fix phpMyAdmin, Roundcube and squirrelmail

./build roundcube
./build squirrelmail
./build phpmyadmin

No you can fix the permissions of all the files and folders of the users.

for i in `/bin/ls /usr/local/directadmin/data/users/` ; do chown -R $i.$i /home/$i/domains/* ; echo $i ;done
for i in `/bin/ls /usr/local/directadmin/data/users/` ; do find /home/$i/domains/ -type f -exec chmod 644 {} \; ; echo $i ;done
for i in `/bin/ls /usr/local/directadmin/data/users/` ; do find /home/$i/domains/ -type d -exec chmod 755 {} \; ; echo $i ;done

Source: http://servermanagementplus.com/linux-server-support/install-suphp-directadmin-using-custombuild

Useful link: http://forum.directadmin.com/showthread.php?t=29824

vzctl stop 1100

vzquota drop 1100

vzctl start 1100

While starting VE with VEID 200 quota will be recalculated

Purpose

In our base CentOS 6.3 image it uses a few endpoints in the EPEL repos that are set by default that use SSL 3.0. Due to this you will receive the error noted below when attempting to use yum update from the instance. This article will show you how to remedy that while we work on deploying an updated CentOS 6.x image.

 

Loaded plugins: fastestmirror, security
Determining fastest mirrors
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again.

Notes

We will update this knowledge base article once we have an updated and fixed CentOS 6.x image.

The CentOS 5.8 and CentOS 7 images available to use don’t have this issue.

Walkthrough Steps

Running this command will update the repo to use HTTP rather than HTTPS:

sudo sed -i "s/mirrorlist=https/mirrorlist=http/" /etc/yum.repos.d/epel.repo

You should then be able to update with this command:

yum -y update


Source: https://community.hpcloud.com/article/centos-63-instance-giving-cannot-retrieve-metalink-repository-epel-error