Bug #3446
Murmur > Mumble-server Migration
0%
Description
- steps to reproduce:
1. Using a working install of murmur upgrade via the usual pacman -Syu and say yes/y to the replacement of the package murmur with mumble server.
2. As requested consolidate the relevant config into the from the murmur.ini to the mumble-server.ini, then copy or move the /var/db/murmur/murmur.sqlite file to /var/lib/mumble-server/mumble-server.sqlite and make sure that the _mumble-server system user is able to access the ssl certs.
3. Start mumble using either the systemd unit or the mumble-server -fg -in ... (etc) command, both continue fine until it reads the following:
Feb 09 20:05:52 hostname mumble-server[3783]: mumble-server: /build/mumble/src/mumble-1.5.517/src/MumbleProtocol.cpp:370: void Mumble::Protocol::UDP>AudioEncoder<role>::preparePreEncodedSnippets() [with Mumble::Protocol::Role role = Mumble::Protocol::Role::Server]: Assertion `successful' failed.
Whilst systemd shows the mumble-server unit as active, the server is not responsive or seemingly operational and top shows fairly high cpu usage (perhaps looping?).
Downgrading back to murmur fixes the issue
History
Updated by ryry about 2 months ago
Not sure why the "pacman Syu and say yes/y to the replacement of the package murmur with mumble server" line above is struck through, but it shouldn't be it is part of the steps to reproduce.
Updated by bill-auger about 2 months ago
- Description updated (diff)
thats is due to redmine's wiki syntax - it is because the next line begins with dashes ('--') - so i changed the dashes to a numbered list (or press the "ordered list" button)