Natenoms Wiki

Weil Teilen Spaß macht :)




Installation of Mumble Moderator

The installation of MuMo is a bit tricky …

This howto is outdated, please try to use the German one, which I updated in 2020. I will later try to update this English version as well :)

See Installation von MuMo (MumbleModerator)


  • Debian 6 or later; in the section „Configure Mumble Moderator“ and later the system is not relevant anymore.
  • A Mumble server should be installed on the same system and should be accessible through Ice; see also Install a Mumble-Server (German).



One needs root permissions for the following steps:

Packets (on a Debian Squeeze or later):

  • python-zeroc-ice – Python-Bindings, to be able to use Ice
  • git-core – We need this to get the latest version of Mumble Moderator
  • python-daemon – Needed if MuMo should run as a daemon

Install all packages with:

apt-get install git-core python-zeroc-ice python-daemon

Create a new user:

adduser mumo

Get Mumble Moderator

Now login as the new user:

su - mumo

And clone the project files from MuMo:

git clone

All files are now in the directory 'mumo'.

Configure Mumble Moderator

Change to the new directory:

cd mumo

Here you can edit the file mumo.ini, see next section.

slice variable

If you are using a Mumble-Server >= 1.2.4 then you don't need to setup the 'slice = ' variable, Mumble Moderator will get the file from the server automatically.

If your server is older than 1.2.4 then you must point slice = to the correct path. On Debian this file is located in '/usr/share/slice/ after the installation of the package 'mumble-server'.

If you did not use the Debian package to install the Mumble server copy the file from your own package to /usr/share/slice/ and add that path to the slice variable:

slice = /usr/share/slice/'


If your server uses an icesecretwrite you must add this to the mumo.ini.

secret = yourpassword


Create a new directory named modules-enabled:

mkdir modules-enabled

Now change into the created directory and link all *.ini files of modules that should be active, for example:

cd modules-enabled && ln -s ../modules-available/seen.ini && cd -


This is an example of a complete mumo.ini, click to show the content:


; Host and port of the Ice interface on
; the target Murmur server.

host =
port = 6502

; Slicefile to use (e.g. /etc/slice/, 
; if empty MuMo will load the slice file from the
; target server at startup.

slice = 

; Semicolon seperated list of slice include directories
; to consider. This is only used on legacy platforms
; with old or broken Ice versions.
slicedirs = /usr/share/slice;/usr/share/Ice/slice

; Shared secret between the MuMo and the Murmur
; server. For security reason you should always
; use a shared secret.

secret =

;Check Ice connection every x seconds

watchdog = 15

; Comma seperated list of server ids to listen on (empty for all)
; note that if a server isn't listed here no events for it can
; be received in any module
servers = 

mod_dir = modules/
cfg_dir = modules-enabled/
timeout = 2

pidfile =

; Logging configuration
; Available loglevels: 10 = DEBUG (default) | 20 = INFO | 30 = WARNING | 40 = ERROR

level =
file = mumo.log

Ice.ThreadPool.Server.Size = 5

This is the directory structure of a full MuMo installation.

This is the directory structure of a full MuMo installation.

|-- modules
|   |--
|   |-- antirec.pyc
|   |--
|   |--
|   |-- deaftoafk.pyc
|   |--
|   |-- idlemove.pyc
|   |--
|   |-- onjoin.pyc
|   |--
|   |-- seen.pyc
|   |--
|   |-- test.pyc
|   |--
|   `-- wrongversion.pyc
|-- modules-available
|   |-- antirec.ini
|   |-- bf2.ini
|   |-- deaftoafk.ini
|   |-- idlemove.ini
|   |-- onjoin.ini
|   |-- seen.ini
|   |-- test.ini
|   `-- wrongversion.ini
|-- modules-enabled
|   |-- antirec.ini -> ../modules-available/antirec.ini
|   |-- deaftoafk.ini -> ../modules-available/deaftoafk.ini
|   |-- seen.ini -> ../modules-available/seen.ini
|   `-- wrongversion.ini -> ../modules-available/wrongversion.ini

Start MuMo

Now you can start your Mumble Moderator:

python -a

Thats it :)

Close it with Ctrl + c.

Run Mumble Moderator as a system daemon

You can choose between:

  • Init script (recommended)
  • Start it by hand

Use an init script

In this section you must work with root permissions or with sudo on Ubuntu. The init script can be downloaded from the Mumble Moderator repository:

Copy it to /etc/init.d/mumo Now you must change the wordir in the script from




Make it executable chmod a+x /etc/init.d/mumo

Now add it to the runlevel:

update-rc.d mumo defaults

On the next system start Mumble Moderator starts automatically; to start it without a system restart, execute

service mumo start

Start Mumble Moderator by hand

You need to start Mumble Moderator with the parameter -d to let it fork to the background.

python -d



When Mumble Moderator does not start as a daemon and the log contains:

Traceback (most recent call last):
File “”, line 535, in
File “/usr/lib/pymodules/python2.7/daemon/”, line 352, in __enter__
File “/usr/lib/pymodules/python2.7/daemon/”, line 344, in open
File “/usr/lib/pymodules/python2.7/”, line 223, in __enter__
File “/usr/lib/pymodules/python2.7/daemon/”, line 109, in acquire
super(TimeoutPIDLockFile, self).acquire(timeout, *args, **kwargs)
File “/usr/lib/pymodules/python2.7/daemon/”, line 59, in acquire
super(PIDLockFile, self).acquire(*args, **kwargs)
File “/usr/lib/pymodules/python2.7/”, line 261, in acquire
raise LockTimeout

Remove the file to solve this.

See also

en/mumble/tools/mumo/mumo-installation.txt · Zuletzt geändert: 2022/10/27 14:21 von

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

Dieses Wiki wurde archiviert und wird nicht mehr gepflegt. Mein neues Wiki gibt es auf Details auf der Startseite.