linux

Proxmox 3.x to Proxmox 4.x

Share this
I have a very simple Proxmox setup at home. No cluster (anymore), but I did have to convert from 3.x to 4.x to keep current. This means going from OpenVZ to LXC. In reality they are very similar, but it's more or less like changing out the hood on the car (from a sysadmin perspective). The basic theory behind the conversion is not to upgrade the current machine in place, but to do a side-by-side or blue/green deployment in order to retain any information about the old guest VMs and containers as well as keep a back out plan.

Tags: 

Drupal Error 500 With A Correct Server Configuration in VirtualMin

Share this
This past week I migrated some sites that were originally on their own server to a cloud server running VirtualMin. After migrating the sites, everything seemed to be in place including the MySQL database, files, DNS, etc. However, I kept getting a 500 Internal Server Error when loading the site. To fix this, I had to change options in the .htaccess file for both the main site and the files directory (sites/default/files): Change Options +FollowSymLinks to # Options +FollowSymLinks Options +SymLinksIfOwnerMatch

Tags: 

Installing ViMP Part 3: Installing ViMP

Share this

These steps are mostly taken from the ViMP FAQ, with modifications from where I stumbled. I had originally tried to make this one long document, but to avoid a wall of text and getting lost in the middle, I've split it out into three parts: Installing the Web Server, Installing the Transcoding Tools, and Installing ViMP.

Notes:

  • This how-to assumes that you have already installed Ubuntu Server 12.04 LTS, have SSH enabled in order to remotely manage the server, and have followed Part 1 of this tutorial
  • I prefer to use nano as my text editor, because it's stupid simple. Ctrl+W is for search, Ctrl+X is for close/save.
  • I run these commands as sudo. Use sudo su in order to drop into permanent sudo mode.

Installing the Transcoding Tools

  1. First and foremost, you'll have to download the ViMP installer and move it to your server with a program such as FileZilla. Because the download is behind a login, you won't be able to do a wget to download. I recommend putting the download in your home folder and launching the installer from there. I had problems when I uploaded it to the recommended location, /var/www/.
  2. Once ViMP is loaded on the server, make it executable:

    chmod +x vimp.framework---installer.bin

  3. Start the install script:

    ./.framework---installer.bin

Tags: 

Installing ViMP Part 1: Installing the Web Host

Share this

These steps are mostly taken from the ViMP FAQ, with modifications from where I stumbled. I had originally tried to make this one long document, but to avoid a wall of text and getting lost in the middle, I've split it out into three parts: Installing the Web Server, Installing the Transcoding Tools, and Installing ViMP.

This how-to assumes that you have already installed Ubuntu Server 12.04 LTS and have SSH enabled in order to remotely manage the server. When setting up the server there is no need to do the LAMP install package, as the steps below will effectively take care of that.

Also note that I prefer to use nano as my text editor, because it's stupid simple. Ctrl+W is for search, Ctrl+X is for close/save.

Installing the Web Server Packages

  1. First we need to install the basic Apache and MySQL packages:

    apt-get update
    apt-get install apache2 php5 php5-gd php5-mysql mysql-server mysql-client php5-cli php5-mcrypt php5-xsl php5-curl php5-gmp php5-json libjpeg62 libjpeg62-dev ruby

  2. Install a MTA (Mail Transfer Agent) for sending emails to users and admins:

    apt-get install sendmail-bin sendmail

  3. We need to modify the default Apache configuration to point to the correct folder for the ViMP install. The web-facing part of the ViMP install is located in the /web subfolder of wherever you install ViMP, so I chose to install ViMP to /var/www/vimp/ and point the Apache config to /var/www/vimp/web/.

    nano /etc/apache2/sites-available/default.conf

    Note: This may be /etc/apache2/sites-available/000-default.conf
    Replace the entire file with the following text:

    <VirtualHost *:80>
    # ServerAdmin webmaster@localhost
    # ServerName mydomain.tld

Tags: 

Pages

Subscribe to RSS - linux