On 06/22/2014 11:15 AM, Carlos Ruiz Díaz wrote:
I've been through the same problem some time ago, even with the same
misleading syslog message. Turned out the core file was not where the
logs said they were put, but in the exact working directory where I
manually started the service.
I looked,
I've been through the same problem some time ago, even with the same
misleading syslog message. Turned out the core file was not where the logs
said they were put, but in the exact working directory where I manually
started the service.
Try running rtpengine without the init.d scripts. Rtpengine h
On 06/22/2014 10:59 AM, Carlos Ruiz Díaz wrote:
The core file is usually stored in the working directory where the
executable was invoked.
Yeah, if it's not being caught and then mishandled by a specious
endeavuor like ABRT, conceived by cretins and imbeciles.
--
Alex Balashov - Principal
E
This ABRT service is one of the stupidest things I've ever heard of.
Whoever conceived of this scourge, and other futile and misguided
attempts to speciously "automate" things that have worked just fine for
decades, should burn in a special circle of hell. Neither I nor anyone
else need a "cor
The core file is usually stored in the working directory where the
executable was invoked.
Regards,
Carlos
On Sun, Jun 22, 2014 at 9:28 AM, Alex Balashov
wrote:
> On 06/21/2014 10:01 PM, Richard Fuchs wrote:
>
> This is not something that rtpengine is doing. You'd have to look within
>> your
On 06/21/2014 10:01 PM, Richard Fuchs wrote:
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/6/html/Deployment_Guide/ch-abrt.html
Thanks f
On 06/21/14 18:19, Alex Balashov wrote:
> Hello,
>
> Despite this fix
>
>
> https://github.com/sipwise/rtpengine/commit/cbe1f805363b3d6a117e9e5425d79943ddbf92a0
>
>
> I am continuing to experience periodic crash problems under high loads
> with rtpengine. This is after upgrading mediaproxy-ng
