Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
after building murmur from the source on Debian 6.0.6 I get a "No such slot"
message in the logfile.
<W>2012-10-24 12:50:51.297 Initializing settings from /etc/mumble-server.ini (basepath /etc)
<C>2012-10-24 12:50:51.299 Adding 1 CA certificates from certificate file.
<W>2012-10-24 12:50:51.299 OpenSSL: OpenSSL 0.9.8o 01 Jun 2010
<C>2012-10-24 12:50:51.299 Successfully switched to uid 113
<W>2012-10-24 12:50:51.309 SSL: Added CA certificates from '/etc/ssl/certs/ca-certificates.crt'
<W>2012-10-24 12:50:51.315 ServerDB: Opened SQLite database /var/lib/mumble-server/mumble-server.sqlite
<W>2012-10-24 12:50:51.317 Resource limits were 0 0
<W>2012-10-24 12:50:51.317 Successfully dropped capabilities
<W>2012-10-24 12:50:51.318 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running
<W>2012-10-24 12:50:51.346 Murmur 1.2.4 (Compiled Oct 24 2012 09:46:06) running on X11: Debian GNU/Linux 6.0.6 (squeeze): Booting servers
<W>2012-10-24 12:50:51.363 1 => Server listening on [::]:64738
<W>2012-10-24 12:50:51.374 1 => Not registering server as public
<W>2012-10-24 12:50:51.374 Object::connect: No such slot MurmurDBus::userTextMessage(const User *, const TextMessage &)
The server seems to work okay.
Here is my configuration file:
# 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 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 127.0.0.1 -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
# Murmur default to logging to murmur.log. If you leave this blank,
# murmur will log to the console (linux) or through message boxes (win32).
# If set, murmur will write its process ID to this file.
# 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
# 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.
# Regular expression used to validate channel names
# (note that you have to escape backslashes with \ )
# 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
# Only uncomment the 'registerName' parameter if you wish to give your "Root" channel a custom name.
# To enable bonjour service discovery uncomment the following line.
# To change the name announced by bonjour adjust the registerName variable.
# See [url]http://developer.apple.com/networking/bonjour/index.html[/url] 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.
# 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 ideas whats going on there?
The cop-out solution would be to just disable dbus support at compile time.
That interface is deprecated for murmur management anyway.