mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
Murmur does not shut down when SIGTERM #1644
Labels
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mumble-mumble-voip#1644
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Silmerias on GitHub (Sep 30, 2019).
murmur-static_x86-1.3.0
Debian stretch
4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u1 (2019-09-20) x86_64 GNU/Linux
When sent SIGTERM by systemd we see murmur closing, but the process will never shut down before systemd sigterm timeout kill it with SIGKILL.
During the process the CPU is 100% overheated and strace show murmur trying to poll at 24000 messages/seconds.
@davidebeatrici commented on GitHub (Sep 30, 2019):
Could you attach GDB to Murmur and check the backtrace after
SIGTERMis sent, please?@Silmerias commented on GitHub (Sep 30, 2019):
@mkrsn commented on GitHub (Mar 16, 2021):
Same problem here. Any News on that?
version: 1.3.4.x86_static
Linux 5.10.23-gentoo #1 SMP Mon Mar 15 12:07:21 CET 2021 x86_64 GNU/Linux
After a SIGTERM:
fd12 is the file descriptor to the MariaDB Socket.
backtrace
@Krzmbrzl commented on GitHub (Mar 17, 2021):
Afaik nobody was able to track the issue down yet. In fact I am not even sure somebody found the time to really try yet 🤔
@Hartmnt commented on GitHub (Mar 7, 2025):
I can not reproduce this using recent versions of mumble-server, nor murmur 1.3.4
Both tested as a service with systemd v256 using
systemctl stop murmurAm I missing something here or was this a systemd or configuration problem?
@mkrsn commented on GitHub (Mar 7, 2025):
This issue is now ~6 years old - maybe it got fixed unintentionally in the meanwhile.
Some months after reporting the issue i switched away from the static binary. Since then I compile it by myself - problem solved for me.
As far as I can tell: it was a problem in the binary. I have never used systemd and have not changed the configuration, only the binary.
@Hartmnt commented on GitHub (Mar 7, 2025):
@mkrsn Interesting, I have tried as systemd service and as plain binary. I even downloaded the old 1.3.4 static binary from GitHub. Under no circumstances I could reproduce the described behavior... At least not with a relative recent distro. I'll close this then.
@mkrsn commented on GitHub (Mar 7, 2025):
If it is helpful for you, i can check the binary. See if I can still reproduce the issue.
@Hartmnt commented on GitHub (Mar 7, 2025):
@mkrsn Mhh, we don't support the 1.3 series anymore anyway, so no need to bother if 1.5.x works.
But I have to wonder what went wrong at what point :D