Mix Installation for other Linux based systems

From JonDonym Wiki
Revision as of 14:25, 12 July 2018 by Rolf (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

En2.png De2.png    <- prev | Content | next ->


HowTo install the mix server software for Linux

This HowTo describes the installation of the mix server and related software for RedHat Linux. For Debian and Ubuntu servers JonDos GmbH provides packages to simplify the installation. See: Mix Installation (Debian and Ubuntu).

The software for mix servers is distributed as source code.


In order to compile the mix sources the libraries OpenSSL (at least v.0.9.7) and Xerces-C++ are required. Additionally a C++ compiler, make, automake, autoconf and subversion are required, too. You can install all that stuff with the package manager of your operating system.

RedHat:  yum install g++ make automake libssl-devel libxerces-c2-devel subversion

For premium mixes PostgreSQL database server, client and C-libraries for PostgreSQL clients are required, too.

RedHat:  yum install postgresql postgresql-client libpq-devel

Checkout the source code

Checkout the latest stable version from our subversion repository. We recommend the use of the directory /home/mix for sources.

mkdir /home/mix
cd /home/mix

svn checkout https://svn.jondos.de/svn/proxytest/proxytest/branches/stable

Note you should now use this code here in revision 6700 (version 00.11.14):

svn checkout https://svn.jondos.de/svn/proxytest/proxytest/trunk/
svn up -r 6700

Compile and install using make (version 1)

You can compile and install the mix software using make. Please enable the required compile options for your mix:

cd /home/mix/stable
./configure --enable-payment ...
make install

Compile and install using rc-scripts (version 2)

The mix source code contains a maintenace script and parameter file in misc/Linux/rc-scripts for simplify installation and software updates. First copy the files to their default destinations:

cd /home/mix/stable
cp misc/Linux/rc-scripts/etc_default_mix /etc/default/mix
cp misc/Linux/rc-scripts/etc_init.d_mix /etc/init.d/mix

Edit the settings in /etc/default/mix to fit your preferences. Very important: choose the correct compile options for your mix. Two examples are prepared: one for free mixes and one for premium mixes.

# compile optins for free mixes

Afterwards you can compile and install the mix:

/etc/init.d/mix compile
/etc/init.d/mix install

Enable additional features

Depending on the features needed by your mix, you can enable some more features for your mix with COMPILE_OPTIONS:

 ./configure --enable-payment .... ....

Mandatory feature for premium services:

  • --enable-payment Specifies to build with payment support.

Mandatory for free mixes:

  • --enable-with-integrity-check security feature

Mandatory feature for free entry mixes:

  • --enable-user-bandwidth-limitation Specifies to build with with bandwidth limitation. The limitation parameters can be specified in the mix configuration file. (only free entry mixes)
  • --enable-with-integrity-check Enables the new integrity check security protocol.

Monitoring your mix:

  • --enable-server_monitoring Specifies to build with state tracking for server monitoring. You can specify a monitor port in the mix configuration (it is normally port 8080) and fetch a XML file from this IP:port time by time to check your mix. A plug-in for Nagios, which is using the monitoring port, will be found in the mix source tree misc.

Disable infoservice threads:

  • --enable-infoservice-no-threads Do not use threads for communication with infoservices. You use this feature in case of problems with infoservice communication.

Additional Logging features:

  • --enable-crime-detection Enable crime detection mode. Crime detection parameters can be specified in the mix configuration file. Do ONLY use it, if you are under constraint by authorities and law. For working properly, all mixes of a cascade have to enable this feature.
  • --enable-dataretentionlog Enable log messages according to data retention law.

Create a system user account

It is not a good solution to run the mix server with root privileges. Create a new system user account (recommended name: mix) and specify this user account in the mix configuration file. After startup, the mix server will switch to this UID.

Create a system user account with useradd:

adduser --quiet --system --disabled-password --shell=/bin/false --group mix

Create a log directory

The directory and file for log messages will be specified in the mix configuration file. You have to create the directory and set safe permissions:

mkdir /var/log/mix
chown mix:adm /var/log/mix
chmod 0750 /var/log/mix

No logrotate configuration is necessary. The mix server creates a new file, if the log file size exceeds the configured limit.

Start the mix server

You have to create a mix configuration, save the config in /etc/mix/config.xml and start or stop the mix:

start:  /etc/init.d/mix start
stop:   /etc/init.d/mix stop

Alternativly you can raise the number of max. open descriptors to the value specified in the mix configuration file and you can start the mix at command line:

start:   ulimit -SHn 32768
         mix -c /path/to/config.xml
stop:    killall mix

After startup the mix server will switch to the sytem UID specified in the mix configuration file.

Update the mix software using rc-scripts

Like other software the mix is updated time by time. New features will be added, bugs will be fixed ... and so on. Join the operator mailing list to stay up-to-date about software updates. If an update is announced, run the following steps.

/etc/init.d/mix upgrade
/etc/init.d/mix restart

The update creates a backup of the old mix binary in $SOURCE_PATH/backup. If you were run in trouble with the new version, you can restore the old version by:

/etc/init.d/mix restore
/etc/init.d/mix restart

Update the mix software by hand

Alternatively you can update the mix by hand. You have to know the compile options.

cd /home/mix/stable
make distclean
svn update
./configure --enable-server_monitoring --enable-payment .... ....
make install

After successful update restart the mix.

Personal tools