[asterisk-bugs] [JIRA] (ASTERISK-23617) Asterisk segfault when AgentLogin concur in a time frame using Realtime ODBC
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Wed Jun 25 12:59:57 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-23617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219910#comment-219910 ]
Rusty Newton commented on ASTERISK-23617:
-----------------------------------------
[~kmoore] looked into the backtraces. It appears you have roughly five different crashes. Memory corruption is suspected. To validate, you should run under [Valgrind|https://wiki.asterisk.org/wiki/display/AST/Valgrind] and provide the resulting output. You'll also want to run a memory diagnostic to check your system RAM.
Press Enter Feedback when you have the requested information.
> Asterisk segfault when AgentLogin concur in a time frame using Realtime ODBC
> ----------------------------------------------------------------------------
>
> Key: ASTERISK-23617
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-23617
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_agent, Resources/res_odbc
> Affects Versions: 11.8.1, 11.9.0
> Environment: CentOS release 6.5 2.6.32-431.11.2.el6.x86_64 (was 2.6.32-431.5.1.el6.x86_64) Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz 12Gb RAM
> Reporter: VoIPCamp
> Assignee: Rusty Newton
> Attachments: core.1014.gdb.txt, core.1014.log.txt, core.12979.txt, core.17055.gdb.txt, core.17055.log.txt, core.17381.txt, core.21046.txt, core.28334.gdb.txt, core.28334.log.txt, core.28596.gdb.txt, core.28596.log.txt, core.4930.txt, core.5904.txt, core.6580.gdb.txt, core.6580.log.txt, core.ast1190.14903.gdb.txt, core.ast1190.14903.log.txt, core.ast1190.1620.gdb.txt, core.ast1190.1620.log.txt, core.ast1190.7930.gdb.txt, core.ast1190.7930.log.txt
>
>
> Asterisk segfault when AgentLogin or logoff (hang up the chan_agent call) concur in a time frame. This use to happen when operation start or when agents shift is over.
> Realtime ODBC is used for dynamic agents and parts of dialplan. I've isolated some backtraces which seems an issue with the odbc driver itself and not asterisk (even though think it should avoid to crash).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list