[asterisk-bugs] [JIRA] (ASTERISK-19538) Asterisk segfaults on sippeers realtime redundancy
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Sun May 17 15:35:33 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226243#comment-226243 ]
Rusty Newton edited comment on ASTERISK-19538 at 5/17/15 3:35 PM:
------------------------------------------------------------------
A fix was merged. Auto-close missed this one.. closing out.
was (Author: rnewton):
Auto-close missed this one.. closing out.
> Asterisk segfaults on sippeers realtime redundancy
> --------------------------------------------------
>
> Key: ASTERISK-19538
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-19538
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Addons/res_config_mysql
> Affects Versions: 1.8.10.0
> Environment: CentOS 5, CentOS 6
> Reporter: Alex
> Severity: Critical
> Attachments: backtrace.txt
>
>
> Easily reproducible segfault affecting all versions of the * 1.8 branch:
> 1. Create two MySQL servers server1 and server2 in res_mysql.conf
> 2. Apply redundancy in extconfig.conf as follows:
> sippeers => mysql,server,sip_peers,1
> sippeers => mysql,server2,sip_peers,2
> 3. Start Asterisk. It won't start, and will segfault at start.
> Tested on different servers in different configurations. Segfault is constant, and depends only on redundancy configuration (leaving only one server helps). No backtrace is provided, if (really) needed, I can provide it, but the bug is easily reproducible.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list