[SR-Users] Disabling rtpengine abrt handler

[Carlos Ruiz Díaz]

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 has its way of
daemonizing itself anyway.

If you are unlucky even after doing this, maybe a standard shell find could
help you.

# find / -name core.<pid-reported-in-the-logs> -type f
# find / -name core.1123 -type f


On Sun, Jun 22, 2014 at 10:01 AM, Alex Balashov <abalashov at evaristesys.com>
wrote:

> 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
> Evariste Systems LLC
> Tel: +1-678-954-0670
> Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
>
> Please be kind to the English language:
>
> http://www.entrepreneur.com/article/232906
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>



-- 
Carlos
http://caruizdiaz.com
http://ngvoice.com
+52 55 3048 3303
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20140622/6b20c645/attachment.html>