[asterisk-bugs] [JIRA] (ASTERISK-27532) ERROR[5383][C-00003919] astobj2.c: Excessive refcount 100000 reached on ao2 object 0x142f648
Mohit Taneja (JIRA)
noreply at issues.asterisk.org
Thu Feb 1 04:19:13 CST 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-27532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241950#comment-241950 ]
Mohit Taneja commented on ASTERISK-27532:
-----------------------------------------
Hi,
We upgraded the system to 13.18 as suggested and after a week we are again getting the same frack errors which is causing High CPU. Please help us to fix it.
2018-01-31 09:54:54] ERROR[19073][C-0004576f] astobj2.c: Excessive refcount 100000 reached on ao2 object 0x2ac1158
[2018-01-31 09:54:54] ERROR[19073][C-0004576f] astobj2.c: FRACK!, Failed assertion Excessive refcount 100000 reached on ao2 object 0x2ac1158 (0)
[2018-01-31 09:54:54] ERROR[22341][C-000459fc] astobj2.c: Excessive refcount 100000 reached on ao2 object 0x2ac1158
[root at is01-astrsk-001 ~]# asterisk -rx "core show version"
Asterisk 13.18.3 built by mockbuild @ jenkins2.schmoozecom.net on a x86_64 running Linux on 2017-12-01 23:22:34 UTC
PFA complete snippit
> ERROR[5383][C-00003919] astobj2.c: Excessive refcount 100000 reached on ao2 object 0x142f648
> --------------------------------------------------------------------------------------------
>
> Key: ASTERISK-27532
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-27532
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: . I did not set the category correctly.
> Affects Versions: 13.17.0
> Environment: Sangoma Freepbx official distro FreePBX 13.0.192.16
> Asterisk 13.17.0
> Reporter: Mohit Taneja
> Assignee: Unassigned
> Labels: fax, webrtc
> Attachments: console.txt, Frack_version13_18.txt, log_2018-01-15_core_show_channels.txt, log_2018-01-15_top.txt
>
>
> Hi
> We are recently installed Freepbx distro “FreePBX 13.0.192.16” running “Asterisk 13.17.0” on a x86_64 running Linux. From last 2 weeks the CPU suddenly goes to 100% utilization everyday between 9:50 AM EDT to 10:30 AM EDT.
> In the full logs we saw below error during the high CPU utilization. Once the error stop appearing the CPU agin goes to normal
> I have disabled CDR Reports and Call Recording Report modules but the problem is still happening
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list