Red Hat Bugzilla – Bug 1024138
murmur service fails to start (networking)
Last modified: 2015-02-17 12:50:56 EST
Description of problem:
The murmur service fails to start on system boot sometimes. It usually requires a full system reboot to trigger this bug. It usually follows log messages like:
<W>2012-05-01 09:39:19.659 1 => Server: TCP Listen on [::]:64738 failed: The bound address is already in use
<W>2013-04-12 19:36:21.250 Binding to address ::1%1
<W>2013-04-12 19:36:21.250 Binding to address 127.0.0.2
<W>2013-04-15 15:21:49.131 1 => Server listening on [0::1]:64738
<W>2013-04-15 15:21:49.136 1 => Server listening on 127.0.0.2:64738
We believe the problem is a failure in systemd ordering to wait for networking to be fully up. We believe the fix is to set in
I don't reboot much, so real testing of this is pending.
This may have gotten better with newer versions of systemd, since the most common failures were with previous versions of Fedora.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install murmur, base configure
3. service murmur status
4. try to connect with mumble from another machine
Sometimes it works, sometimes the service status errors out. I haven't noticed it starting successfully but not being connectable, but I think that's a possible outcome.
murmur waits for an externally connectable interface to be fully up before binding to a random IP.
By the way, I have host= set to my machine's static hostname in /etc/mumble-server.ini, and my machine uses DHCP (though it has a permanent lease on the IP/hostname).
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.