Mumble Server hangs at "Booting Servers"

[elentrepreneur]

Hello,

I've been running murmur 1.2.3 for a couple of months with no issues. Yesterday, I rebooted my Ubuntu 12.04 server, but when it came back up, I noticed I couldn't connect to murmur. I found that Murmur was running, but it was not listening on any ports. I took a look at the log and noticed that it was hanging after the "booting servers" message.

The log snippet:

<W>2012-07-03 20:21:02.784 Initializing settings from /etc/mumble-server.ini (basepath /etc)
<W>2012-07-03 20:21:02.784 OpenSSL: OpenSSL 1.0.1 14 Mar 2012
<W>2012-07-03 20:21:02.837 SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email
<C>2012-07-03 20:21:02.837 Successfully switched to uid 113
<W>2012-07-03 20:21:02.839 ServerDB: Openend SQLite database /var/lib/mumble-server/mumble-server.sqlite
<W>2012-07-03 20:21:02.841 Resource limits were 0 0
<W>2012-07-03 20:21:02.841 Successfully dropped capabilities
<W>2012-07-03 20:21:02.843 DBus registration succeeded
<W>2012-07-03 20:21:02.845 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running
<W>2012-07-03 20:21:02.875 Murmur 1.2.3 (1.2.3-2ubuntu4) running on X11: Ubuntu 12.04 LTS: Booting servers

 

It seems like Murmur is not binding to a port like it should. I have performed 'sudo netstat -anltp | grep "64738"' and have received no results. 'sudo netstat -anltp | grep "6502"' does however yield one result (which is for ice).

My last successful connect log looked something like this:

<W>2012-06-29 20:12:30.891 Initializing settings from /etc/mumble-server.ini (basepath /etc)
<W>2012-06-29 20:12:30.921 OpenSSL: OpenSSL 1.0.1 14 Mar 2012
<W>2012-06-29 20:12:31.566 SSL: Adding recommended CA UTN-USERFirst-Client Authentication and Email
<C>2012-06-29 20:12:31.566 Successfully switched to uid 113
<W>2012-06-29 20:12:31.679 ServerDB: Openend SQLite database /var/lib/mumble-server/mumble-server.sqlite
<W>2012-06-29 20:12:31.715 Resource limits were 0 0
<W>2012-06-29 20:12:31.801 Successfully dropped capabilities
<W>2012-06-29 20:12:31.811 DBus registration succeeded
<W>2012-06-29 20:12:32.361 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running
<W>2012-06-29 20:12:32.835 Murmur 1.2.3 (1.2.3-2ubuntu4) running on X11: Ubuntu 12.04 LTS: Booting servers
<W>2012-06-29 20:12:33.137 1 => Server listening on [::]:64738
<W>2012-06-29 20:12:33.321 1 => Announcing server via bonjour
<W>2012-06-29 20:12:33.505 1 => Not registering server as public
<W>2012-06-29 20:12:33.664 1 => <1:(-1)> New connection: 192.168.1.3:54141
<W>2012-06-29 20:12:33.840 1 => <2:(-1)> New connection: 69.119.145.139:52401
<W>2012-06-29 20:12:34.151 1 => <1:(-1)> Client version 1.2.3 (Win: 1.2.3)
<W>2012-06-29 20:12:34.637 1 => Starting voice thread
<W>2012-06-29 20:12:34.821 1 => CELT codec switch ffffffff80000010 0 (prefer ffffffff80000010)

 

Anyone have any ideas of what could be causing it to hang like this? I don't see any logs elsewhere pointing to what may be going wrong.

[kissaki]

I’m not sure how Mumble handles virtual server starts. But did you stop the virtual servers of Mumble by any chance, before shutting it down?

Do you have a web-interface where you could manually start your virtual servers?

Or, if you bound Ice or DBus, could you check that port?

I presume the process is running, it just does not start any virtual server instances.

It doesn’t even log errors, so that would explain that.

[elentrepreneur]

Thanks for the reply!

I finally managed to fix it. I ran murmurd with no parameters, forcing mumble to start with default settings/database and mumble worked fine. From this I kind of figured out that the sqlite database may have been corrupt causing this error, even though the log stated it was opening fine. I ran 'dpkg-reconfigure mumble-server' which rebuilt the database (among other things) and it started working again. I lost all of my registered user settings and channel info but at least I now have a working murmur server again!