Your message dated Thu, 03 Jan 2019 18:32:34 +0100
with message-id <[email protected]>
and subject line Closing bugs reported against unsupported versions
has caused the Debian Bug report #804652,
regarding asterisk: Crash of asterisk with Segfault
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.)


-- 
804652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804652
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---

Package: asterisk
Version: 1:11.13.1~dfsg-2+b1
Severity: important

Dear Maintainer,


asterisk crashes once a week with a segfault.

here is a short crash message from dmesg

[3029918.722174] asterisk[30561]: segfault at c9f63ad6 ip 00007f84f2123e2c sp 
00007f8487b1c860 error 4 in libc-2.19.so[7f84f20d9000+19f000]
[3874464.510536] asterisk[19998]: segfault at 4cd8d2e5 ip 00007f23c8e78e2c sp 
00007f235d952860 error 4 in libc-2.19.so[7f23c8e2e000+19f000]


One side affect is, that you cannot restart asterisk by

systemctl start asterisk
is not able to restart the process. You have to
systemctl stop asterisk
systemctl start asterisk
to get it up again.


The major problem is of course, that asterisk crashes.

I installed the dbg packages and I'm writing a core-dump next time the crash 
happens.




-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages asterisk depends on:
ii  adduser                                       3.113+nmu3
ii  asterisk-config                               1:11.13.1~dfsg-2
ii  asterisk-core-sounds-en [asterisk-prompt-en]  1.4.22-1
ii  asterisk-core-sounds-en-gsm                   1.4.22-1
ii  asterisk-modules                              1:11.13.1~dfsg-2+b1
ii  libc6                                         2.19-18+deb8u1
ii  libcap2                                       1:2.24-8
ii  libedit2                                      3.1-20140620-2
ii  libgcc1                                       1:4.9.2-10
ii  libpopt0                                      1.16-10
ii  libsqlite3-0                                  3.8.7.1-1+deb8u1
ii  libssl1.0.0                                   1.0.1k-3+deb8u1
ii  libstdc++6                                    4.9.2-10
ii  libtinfo5                                     5.9+20140913-1+b1
ii  libxml2                                       2.9.1+dfsg1-5

Versions of packages asterisk recommends:
ii  asterisk-moh-opsound-gsm                         2.03-1
ii  asterisk-voicemail [asterisk-voicemail-storage]  1:11.13.1~dfsg-2+b1
ii  sox                                              14.4.1-5

Versions of packages asterisk suggests:
pn  asterisk-dahdi   <none>
pn  asterisk-dev     <none>
pn  asterisk-doc     <none>
pn  asterisk-ooh323  <none>
pn  asterisk-vpb     <none>

-- Configuration Files:
/etc/default/asterisk changed:
AST_DUMPCORE=yes
CORE_PATTERN='/tmp/core.%e.%t'


-- no debconf information

--- End Message ---
--- Begin Message ---
Dear user,

thanks for helping us making Debian better by reporting this bug. Unfortunately it could not be dealt with in time. We lack the manpower to check all currently open bugs whether they still apply for the current version. Therefor we are closing old issues hoping that the documented problem has already been resolved.

If you can still reproduce this issue with a supported version of Debian/Asterisk

- 13.14 in Debian Stretch
- 13.23.1 in Debian Buster/Sid (right now)
- 16.1.0 in Experimental (soon in buster/sid I hope)

please feel free to reopen this bug.

Thanks,
Bernhard

--- End Message ---

Reply via email to