I ran into this issue last week on a brand-new install of Raspbian 'Bullseye' 
running on a RPi 3.  It essentially makes it impossible to control the daemon 
using normal systemd tools, and often results in multiple instances of murmurd 
running simultaneously.

All I did to run into it was install the OS, `apt upgrade` everything, install 
a handful of common packages (emacs-nox, screen, chrony; nothing exotic), then 
install mumble-server from the default Raspbian repos.  

Both the 'start on boot' and 'high priority' dpkg configuration options were 
enabled.

I didn't install, nor am I trying to use, any custom SSL certs (or SSL certs at 
all, except as they might be used in the default configuration).

I encountered the problem almost immediately, because after `apt install 
mumble-server` completed, the first thing I did was lightly edit 
/etc/mumble-server.ini and then attempt to restart the service:

    # systemctl restart mumble-server.service
    <-- APPROX. 4 MINUTES PASS... -->
    Job for mumble-server.service failed because a timeout was exceeded.
    See "systemctl status mumble-server.service" and "journalctl -xe" for 
details.

The journal contains, among other things, these lines:

    mumble-server.service: Found left-over process 1469 (murmurd) in control
     group while starting unit. Ignoring.
    This usually indicates unclean termination of a previous run, or service
     implementation deficiencies.

And it appears there are now two instances of murmurd:

    # ps aux | grep murmurd
    mumble-+   650  0.0  2.4  78920 23324 ?        Sl   May28   0:06 
     /usr/sbin/murmurd -ini /etc/mumble-server.ini
    mumble-+  5194  0.0  2.4  70700 23236 ?        S    May28   0:03 
     /usr/sbin/murmurd -ini /etc/mumble-server.ini

And if I run `systemctl restart mumble-server` again, it will create a 3rd 
instance of murmurd and so on.

It's clear from reading about this issue that I'm not the first to run into it, 
and there appear to be a variety of solutions, but it's unclear what tradeoffs 
(if any) they involve.  It would really be ideal if the package just worked 
'out of the box' with sane defaults.

Happy to provide additional information as needed.

V/R,
James

Reply via email to