[asterisk-bugs] [JIRA] (ASTERISK-25184) Lockup in IAX channel
Birger "WIMPy" Harzenetter (JIRA)
noreply at issues.asterisk.org
Thu Jun 25 00:37:33 CDT 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Birger "WIMPy" Harzenetter updated ASTERISK-25184:
--------------------------------------------------
Status: Waiting for Feedback (was: Waiting for Feedback)
The last line in the log was
ERROR[18969] utils.c: Thread 'network_thread started at [12659] chan_iax2.c start_network_thread()' still has a lock! - 'our_timer' (0xa596810) from 'timerfd_timer_ack' in res_timing_timerfd.c:191!
But I guess that was from trying to unload the channel.
Oh, that's interesting. I didn't realize I have a core dump. It must have crashed while I killed it.
Looks like the real issue is that something exploded.
It started with several
ERROR[18974] /usr/src/telephony/asterisk/asterisk-11.17.1/include/asterisk/utils.h: Memory Allocation Failure in function internal_ao2_alloc at line 571 of astobj2.c
round about every 3 minutes.
> Lockup in IAX channel
> ---------------------
>
> Key: ASTERISK-25184
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25184
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_iax2
> Affects Versions: 11.17.1
> Reporter: Birger "WIMPy" Harzenetter
> Assignee: Birger "WIMPy" Harzenetter
> Attachments: backtrace.txt, iax-lockup.txt
>
>
> To quote rmudgett:
> It looks like a circular active_list.
> Or the logging system may be overwhelmed.
> As it's a virtual server, disk I/O might be an issue at times, but the call volume is very low.
> The are probably some locks unrelated to the issue as I took the information after trying to unload chan_iax2.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list