[asterisk-bugs] [JIRA] (ASTERISK-24885) Frequent Asterisk 13.2 core crash

Oleg Maximenco (JIRA) noreply at issues.asterisk.org
Mon Mar 16 16:03:35 CDT 2015


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

Oleg Maximenco edited comment on ASTERISK-24885 at 3/16/15 4:02 PM:
--------------------------------------------------------------------

I'll try to re-compile Asterisk with debug info on and make another backtrace by end of the week, but right now I'm just thinking to downgrade to 13.1, at least temporary so the users will calm down a little.

Yes, I've already contacted Digium support about a problem related to transfers: in about 1 case out of 10 our employees experience a "frozen" transfer - a transferring person's extension stays forever on the phone's screen.

The DPMA version is 13.0.2.1.1_x86_64.

Also started seeing this error message quite often (not sure if it's related though, but just in case):
[Mar 16 15:21:52] ERROR[25275]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:21:56] ERROR[19224]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:21:56] ERROR[29568]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:22:17] ERROR[24394]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:22:26] ERROR[24394]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:22:26] ERROR[19224]: taskprocessor.c:715 taskprocessor_push: tps is NULL!

Edit: the error message is showing up when a phone tries to register in the system, and because of the error message all registration requests fail. Hopefully restart will help.

Edit2: Restart helped, that does look something related to DPMA, because all other functionality besides of the DPMA-based wasn't affected.


was (Author: docusync):
I'll try to re-compile Asterisk with debug info on and make another backtrace by end of the week, but right now I'm just thinking to downgrade to 13.1, at least temporary so the users will calm down a little.

Yes, I've already contacted Digium support about a problem related to transfers: in about 1 case out of 10 our employees experience a "frozen" transfer - a transferring person's extension stays forever on the phone's screen.

The DPMA version is 13.0.2.1.1_x86_64.

Also started seeing this error message quite often (not sure if it's related though, but just in case):
[Mar 16 15:21:52] ERROR[25275]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:21:56] ERROR[19224]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:21:56] ERROR[29568]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:22:17] ERROR[24394]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:22:26] ERROR[24394]: taskprocessor.c:715 taskprocessor_push: tps is NULL!
[Mar 16 15:22:26] ERROR[19224]: taskprocessor.c:715 taskprocessor_push: tps is NULL!

Edit: the error message is showing up when a phone tries to register in the system, and because of the error message all registration requests fail. Hopefully restart will help.

Edit2: Restart helped, that does look something related to DPMA, because all other functionality besides of DPMA-based wasn't affected.

> Frequent Asterisk 13.2 core crash
> ---------------------------------
>
>                 Key: ASTERISK-24885
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24885
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.2.0
>         Environment: CentOS 7 / Kernel 3.10.0-123.2.e17.x96_64
>            Reporter: Oleg Maximenco
>            Assignee: Oleg Maximenco
>            Severity: Critical
>         Attachments: backtrace-3-16_09am.txt, backtrace-3-16_12pm.txt, gdb-3-16_09am.txt, gdb-3-16_12pm.txt
>
>
> Asterisk crashes 3-5 times a day after upgrading from 13.1 to 13.2.



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



More information about the asterisk-bugs mailing list