On 04/13/2015 02:43 PM, Tuxicoman wrote:
[...]
> # netstat -tpln
> tcp6 0 0 :::64738 :::* LISTEN 1360/murmurd
Good.
[...]
> Now it seems to listen to ipv6 ONLY. Other services like sshd have both
> 0.0.0.0:22 and :::22 services listening in netstat.
>
> I have only an ipv4
On 04/13/2015 02:49 PM, Tuxicoman wrote:
> sorry, in fact, I can access it in ipv4.
meaning if you use host=:: that you can access it in ipv4? Yes that's
expected.
The test I'm looking for results for is if host=:: has murmurd listen on
bootup correctly, but host= (i.e. nothing, or commented out
sorry, in fact, I can access it in ipv4.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
# systemctl status mumble-server
● mumble-server.service - Mumble VoIP server
Loaded: loaded (/lib/systemd/system/mumble-server.service; enabled)
Active: active (running) since lun 2015-04-13 20:32:21 CEST; 1min 28s
ago
Docs: man:murmurd(1)
file:///usr/share/doc/mumble-server/
On 04/13/2015 03:33 AM, Tuxicoman wrote:
> Thanks, this works !
Thank goodness. ;-)
Not quite done with this bug yet though; you'll see why below.
> Maybe having "host=0.0.0.0" as default value in the mumble-server.ini
> example file would be a good solution to fix this bug in the meanwhile?
We
Thanks, this works !
Maybe having "host=0.0.0.0" as default value in the mumble-server.ini
example file would be a good solution to fix this bug in the meanwhile?
# systemctl status mumble-server
● mumble-server.service - Mumble VoIP server
Loaded: loaded (/lib/systemd/system/mumble-server.ser
On 04/12/2015 06:37 PM, Erwan JACQ wrote:
> I'm sorry but the systemd service file provided didn't change the
> behavior. The issue is still the same on my machine.
Ugh. Okay. Thanks much for reporting this... at minimum it's
good to know that a systemd service file likely isn't a fix
for this.
I'm sorry but the systemd service file provided didn't change the behavior. The
issue is still the same on my machine.
Here are my tests with 2 configurations:
A/with no "host" specified
# systemctl status mumble-server
● mumble-server.service - Mumble VoIP server
Loaded: loaded (/lib/syste
tags -1 - unreproducible moreinfo
thanks
On 03/11/2015 03:53 PM, Tuxicoman wrote:
> Package: mumble-server
> Version: 1.2.8-2
> Severity: important
>
> Dear Maintainer,
>
> After restart, the mumble-server is started but not listening.
> A manual restart of the service (systemctl restart mumble-
On 03/11/2015 03:53 PM, Tuxicoman wrote:
> Package: mumble-server
> Version: 1.2.8-2
> Severity: important
>
> Dear Maintainer,
>
> After restart, the mumble-server is started but not listening.
> A manual restart of the service (systemctl restart mumble-server) makes
> it work.
> The bug has bee
One more info :
# ls -l /etc/mumble-server.ini
-rw-r- 1 root mumble-server 6990 jan 18 13:45 /etc/mumble-server.ini
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: mumble-server
Version: 1.2.8-2
Severity: important
Dear Maintainer,
After restart, the mumble-server is started but not listening.
A manual restart of the service (systemctl restart mumble-server) makes it
work.
The bug has been reported too for Ubuntu :
https://bugs.launchpad.net/ubuntu
12 matches
Mail list logo