This is a read-only archive of the Mumble forums.

This website archives and makes accessible historical state. It receives no updates or corrections. It is provided only to keep the information accessible as-is, under their old address.

For up-to-date information please refer to the Mumble website and its linked documentation and other resources. For support please refer to one of our other community/support channels.

Jump to content

Service not running after initial configuration?


Recommended Posts

Setting up a mumble server for the first time. I got it installed, configured the ini how I liked it and then opened ports, but for some reason it doesn't appear to be running correctly.

As you can see current date/time is 8:53

> date
Sat Mar  5 08:53:34 EST 2016


Restart of the service goes through fine

> sudo service mumble-server restart 


It appears to be running

> sudo service --status-all | grep mumble
[ + ]  mumble-server

But, when I look at my logs, nothing has happened since when I started having this issue about an hour ago. It seems to have caught a SIGTERM at some point and shut down, but I don't know why and no matter what I do, it won't start up again or generate new logs.

> sudo cat /var/log/mumble-server/mumble-server.log
<W>2016-03-05 07:51:30.240 Initializing settings from /etc/mumble-server.ini (basepath /etc)
<W>2016-03-05 07:51:30.241 OpenSSL: OpenSSL 1.0.2d 9 Jul 2015
<W>2016-03-05 07:51:30.464 ServerDB: Opened SQLite database /var/lib/mumble-server/mumble-server.sqlite
<W>2016-03-05 07:51:30.467 Generating new tables...
<W>2016-03-05 07:51:30.675 Murmur 1.2.8 (1.2.8-2ubuntu1) running on X11: Ubuntu 15.10: Booting servers
<W>2016-03-05 07:51:30.691 1 => Password for 'SuperUser' set to 'x@V?{k$t?"'
<W>2016-03-05 07:51:30.705 1 => Server listening on [::]:64738
<W>2016-03-05 07:51:30.709 1 => Generating new server certificate.
<W>2016-03-05 07:51:30.862 1 => Announcing server via bonjour
<W>2016-03-05 07:51:30.872 1 => Not registering server as public
<W>2016-03-05 07:51:30.872 Object::connect: No such slot MurmurDBus::userTextMessage(const User *, const TextMessage &)
<C>2016-03-05 07:51:42.932 Caught SIGTERM, exiting
<W>2016-03-05 07:51:42.933 Killing running servers
<W>2016-03-05 07:51:42.939 1 => Stopped announcing server via bonjour
<W>2016-03-05 07:51:42.943 1 => Stopped
<W>2016-03-05 07:51:42.943 Shutting down



# Murmur configuration file.
# General notes:
# * Settings in this file are default settings and many of them can be overridden
#   with virtual server specific configuration via the Ice or DBus interface.
# * Due to the way this configuration file is read some rules have to be
#   followed when specifying variable values (as in variable = value):
#     * Make sure to quote the value when using commas in strings or passwords.
#        NOT variable = super,secret BUT variable = "super,secret"
#     * Make sure to escape special characters like '\' or '"' correctly
#        NOT variable = """ BUT variable = "\""
#        NOT regex = \w* BUT regex = \\w*

# Path to database. If blank, will search for
# murmur.sqlite in default locations or create it if not found.

# If you wish to use something other than SQLite, you'll need to set the name
# of the database above, and also uncomment the below.
# Sticking with SQLite is strongly recommended, as it's the most well tested
# and by far the fastest solution.

# If you want to use ZeroC Ice to communicate with Murmur, you need
# to specify the endpoint to use. Since there is no authentication
# with ICE, you should only use it if you trust all the users who have
# shell access to your machine.
# Please see the ICE documentation on how to specify endpoints.
#ice="tcp -h -p 6502"

# Ice primarily uses local sockets. This means anyone who has a
# user account on your machine can connect to the Ice services.
# You can set a plaintext "secret" on the Ice connection, and
# any script attempting to access must then have this secret
# (as context with name "secret").
# Access is split in read (look only) and write (modify) 
# operations. Write access always includes read access,
# unless read is explicitly denied (see note below).
# Note that if this is uncommented and with empty content,
# access will be denied.


# Murmur defaults to not using D-Bus. If you wish to use dbus, which is one of the
# RPC methods available in Murmur, please specify so here.  [The D-Bus interface
# is now considered deprecated and using it is no longer advised.]

# Alternate D-Bus service name. Only use if you are running distinct
# murmurd processes connected to the same D-Bus daemon.

# How many login attempts do we tolerate from one IP
# inside a given timeframe before we ban the connection?
# Note that this is global (shared between all virtual servers), and that
# it counts both successfull and unsuccessfull connection attempts.
# Set either Attempts or Timeframe to 0 to disable.
#autobanAttempts = 10
#autobanTimeframe = 120
#autobanTime = 300

# Specifies the file Murmur should log to. By default, Murmur
# logs to the file 'murmur.log'. If you leave this field blank
# on Unix-like systems, Murmur will force itself into foreground
# mode which logs to the console.

# If set, Murmur will write its process ID to this file
# when running in daemon mode (when the -fg flag is not
# specified on the command line). Only available on
# Unix-like systems.

# The below will be used as defaults for new configured servers.
# If you're just running one server (the default), it's easier to
# configure it here than through D-Bus or Ice.
# Welcome message sent to clients when they connect.
welcometext="<br />Welcome to Vandin's mumble server.<br />Enjoy your stay!<br />"

# Port to bind TCP and UDP sockets to.

# Specific IP or hostname to bind to.
# If this is left blank (default), Murmur will bind to all available addresses.

# Password to join server.

# Maximum bandwidth (in bits per second) clients are allowed
# to send speech at.

# Maximum number of concurrent clients allowed.

# Amount of users with Opus support needed to force Opus usage, in percent.
# 0 = Always enable Opus, 100 = enable Opus if it's supported by all clients.

# Maximum depth of channel nesting. Note that some databases like MySQL using
# InnoDB will fail when operating on deeply nested channels.

# Regular expression used to validate channel names.
# (Note that you have to escape backslashes with \ )
#channelname=[ \\-=\\w\\#\\[\\]\\{\\}\\(\\)\\@\\|]+

# Regular expression used to validate user names.
# (Note that you have to escape backslashes with \ )

# Maximum length of text messages in characters. 0 for no limit.

# Maximum length of text messages in characters, with image data. 0 for no limit.

# Allow clients to use HTML in messages, user comments and channel descriptions?

# Murmur retains the per-server log entries in an internal database which
# allows it to be accessed over D-Bus/ICE.
# How many days should such entries be kept?
# Set to 0 to keep forever, or -1 to disable logging to the DB.

# To enable public server registration, the serverpassword must be blank, and
# this must all be filled out.
# The password here is used to create a registry for the server name; subsequent
# updates will need the same password. Don't lose your password.
# The URL is your own website, and only set the registerHostname for static IP
# addresses.
# Only uncomment the 'registerName' parameter if you wish to give your "Root" channel a custom name.
#registerName=Free Public Server. Come on in!

# If this option is enabled, the server will announce its presence via the 
# bonjour service discovery protocol. To change the name announced by bonjour
# adjust the registerName variable.
# See for more information
# about bonjour.

# If you have a proper SSL certificate, you can provide the filenames here.
# Otherwise, Murmur will create it's own certificate automatically.

# If Murmur is started as root, which user should it switch to?
# This option is ignored if Murmur isn't started with root privileges.

# If this options is enabled, only clients which have a certificate are allowed
# to connect.

# If enabled, clients are sent information about the servers version and operating
# system.

# You can configure any of the configuration options for Ice here. We recommend
# leave the defaults as they are.
# Please note that this section has to be last in the configuration file.

Any help would be appreciated.

Link to comment
Share on other sites


  • Create New...