On 06/21/14 18:19, Alex Balashov wrote:
Hello,
Despite this fix
https://github.com/sipwise/rtpengine/commit/cbe1f805363b3d6a117e9e5425d7994…
I am continuing to experience periodic crash problems under high loads
with rtpengine. This is after upgrading mediaproxy-ng -> rtpengine.
Unfortunately, after this upgrade, it is impossible to tell the cause of
the crash because the [seemingly] newer rtpengine SIGABRT and/or crash
handler is not running properly and is getting in my way:
Jun 20 15:47:55 rtphost abrtd: Directory 'ccpp-2014-06-20-15:47:54-1123'
creation detected
Jun 20 15:47:55 rtphost abrt[2159]: Saved core dump of pid 1123
(/usr/sbin/rtpengine) to /var/spool/abrt/ccpp-2014-06-20-15:47:54-1123
(97013760 bytes)
Jun 20 15:47:55 rtphost abrtd: Executable '/usr/sbin/rtpengine' doesn't
belong to any package and ProcessUnpackaged is set to 'no'
Jun 20 15:47:55 rtphost abrtd: 'post-create' on
'/var/spool/abrt/ccpp-2014-06-20-15:47:54-1123' exited with 1
Jun 20 15:47:55 rtphost abrtd: Deleting problem directory
'/var/spool/abrt/ccpp-2014-06-20-15:47:54-1123'
I am not sure why this script is exiting, but the result is that I have
no /var/spool/abrt/ccpp-2014-06-20-15:47:54-1123 and no core dump to
work with. This is on a standard minimal CentOS 6.5.x install.
Is there any way to either disable this signal handler and just let it
dump core normally, or, otherwise, to definitively fix the crash handler?
This is not something that rtpengine is doing. You'd have to look within
your system installation/distribution, possibly here:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux…
cheers