[asterisk-bugs] [JIRA] (ASTERISK-27205) res_rtp_asterisk: Asterisk crash with netlink error
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Wed Dec 20 08:36:07 CST 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-27205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240920#comment-240920 ]
Joshua Colp commented on ASTERISK-27205:
----------------------------------------
[~sum] I have a feeling that the fix for ASTERISK-27299 may have also fixed this based on your comment you just left. The file descriptor that was in use by netlink may have gotten closed accidentally.
> res_rtp_asterisk: 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_pjsip, Resources/res_rtp_asterisk
> Affects Versions: 13.15.0, 13.17.0
> Environment: Linux Ubuntu kernel 4.4.0-83 with glibc 2.23 and asterisk using internal PJSIP
> Reporter: Abhay Gupta
> Assignee: Unassigned
> Attachments: 14_50.txt, 17_08.txt, 24_08_12_00_bt_log, bt.txt, filename.txt, full_100000, gdb_18aug.txt, logs.txt, log.txt, Screen Shot 2017-09-12 at 12.34.05 PM.png, Screen Shot 2017-09-12 at 12.36.06 PM.png
>
>
> 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)
More information about the asterisk-bugs
mailing list