| Summary: | ASTERISK-25184: Lockup in IAX channel | ||
| Reporter: | Birger "WIMPy" Harzenetter (wimpy) | Labels: | |
| Date Opened: | 2015-06-23 12:10:25 | Date Closed: | 2020-01-14 11:14:09.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_iax2 |
| Versions: | 11.17.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) backtrace.txt ( 1) iax-lockup.txt | |
| Description: | 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. | ||
| Comments: | By: Birger "WIMPy" Harzenetter (wimpy) 2015-06-23 12:12:14.178-0500 Locks and threads from the situation By: ibercom (ibercom) 2015-06-23 13:16:56.722-0500 It could be related to ASTERISK-24983. By: Richard Mudgett (rmudgett) 2015-06-23 16:00:14.383-0500 It is not the same as ASTERISK-24983 By: Rusty Newton (rnewton) 2015-06-23 20:06:04.727-0500 Re-attaching WIMPy's debug as .txt so it can easily be viewed in browser.. By: Rusty Newton (rnewton) 2015-06-24 16:36:35.137-0500 [~rmudgett] determined that the output is not enough to show the cause of the problem. If you can show us how to reproduce the situation then we may be able to investigate further, otherwise I'm not sure what else we can do here. By: Birger "WIMPy" Harzenetter (wimpy) 2015-06-25 00:36:06.914-0500 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. By: Richard Mudgett (rmudgett) 2015-06-25 09:30:08.887-0500 There isn't enough here to figure out what happened. Looks like it could have started with the out of memory messages and snowballed from there. Which would mean that there is a potential memory leak involved. If you can figure out what triggers this and then use MALLOC_DEBUG to see what is leaking that would be helpful. Otherwise, I'm not sure what we could do. By: Birger "WIMPy" Harzenetter (wimpy) 2015-06-28 15:42:19.898-0500 The only thing I see is ERROR[18969] lock.c: chan_iax2.c line 1060 (signal_condition): Error obtaining mutex: Invalid argument 3 hours before the first Memory Allocation Failure. Apart from that just spurious warnings from IAX, but the last one is one more hour before the above one. By: Asterisk Team (asteriskteam) 2015-07-13 12:00:16.853-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||