Mumble goes to timeout when connecting to murmur server

about the Ultimate Question of Life, the Universe, and Everything

Mumble goes to timeout when connecting to murmur server

Postby fbartolom » Thu Jan 05, 2017 11:05 am

I installed a murmur server with Ice support on my Centos 7 server and configured to answer to port 64738. Notwistanding everything seemed fine in the installation, the server fails to answer. You may test it yourself connecting to it. Here is the murmur.ini file:

# 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.

# 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.

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

# 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.


# 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 this server running <b>Murmur</b>.<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=Mumble Server

# 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 ... index.html 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.
#uname= murmur

# 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.
while '
Code: Select all
ps -uax|grep murmur
' gives:

murmur 20987 0.0 0.6 73864 12868 ? Sl 10:16 0:00 /usr/local/murmur/murmur.x86 -ini /etc/murmur.ini

Code: Select all
journalctl -b -u murmur

Jan 05 10:10:21 localhost.localdomain systemd[1]: Started Mumble Server (Murmur).
Jan 05 10:16:57 localhost.localdomain systemd[1]: Stopping Mumble Server (Murmur)...
Jan 05 10:16:57 localhost.localdomain systemd[1]: Starting Mumble Server (Murmur)...
Jan 05 10:16:57 localhost.localdomain systemd[1]: PID file /var/run/murmur/ not readable (yet?) after start.
Jan 05 10:16:57 localhost.localdomain systemd[1]: Started Mumble Server (Murmur).

And finally the log file:
<W>2017-01-05 10:47:04.939 Initializing settings from /etc/murmur.ini (basepath /etc)
<W>2017-01-05 10:47:04.940 Meta: TLS cipher preference is "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:AES256-SHA:AES128-SHA"
<W>2017-01-05 10:47:04.940 OpenSSL: OpenSSL 1.0.1q 3 Dec 2015
<W>2017-01-05 10:47:04.979 ServerDB: Opened SQLite database /var/lib/murmur/murmur.sqlite
<W>2017-01-05 10:47:04.983 MurmurIce: Endpoint "tcp -h -p 6502" running
<W>2017-01-05 10:47:04.984 OSInfo: Failed to execute lsb_release
<W>2017-01-05 10:47:04.984 Murmur 1.2.13 (1.2.13) running on X11: Linux 3.10.0-514.2.2.el7.x86_64: Booting servers
<W>2017-01-05 10:47:04.992 1 => Server listening on [::]:64738
<W>2017-01-05 10:47:04.996 1 => Announcing server via bonjour
<W>2017-01-05 10:47:05.005 1 => Not registering server as public
<W>2017-01-05 10:47:05.005 Object::connect: No such slot MurmurDBus::userTextMessage(const User *, const TextMessage &)

What should I do to have it correctly working on my Centos server.
Posts: 29
Joined: Wed Mar 04, 2015 6:29 pm
Location: Rome, Italy

Re: Mumble goes to timeout when connecting to murmur server

Postby kissaki » Tue Mar 07, 2017 11:27 pm

According to your logs it started and is listening.
Check via ps if the process is indeed running, and via netstat if it is indeed still listening. If so, maybe you have a firewall that blocks requests?
MumPI: Your Mumble Web Interface in PHP
User avatar
Team member
Team member
Posts: 1230
Joined: Sat Jan 09, 2010 12:15 pm

Re: Mumble goes to timeout when connecting to murmur server

Postby fbartolom » Wed Mar 08, 2017 8:02 am

I have no active firewall, for what I know, and murmur is alive and kicking:
ps -uax |grep mu
/usr/local/murmur/murmur.x86 -ini /etc/murmur.ini
how may I know better?

If you like to know more, you may try connecting to it at at the standard port.
Posts: 29
Joined: Wed Mar 04, 2015 6:29 pm
Location: Rome, Italy

Return to mumbles & murmurs

Who is online

Users browsing this forum: No registered users and 1 guest