does not start automatically

[Robert Thompson]

I just did a fresh install of 12.04 x64 along with the mumble-server package. When restarting the system the mumble-server never goes into listening mode, the log file simply reads:

<W>2012-05-07 23:47:16.120 Initializing settings from /etc/mumble-server.ini (basepath /etc)
<W>2012-05-07 23:47:16.121 OpenSSL: OpenSSL 1.0.1 14 Mar 2012
<W>2012-05-07 23:47:16.234 SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email
<W>2012-05-07 23:47:16.240 ServerDB: Openend SQLite database /var/lib/mumble-server/mumble-server.sqlite
<W>2012-05-07 23:47:16.246 DBus registration succeeded
<W>2012-05-07 23:47:16.253 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running
<W>2012-05-07 23:47:16.343 Murmur 1.2.3 (1.2.3-2ubuntu4) running on X11: Ubuntu 12.04 LTS: Booting servers
<W>2012-05-07 23:47:16.355 1 => Announcing server via bonjour
<W>2012-05-07 23:47:16.363 1 => Not registering server as public

but if I do a simple '/etc/init.d/mumble-server restart' it begins to work fine and the log file reads:

<W>2012-05-07 23:55:07.391 Initializing settings from /etc/mumble-server.ini (basepath /etc)
<W>2012-05-07 23:55:07.392 OpenSSL: OpenSSL 1.0.1 14 Mar 2012
<W>2012-05-07 23:55:07.441 SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email
<W>2012-05-07 23:55:07.442 ServerDB: Openend SQLite database /var/lib/mumble-server/mumble-server.sqlite
<W>2012-05-07 23:55:07.448 DBus registration succeeded
<W>2012-05-07 23:55:07.450 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running
<W>2012-05-07 23:55:07.483 Murmur 1.2.3 (1.2.3-2ubuntu4) running on X11: Ubuntu 12.04 LTS: Booting servers
<W>2012-05-07 23:55:07.489 1 => Server listening on [::]:64738
<W>2012-05-07 23:55:07.492 1 => Announcing server via bonjour
<W>2012-05-07 23:55:07.498 1 => Not registering server as public

I did a complete removal and reinstallation of mumble-server and the problem still persists. I asked on the Ubuntu forums and have yet to receive any ideas so I'm submitting this as a bug.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sam Bostock (bosticko)]

In the log above, the difference is
<W>2012-05-07 23:55:07.489 1 => Server listening on [::]:64738
is not in the first paste, but is in the second.

I am also experiencing the same problem, and have the same line missing from my logs when the system boots, but appearing upon manual restart.

[Benjamin Xiao (ben-r-xiao)]

This is happening in Ubuntu 14.04 with Mumble 1.2.4 as well.

A service restart fixes it.

[Benjamin Xiao (ben-r-xiao)]

I didn't have any problems running mumble-server on Amazon EC2 so maybe it is because I am using Network Manager and the network interface isn't ready when Mumble starts up.

[Benjamin Xiao (ben-r-xiao)]

I have managed to workaround the issue by creating a NetworkManager dispatcher.d script. It basically restarts the mumble-server when it detects that my connection is up.

Put this script into /etc/NetworkManager/dispatcher.d/90mumblerestart
=============================================================

#!/bin/sh -e

IF=$1
STATUS=$2

if [ "$IF" = "em1" ]
then
        case "$STATUS" in
                up)
                        service mumble-server restart
                ;;
                *)
                ;;
        esac
fi

====================================================

Of course, replace em1 with whatever network interface you're using. This script works around the problem for me and I am able to connect to the mumble-server whenever I restart. The only downside is that whenever you disconnect/reconnect on your connection, the mumble server will get restarted, but I figured that if you're doing that all clients will be dropped anyways so it really makes no difference.