| Summary: | ASTERISK-20022: CLONE - CLI hang and unresponsive when issuing "show channels" or "core show channels" | ||||
| Reporter: | test (mobme) | Labels: | |||
| Date Opened: | 2012-06-18 23:35:14 | Date Closed: | 2012-06-19 07:35:01 | ||
| Priority: | Minor | Regression? | No | ||
| Status: | Closed/Complete | Components: | General | ||
| Versions: | Frequency of Occurrence | ||||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) 14178.patch | |||
| Description: | Asterisk CLI becomes un-responsive after issuing "show channels" or "core show channels". The issue is exhibited on Asterisk 1.4.22 release. The issue had also been exhibited with using versions 1.4.21.X and 1.4.20. ****** ADDITIONAL INFORMATION ****** I couldn't find any indication why would this happen, even increasing the logging level in logger.conf doesn't yield any information regarding this. The issue is exhibited when the system is using a large number of channels for a long period of time. The interesting part here that this machine is part of a two machine environment, running the same Kernel and the same code (apart from minor changes in the dialplan). One machine is not exhbiting any issues, while the other does. Originally, we've used two DELL 2950 servers, and were under the impression that the server hardware is causing this, however, the problematic server had been replaced to an IBM server, however, the issue remains. The configuration of the server is as following: Hardware IBM xServer x3650 2GB RAM 2 x 144GB SAS (System Drives) 4 x 300GB SAS (DATA Drives) 2 x TE420P card with HEC Software CentOS 5.2 with all updates Asterisk 1.4.22 FreePBX for management only version 2.4.X A set of small AGI scripts for the platform usage In terms of modules compiled, here is the list: DAHDI 2.1.0.3 LIBPRI 1.4.7 ASTERISK 1.4.22 ASTERISK-ADDONS 1.4.7 Linux Kernel is: 2.6.18-92.1.22.el5 #1 SMP Tue Dec 16 11:57:43 EST 2008 x86_64 x86_64 x86_64 GNU/Linux Another issue that I've noticed (may be related or not), when loading DAHDI and the coresponding Card module, the network seems to halt for almost 20 seconds, then resumes for some reason. I couldn't find any indication why that would happen, however, when the HEC boards are removed - that doesn't happen, however, the problem still remains. Before the server hardware was replaced, we've replaced(on the DELL servers) the TE420 cards, the HEC modules, processors, memory, motherboards - you name it, it was replaced. Nothing seems to budge this one. My general feel is that we're having some problems with the TE420P and the HEC module, however, I can't really pin point it, as these were replaced. However, I can't really classify this behaviour to a specific part of Asterisk, in order to classify the bug personality. Following below is some machine information: lspci -v Digium related output: 08:08.0 Communication controller: Digium, Inc. Unknown device 0420 (rev 02) Subsystem: Unknown device 0004:0000 Flags: bus master, medium devsel, latency 64, IRQ 122 Memory at c7000000 (32-bit, non-prefetchable) [size=128] 11:08.0 Communication controller: Digium, Inc. Unknown device 0420 (rev 02) Subsystem: Unknown device 0004:0000 Flags: bus master, medium devsel, latency 64, IRQ 114 Memory at c4000000 (32-bit, non-prefetchable) [size=128] /proc/interrupts CPU0 CPU1 CPU2 CPU3 0: 19994098 0 0 0 IO-APIC-edge timer 1: 0 0 0 0 IO-APIC-edge i8042 8: 1 0 0 0 IO-APIC-edge rtc 9: 0 0 0 0 IO-APIC-level acpi 14: 0 0 0 0 IO-APIC-edge libata 15: 149 0 179997 0 IO-APIC-edge ide1 90: 55 0 0 0 IO-APIC-level ehci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb4 98: 0 0 0 0 IO-APIC-level uhci_hcd:usb3, uhci_hcd:usb5 114: 27612 17278848 2650001 9998 IO-APIC-level wct4xxp 122: 22174 2660071 16950066 328732 IO-APIC-level wct4xxp 130: 253531 0 0 0 PCI-MSI eth0 169: 32980 0 826323 0 IO-APIC-level aacraid NMI: 1476 2868 2806 1359 LOC: 19986898 19986863 19985283 19985236 ERR: 0 MIS: 0 Cheers, Nir | ||||
| Comments: | By: Matt Jordan (mjordan) 2012-06-19 07:34:55.694-0500 Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions. After testing with Asterisk 1.8, if you find this problem has not been resolved, please open a new issue against Asterisk 1.8. | ||||