Ubuntu Server 14.04 (Trusty Tahr) – Zentyal 3.5 Installation


Zentyal Server is an open source Linux small business server, that can act as a Gateway, Infrastructure Manager, Unified Threat Manager, Office Server, Unified Communication Server or a combination of the above.

I am performing this setup on a minimal virtual machine installation of Ubuntu Server 14.04. At the time of writing Zentyal 3.5 is the most current Zentyal release.

First make sure that repositories and software are up to date:

sudo apt-get update
sudo apt-get upgrade

Add the Zentyal 3.5 repository to /etc/apt/sources.list:

echo "deb http://archive.zentyal.org/zentyal 3.5 main extra" | sudo tee -a /etc/apt/sources.list

Import public keys for Zentyal 3.5:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 10E239FF
wget -q http://keys.zentyal.org/zentyal-3.5-archive.asc -O- | sudo apt-key add -

Update repositories:

sudo apt-get update

Install Zentyal:

sudo apt-get install zentyal
  • When prompted enter a password for the MySQL root user.
  • Confirm port 443 as the Zentyal https port.

From here we simply setup Zentyal using the web-gui. Open Firefox (the only officially supported browser) and enter the url for your Zentyal install: https://zentyal-server-ip.

Confirm the security exception in Firefox and then log in to Zentyal using your Ubuntu Server credentials:

Zentyal - login

Ubuntu Server 14.04 (Trusty Tahr) – Quick MediaDrop Installation


MediaDrop is a open source online video platform for managing and delivering video, audio and podcasts.


Sadly I found the official documentation to be lacking and had to cross reference it with other install guides to even get a basic setup running.

This guide will take you through a basic installation of MediaDrop that utilizes the built in Paste Server provided by Python. If you prefer a more permanent solution you can setup an Apache 2 or Nginx web server yourself. For the time being I am happy enough to just have MediaDrop running – having experienced a couple of bugs I do not want to mess with my working configuration any further right now.

My working environment is a minimal installation of Ubuntu 14.04 Server on VMware vSphere 5.x.

Let’s begin our installation – first we will elevate ourselves to the root user and then install MySQL, System libraries, development headers, python libraries and tools:

sudo -i

apt-get install mysql-server mysql-client libjpeg-dev zlib1g-dev libfreetype6-dev libmysqlclient-dev python-dev python-setuptools python-virtualenv git

When prompted enter a password for the MySQL root user.

Setup Python virtual environment:

cd /

virtualenv --no-site-packages venv

Activate the virtual environment:

source venv/bin/activate

Install MediaDrop from Git:

git clone git://github.com/mediadrop/mediadrop.git mediadrop-git

Download and install all the necessary dependencies for MediaDrop into your virtual environment:

cd mediadrop-git

python setup.py develop

Generate the deployment.ini file:

paster make-config MediaDrop deployment.ini

We will now bring up a mysql> prompt to administer the MySQL database:

mysql -u root -p

Enter your MySQL password when prompted.

Create the MySQL database mediadrop_db and the MySQL user mediadrop_user and a password for mediadrop_user:

mysql> create database mediadrop_db;
mysql> grant usage on mediadrop_db.* to mediadrop_user@localhost identified by 'mysecretpassword';
mysql> grant all privileges on mediadrop_db.* to mediadrop_user@localhost;
mysql> exit;

Note: Change ‘mysecretpassword‘ to the password you want for mediadrop_user.

Edit the delpoyment.ini file:

nano deployment.ini

Under the [app:main] heading, look for the sqlalchemy.url setting:

sqlalchemy.url = mysql://username:pass@localhost/dbname?charset=utf8&use_unicode=0

Change the username, pass, and dbname entities to mediadrop_user, password and mediadrop_db:

Note: password here refers to the password that you designated earlier for mediadrop_user.

sqlalchemy.url = mysql://mediadrop_user:mysecretpassword@localhost/mediadrop_db?charset=utf8&use_unicode=0

Setup the built in server:

paster setup-app deployment.ini

Enable simple full text searching:

mysql -u root mediadrop_db < setup_triggers.sql -p

Enter your MySQL password when prompted.

Now that MediaDrop itself is installed and the basics are configured, we can test it out using the Paste server:

paster serve --reload deployment.ini

Open a browser and enter the ip address for your server using port 8080. For example – http://server-ip:8080

To access the admin dashboard you need to append /admin to the above url. The default administrative username is admin, and the password is also admin. Remember to change your password!

If you restart your server you will need to activate the virtual environment again and run the Paste server again. A basic script to handle this looks like this:

cd /
source venv/bin/activate
cd mediadrop-git
paster serve --reload deployment.ini

Save this as something like mediadrop-start.sh and then make it executable:

chmod +x mediadrop-start.sh

Run the script as follows:

sudo ./mediadrop-start.sh

As a closing note I did encounter issues accessing the admin panel after changing the admin password when using Firefox. I could access the admin panel using Internet Explorer though.




Installing Nexenta Core Platform 3.0.1 With Nappit on VMware vSphere 4.x

I have been mulling over what exactly the eventual replacement for my Windows Home Server might be one day – and Nexenta is something that I have been pondering for a while.

The Nexenta Core Platform (NCP) is what the commercial (and community) versions of Nexenta (NexentaStor) are built upon.

NCP is based on Ubuntu, with an OpenSolaris kernel. NexentaStor (Community) has a Web Management User Interface (WMUI) and an 18TB limit for storage. NCP has a community developed WMUI called Nappit.

I decided to look at installed NCP and Nappit to get a feel for NCP over NexentaStor Community edition as I have not decided yet on what amount of storage I might want to use Nexenta for. This is because my plan is to use mirroring to provide basic redundancy rather than other forms of RAID. For some storage pools I might use three mirrored drives together rather than two and so I can see this strategy eating into the 18TB limit of NexentaStor Community (although hopefully not too quickly). I guess I don’t want to feel limited with my next storage server.

I am still pondering the pros and cons of virtualizing NCP on VMware vSphere versus running two physical boxes but for now lets look at installing NCP in a vSphere virtual machine.

Note the following keys used during installation:

  • Up and Down arrow keys move the cursor up and down between input fields and check-boxes,
  • Spacebar marks your selection,
  • Tab cycles through the options,
  • Enter confirms your choice and proceeds to the next step.

First download the Nexenta .iso and copy it to your vSphere datastore.

Create a new virtual machine and specify the following Guest Operating System properties – Linux and Ubuntu (64-bit).

I configured 4Gb of RAM with the default LSI Logic Parallel SCSI controller with a 12GB vitrual hard disk.

Finally point the virtual CD-ROM of the virtual machine to the uploaded Nexenta .iso and boot the virtual machine.

Enter a password for root, then press the down arrow key and re-enter your password. Press tab to highlight the OK button and then press Enter.

Login as root (or login as other user, enter su to get root permission).

At this point I tried to install napp-it but discovered that I did not have an IP address. The fix was as follows:

svcadm disable svc:/network/physical:default
svcadm enable svc:/network/physical:nwam

I entered the following command to check that I had an IP address:

ifconfig -a

Now we can install the nappit web interface for Nexenta:

wget -O - www.napp-it.org/nappit | perl

Open your preferred browser and enter: http://<server-ip&gt;:81 to manage your Nexenta installation.


http://www.nexenta.org/boards/1/topics/1118, http://www.nexenta.org/projects/site/wiki/Difference



Ubuntu Server – Installing ResourceSpace Using Subversion


ResourceSpace is web-based, open source digital asset management system. It can handle photos, videos, audio and documents – and as you will see it has a great (and very flexible) user interface.

So let’s get started with installing ResourceSpace.

First update your repositories and install Apache2, PHP5, MySQL and other required packages (you will be prompted to create a password for your MySQL database):


sudo apt-get update
sudo apt-get install apache2 mysql-server php5 php5-dev 
php5-gd php5-mysql php5-svn subversion
sudo apt-get install nano graphicsmagick graphicsmagick-imagemagick-compat
sudo apt-get install ghostscript antiword xpdf ffmpeg postfix 
libimage-exiftool-perl cron wget

Note: you will also be prompted to configure postfix. I accepted the defaults for the postfix installation as I do not plan on emailing myself from ResourceSpace.

Change directory to /var/www/ and download ResourceSpace from Subversion:

cd /var/www
sudo svn co http://svn.montala.net/svn/resourcespace

Change directory to resourcespace and create and set permissions for the filestore folder:

cd resourcespace
sudo mkdir filestore
sudo chmod 777 filestore

Log in to MySQL as the root MySQL user and create a database called resourcespace:

mysql -u root -p
create database resourcespace;

Make the include folder in /var/www/resourcespace executable for all users:

sudo chmod -R 777 include

At this point you should be able to access ResourceSpace on your server but if you do you will see that there is some outstanding PHP configuration that needs to be done:

ResourceSpace - Installation Check

As you can see the Installation Check tells us that we need to change the memory_limit, post_max_size and upload_max parameters in php.ini:

cd /etc/php5/apache2/
sudo nano  php.ini

Change the memory_limit, post_max_size and upload_max parameters to values that reflect your anticipated usage. I set mine to 512M, 250M and 250M respectively.

Restart Apache:

sudo /etc/init.d/apache2 restart

Now we can open a browser and complete the setup of ResourceSpace as follows: http://<server-ip-address>/resourcespace

ResourceSpace - Database Configuration

Enter the MySQL password that you created during the installation of MySQL.

You will also need to amend to email fields. Simply change the @mysite to something appropriate for your environment.

All of the other fields that you will see on this page are preset so you can scroll to the bottom and click the Begin Installation button (unless you feel the need to change anything like the Application Name, for example).

ResourceSpace - Installation Complete

Installation is now complete and you will be able to log in to ResourceSpace:

ResourceSpace - Home

If you are going to be using ResourceSpace for uploading video I would recommend that you also install Medibuntu.

I ran the Installation check within my ResourceSpace install and found that Blocked browsing of ‘filestore’ directory failed with the following error:

FAIL: filestore folder appears to be browseable; remove ‘Indexes’ from Apache ‘Options’ list.

Obviously this is something that we need to fix:

sudo nano /etc/apache2/httpd.conf

Add the following and then save httpd.conf:

<Directory /var/www/resourcespace>
Options -Indexes
AllowOverride All
Order allow,deny
Allow from all

Restart Apache:

sudo /etc/init.d/apache2 restart

ResourceSpace is quite customizable and I recommend that you take a look at these two YouTube videos to familiarize yourself further:


ResourceSpace Wiki – Installing on Ubuntu Linux

ResourceSpace Wiki – Installation

Ubuntu Forums

Ubuntu 10.4 Lucid – Installing Shutter, Featurefull Screencapture Tool

Shutter is a feature rich open source application for capturing screenshots. Shutter will let you capture a selection, full desktop, window, menus and even whole webpages. It even has a built in editor for annotating captured screens with freehand lines, highlights, lines, arrows, boxes, elipses, text and more. It is as close to SnagIt as I have seen for an open source project – it even has built in plugins for image manipulation.

Installing Shutter on Ubuntu 10.4 (Lucid Lynx) is very straight-forward. Click Applications, then Accessories and then Terminal.

Next add a PPA (Personal Package Archive) for Shutter to your repositories with the following command:

sudo add-apt-repository ppa:shutter/ppa

Then update your apt-get sources so that your system knows about the Shutter PPA that we just added:

sudo apt-get update

Finally install Shutter:

sudo apt-get install shutter

Click Applications, Accessories and then Shutter to run the application.

Shutter is a great utility, now go install it!

For further information visit: http://shutter-project.org/

Free Antivirus for Windows Home Server – WHSClamAV

Installing anti-virus on my Windows Home Server (WHS) is something that I have been thinking about for a while. Even though all of my WHS clients run anti-virus software I still thought that it would be prudent to protect my WHS,  just in-case. I had planned to purchase Avast for WHS but with WHS version 2 (Vail) apparently due later this year I did not want to commit.

WHSClamAV is an open source project that is still under development, hence some of the functionality available in the GUI is not complete – for example, the scheduling and settings tabs, and the user defined scan do not work at the present time. Nevertheless WHSClamAV will scan memory, the system and data drives, or individual share folders from within the WHS console.

The installation of the WHSClamAV add-in is the same as any other add-in for WHS – simply download the .msi file to your WHS Software/Add-Ins folder and then install it via the WHS Console (Settings > Add-Ins > Available Add-Ins). I installed version 0.1.7.

In the WHS ClamAV add-in click the Install button.

ClamAV will then download and install.

The WHSClamAV interface is pretty self explanatory with Quarantine, Scan and Update being the main features available.

While WHSClamAV may not be as fully featured as a paid for anti-virus solution it offers additional peace of mind for free!

Installing Openfire Instant Messaging Server on Windows Home Server

AT&T’s recent incompetence regarding my DSL connection made me appreciate some things that I had begun to take for granted – like being able to IM my wife in another room.

Now that I am back on-line I decided to setup my own local Instant Messaging server on my Windows Home Server (WHS).

Let’s start by downloading Openfire.

On the Openfire download page click the Windows button and then download the .exe file that includes Java JRE. At the time of writing the current version of Openfire is 3.6.4.

Copy the file to your WHS and establish a remote connection to it , then run the Openfire executable.

Select a language for installation and then click OK.

Click Next and then accept the License Agreement and click Next again.

Click Next and change the install location to D:\Program Files\Openfire. Click Next.

Click Finish to run Openfire.

Click Unblock on the Windows Security Alert.

If you try to configure Openfire using Internet Explorer on your WHS it will not work.

I accessed the Openfire web-based setup using Firefox on one of my WHS clients with the IP address of my WHS using port 9090 as follows: http:\\ Simply replace this IP address with the IP address of your own WHS.

On setup screen select a language and click Continue.

The default Server Settings for Domain and Console ports should be fine so just click Continue again.

Assuming that you do not have a MySQL database already running on your WHS click the Embedded Database radio button and then click Continue.

For the Profile Settings leave default selected and click Continue.

Enter an email address and password for the Administrator Account – you do not have to use a real email address if you do not want to.

Setup is now complete and we should be able to log in to the Admin Console.

I found that I needed to stop and start Openfire on my WHS before I could login successfully. Note that the user-name to login with is admin.

Adding new users is very simple – just click Users/Groups and then Create New User. I created a user called ‘mike’.

It is advisable to run Openfire as a service on WHS (so that Openfire will start automatically if WHS is rebooted):

Download and install NTServiceInstaller and the Windows Resource Tools Kit and install them on WHS.

Run NTServiceInstaller and  configure as below (the Executable path is D:\Program Files\openfire\bin\openfire.exe):

Click Install.

Click Start then Run and type services.msc and then click OK.

Start the Openfire service.

I chose the above method (which I found on GeekPill) to run Openfire as a service because the official method did not work for me.

The first client that I tried was Gajim but I did not get on very well with it – it gave me an error message every time I quit it.

The client that I tried after that was Psi. Connecting Psi to my WHS Openfire server was straightforward as Psi asks you if you want to use an existing account when it runs for the first time. On the Account tab of the Psi account setup I entered my Jabber ID: mike@  (my Openfire user-name @ my WHS IP address) and the password for that account.

Under the Connection tab I checked the Manually Specify Server Host/Port checkbox and entered my WHS IP address. I left the port at its default setting.

I then setup Psi for my wife and authorized her account in my Psi client so that we could chat to each other. My only disappointment with Psi was that I had to change settings so that chat windows automatically popped up on the screen.

It would be nice if chat (amongst many other things) were included in WHS – but at least it can be achieved without too much effort …