[asterisk-bugs] [JIRA] (ASTERISK-27205) Asterisk crash with netlink error

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238130#comment-238130 ] 

Asterisk Team commented on ASTERISK-27205:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Asterisk crash with netlink error 
> ----------------------------------
>
>                 Key: ASTERISK-27205
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27205
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 13.15.0
>         Environment: Linux Ubuntu kernel 4.4.0-83 with glibc 2.23 and asterisk using internal PJSIP 
>            Reporter: Abhay Gupta
>
> There is segmentation fault that causes crash and bt is attached , it seems that Nelink error is the cause and can be seen from this changelog of glibc 
> https://abi-laboratory.pro/tracker/changelog/glibc/2.23/log.html
> getaddrinfo now detects certain invalid responses on an internal netlink
>   socket.  If such responses are received, an affected process will
>   terminate with an error message of "Unexpected error <number> on netlink
>   descriptor <number>" or "Unexpected netlink response of size <number> on
>   descriptor <number>".  The most likely cause for these errors is a
>   multi-threaded application which erroneously closes and reuses the netlink
>   file descriptor while it is used by getaddrinfo.
> this signal is not captured causing it to crash .



--
This message was sent by Atlassian JIRA
(v6.2#6252)