Your message dated Fri, 16 Dec 2016 21:22:08 +0100
with message-id <[email protected]>
and subject line Re: Bug#846649 closed by Oleg Moskalenko <[email protected]>
(846649 to be closed)
has caused the Debian Bug report #846649,
regarding Frequent segfaults of coturn
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
846649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846649
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: coturn
Version: 4.5.0.5-1
Severity: serious
Hi,
I encounter frequent segfaults of coturn on a Debian Squeeze VM with
recent kernel (4.8.7-1). I don't know much about coturn, just use it for
a Spreed.ME installation and so far it worked well. But recently it
started to segfault out of the blue. I'm pretty sure that it's not even
used when segfaulting as it is a test installation with very few users.
Here's the log output from syslog:
Nov 28 22:37:49 ld-test kernel: [3277040.519778] turnserver[4996]: segfault at
8 ip 00007fc8f6a38dc6 sp 00007fc8f134bce0 error 4 in
libssl.so.1.0.2[7fc8f6a10000+5f000]
Nov 29 15:53:59 ld-test kernel: [3339210.639775] turnserver[4691]: segfault at
8 ip 00007f9afec9adc6 sp 00007f9af95adce0 error 4 in
libssl.so.1.0.2[7f9afec72000+5f000]
Dec 2 18:46:41 ld-test kernel: [14301.129202] turnserver[658]: segfault at 8
ip 00007f52b5932dc6 sp 00007f52af843ce0 error 4 in
libssl.so.1.0.2[7f52b590a000+5f000]
/var/log/turn/turn_<date>.log and /var/log/turn_<PID>_<date>.log both
don't hold anything related to the segfault.
I'll gladly further debug the issue if you give me instructions.
Cheers,
jonas
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages coturn depends on:
ii adduser 3.115
ii libc6 2.24-7
ii libevent-core-2.0-5 2.0.21-stable-2.1
ii libevent-extra-2.0-5 2.0.21-stable-2.1
ii libevent-openssl-2.0-5 2.0.21-stable-2.1
ii libevent-pthreads-2.0-5 2.0.21-stable-2.1
ii libhiredis0.13 0.13.3-2
ii libmariadbclient18 10.0.28-2
ii libpq5 9.6.1-2
ii libsqlite3-0 3.15.1-1
ii libssl1.0.2 1.0.2j-4
ii lsb-base 9.20161125
ii telnet [telnet-client] 0.17-41
coturn recommends no packages.
Versions of packages coturn suggests:
pn sip-router <none>
pn xmpp-server <none>
-- Configuration Files:
/etc/default/coturn changed:
TURNSERVER_ENABLED=1
/etc/turnserver.conf changed:
listening-port=8443
alt-listening-port=3478
listening-ip=172.18.20.144
relay-ip=172.18.20.144
fingerprint
lt-cred-mech
use-auth-secret
static-auth-secret=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
realm=XXXXXXXXXXXXXXXXXXX
total-quota=100
bps-capacity=0
stale-nonce=600
cert=/etc/letsencrypt/live/XXXXXXXXXXXXXXXXXXXXXXXXXX/fullchain.pem
pkey=/etc/letsencrypt/live/XXXXXXXXXXXXXXXXXXXXXXXXXX/privkey.pem
log-file=/var/log/turn/turn.log
no-loopback-peers
no-multicast-peers
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.5.0.5-1+b1
Hi Oleg,
after no segfault within the last four days I'm pretty sure that the bug
got fixed by the binNMU of coturn. Thanks for maintaining coturn.
Cheers,
jonas
Am 13.12.2016 um 02:38 schrieb Oleg Moskalenko:
> Jonas,
>
> Please test it and let us know.
>
> All crashes of this sort are in 99% due to the OpenSSL incompatibilities.
>
> Thanks
> Oleg
>
>
> On Mon, Dec 12, 2016 at 5:07 PM, Jonas Meurer <[email protected]> wrote:
>> Am 13.12.2016 um 00:50 schrieb Jonas Meurer:
>>
>>> Am 13.12.2016 um 00:45 schrieb Debian Bug Tracking System:
>>>> The bug was filed agains a "testing" binary package forcefully
>>>> installed in a Squeeze environment. That binary package was never
>>>> meant to be used in Squeeze. Coturn heavily relies on OpenSSL and on
>>>> binary compatibility with OpenSSL libraries. We cannot support that
>>>> binary in Squeeze. If you absolutely must to use Coturn with Squeeze,
>>>> then you have to compile Coturn manually from the sources from the
>>>> project page http://coturn.net.
>>>
>>> Sorry, but in my initial report I confused Squeeze with Stretch. In
>>> fact, this bug is discovered on Debian Stretch, which is already in
>>> freeze and supposed to be released as Stable within the next months.
>>>
>>> I keep experiencing this bug almost once a day on the Stretch system
>>> that runs coturn (along with a Spreed.ME setup).
>>>
>>> As I wrote earlier, the bug might be related to the OpenSSL (1.0 -> 1.1)
>>> transition that took place in Stretch recently. Probably a simple
>>> rebuild against OpenSSL 1.1 would fix it. If you like, I could give it a
>>> try. Would that help?
>>
>> Ha, just after sending this mail I saw that coturn indeed had been
>> binNMUed and updated to 4.5.0.5-1+b1 in Stretch. Will figure out whether
>> the binNMU fixed the segfault and report back in a few days.
>>
>> Cheers,
>> jonas
>>
>>
>>
signature.asc
Description: OpenPGP digital signature
--- End Message ---
