[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 Dec 28 02:48:39 CST 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-27532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241182#comment-241182 ]
Mohit Taneja commented on ASTERISK-27532:
-----------------------------------------
It's a virtual freepbx box with 12 GB memory , 4 vCPU and 50 GB HDD. We are using queuemetrics with the freepbx to provider logger and reporting functionalities to agents.
Normal call center activities happen during the time like login/logout/pause/unpasue , incoming calls, IVR selections, call queuing and agent selection and barging.
Core show channels verbose shows around 180 active channels and 100-110 active calls during the time .
What other console output you are looking for ?
As i mentioned we are using freepbx , how to upgrade asterisk to 13.18.4 in this scenerio?
Thanks,
Mohit Taneja
> 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: Mohit Taneja
> Labels: fax, webrtc
> Attachments: console.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