General

The MAP project, does not recommend the installation package from Murmur. Since the MAP project starts (mid 2009, so Murmur 1.1.6) we have already installed the server Murmur on several servers. In most cases, the problems on the Package installation were due. We recommend going directly to the right away, namely the installation of the Static installation.

Package installation

Of course, the package installation possible and leads in 90% of the installations, the desired result, however, is not so easy to handle as the installation of a Static Murmur package. In general, the package installation seems to be faster and easier, but in conjunction with the setup of this is only the illusory shining! However, more information on installing packages you can find here.

Fedora

Arch Linux

Static installation

Step by step

Download

The newest / latest released Murmur server download can either be downloaded from the official Sourceforge page of the Mumble project, or on the MAP project page.

Ressource: Sourceforge

The download is found in the sub folders below: Download. It is recommended to always take the most recent stable version. Usually included in the download is called like this: murmur-static_x86-x.x.x.tar.bz2.

Ressource: Mumb1e.de

It is easier to follow this resource, because we always have the latest and most compatible version to the latest MAP version available:
Download. Furthermore, MAP in each release to ../Server/OS/ you can find the latest static version.

Extract

To unpack the Murmur server is for example the 7-Zip File Manager very well on Windows operating systems.
On Linux operating systems meet the following lines to the packed package to unpack:

Create database

As a rule, on a server or VPS or a machine accessible via the Internet an application to install a MySQL server to manage. For Murmur it is not absolutely necessary to use a MySQL database, because MySQL needs, however, MAP is the use of MySQL for near Murmur. Murmur is also a separate file that is located in the same directory as the server, users manage their data. This is according to developers and the fastest way or Murmur has the best performance with this type of database. This file is in the murmur.ini and have to be defined not by the .sql or .sqlite! Here's an example:

database=murmur.sqlite

The MySQL database e.g. Murmur can be created using phpMyAdmin or Webmin and its users are created with permissions. If these applications can not be installed a database created from the shell:

mysql> CREATE DATABASE databasename;

Create user

A very important step is to create a separate UNIX user for the Murmur server process. This is one of the most important steps in the correct installation of the Murmur server. This may for example in the shell

adduser murmur

be entered by the user to create murmur. Last you need now only in themurmur.ini to define the user just created

uname=murmur

Edit murmur.ini

The most important step is to edit the configuration file of the Murmur Severs, the murmur.ini. Detailed explanations and examples for each variable, see our wiki at murmur.ini. But the most important variables are: database, dbXXXXXX, ice, icesecretread, icesecretwrite, logfile, port, host und uname. Of course, the other values ​​are important too!

Upload

The Murmur of the already extracted files server can now be uploaded to an FTP program. We recommend using Windows WinSCP. Please note that the server should be operated in a protected directory for security reasons. Although it is eigenlich matter and would work everywhere, but we recommend the server eg to operate in the following folders:

/home/murmur/
/home/USER/murmur/
/root/murmur/
/srv/murmur/

Also recommend that, after the upload of MAP, the server does not operate in the MAP directory, since they would be otherwise after all probability in a publicly accessible directory and thus everybody could access the server. The following directories so we have to avoid for the server:

Create murmur.log

In order to start the server when Murmur and during operation and stores its messages, especially error messages, it requires the file murmur.log.
This command has the following in the shell in the directory that contains the Murmur server, run:

touch murmur.log

The murmur.log is important to find fault with the installation. We arrive at the point Check back to this file.

CHMOD permissions

Thus, the Murmur server can be started successfully in the final step must now have the file permissions. To execute in the server the following command:

chmod 775 murmur.x86 murmur.log murmur.pid

Start server

And now the server will start with:

./murmur.x86

or

sh murmur.x86

Check

After starting the server fatal error that stops the trigger straight back of Severs are usually directly after the dücken the ENTER key in the shell shown. In addition, they are written in the murmur.log. Other errors, such as a non-functioning installation slice is stored only in the murmur.log. This is of course very important for the operation of the Mumb1e Admin Plugin. Therefore, after the first start of the Murmur server always take a look at the murmur.log important:

vim murmur.log

Should there be to find inexplicable errors, Mumb1e.de support helps you: Support.