Summary:	ASTERISK-28627: Error FRACK!, failed assertion bad magic number
Reporter:	Rosa Atienza (atienzar)	Labels:
Date Opened:	2019-11-24 15:32:27.000-0600	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	Channels/chan_sip/General
Versions:	13.13.1 13.21.1 13.29.1	Frequency of Occurrence	Frequent
Related Issues:
Environment:	Asterisk compiled on a baremetal machine with debian 10, dell PowerEdge R340 with Intel(R) Xeon(R) E-2124 CPU @ 3.30GHz and 16G RAM, 1T of hard disk with RAID hardware gcc version 8.3.0 (Debian 8.3.0-6) Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux Asterisk with chan_sip and realtime for the sip friends with mariadb.	Attachments:	( 0) sip.conf
Description:	Asterisk without calls, only has 40 extensions,  after 12  or 24 hours working (without traffic ) starts to throw this message, at the moment without crash.   The problem appears if  asterisk is started by systed or if you start with asterisk,  also as root and as asterisk user. [Nov 24 22:19:48] ERROR[20558]: astobj2.c:136 INTERNAL_OBJ: FRACK!, Failed assertion bad magic number 0x1fca for object 0x7f28a02be6e8 (0) [Nov 24 22:19:48] ERROR[20563]: astobj2.c:136 INTERNAL_OBJ: FRACK!, Failed assertion bad magic number 0x1fca for object 0x7f28a02be6e8 (0) [Nov 24 22:19:48] ERROR[20562]: astobj2.c:136 INTERNAL_OBJ: FRACK!, Failed assertion bad magic number 0x1fca for object 0x7f28a02be6e8 (0) [Nov 24 22:19:48] ERROR[20554]: astobj2.c:136 INTERNAL_OBJ: FRACK!, Failed assertion bad magic number 0x1fca for object 0x7f28a02be6e8 (0) [Nov 24 22:19:48] ERROR[20582]: astobj2.c:136 INTERNAL_OBJ: FRACK!, Failed assertion bad magic number 0x1fca for object 0x7f28a02be6e8 (0) [Nov 24 22:19:48] ERROR[20561]: astobj2.c:136 INTERNAL_OBJ: FRACK!, Failed assertion bad magic number 0x1fca for object 0x7f28a02be6e8 (0) [Nov 24 22:19:48] ERROR[20425]:   Got 10 backtrace records # 0: asterisk(__ao2_ref+0x1e1) [0x563ff43d7301] # 1: /usr/lib/asterisk/modules/chan_sip.so(+0x6d61a) [0x7f2889a5161a] # 2: asterisk(+0x1c7520) [0x563ff4537520] # 3: asterisk(ast_taskprocessor_execute+0x166) [0x563ff4550a66] # 4: asterisk(+0x1e77b0) [0x563ff45577b0] # 5: asterisk(ast_taskprocessor_execute+0xc7) [0x563ff45509c7] # 6: asterisk(+0x1e7bbc) [0x563ff4557bbc] # 7: asterisk(+0x1f1d99) [0x563ff4561d99] # 8: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7f28f1ba0fa3] # 9: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f28f17794cf] ... It seems that each line of these : [Nov 24 22:19:48] ERROR[20561]: astobj2.c:136 INTERNAL_OBJ: FRACK!, Failed assertion bad magic number 0x1fca for object 0x7f28a02be6e8 (0) Could correspond for each extension because this line appear as 40 times and then  as 40 times: Nov 24 22:19:48] ERROR[20548]: astobj2.c:136 INTERNAL_OBJ: FRACK!, Failed assertion bad magic number 0x1fca for object 0x7f28a02be6e8 (0) [Nov 24 22:19:48] ERROR[20574]:   Got 10 backtrace records # 0: asterisk(__ao2_ref+0x1e1) [0x563ff43d7301] # 1: /usr/lib/asterisk/modules/chan_sip.so(+0x6d61a) [0x7f2889a5161a] # 2: asterisk(+0x1c7520) [0x563ff4537520] # 3: asterisk(ast_taskprocessor_execute+0x166) [0x563ff4550a66] # 4: asterisk(+0x1e77b0) [0x563ff45577b0] # 5: asterisk(ast_taskprocessor_execute+0xc7) [0x563ff45509c7] # 6: asterisk(+0x1e7bbc) [0x563ff4557bbc] # 7: asterisk(+0x1f1d99) [0x563ff4561d99] # 8: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7f28f1ba0fa3] # 9: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f28f17794cf]
Comments:	By: Asterisk Team (asteriskteam) 2019-11-24 15:32:29.333-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Benjamin Keith Ford (bford) 2019-11-25 10:58:58.018-0600 Can you attach your sip.conf? Also, would you be able to try using PJSIP and see if the problem still exists? It will help narrow down where the problem is actually originating from. By: Rosa Atienza (atienzar) 2019-11-25 14:39:30.010-0600 Here is the sip.conf . By: Benjamin Keith Ford (bford) 2019-11-26 15:40:29.470-0600 The module you're having difficulty with is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available. Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1] If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way. [1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process [2]: http://www.asterisk.org/community/discuss [3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties A side note, if you are able to reproduce the issue with PJSIP, then we can investigate the issue further. Because the FRACK in the backtrace is coming from chan_sip, which is in an extended support state, it is maintained by the community. By: Rosa Atienza (atienzar) 2019-11-28 04:10:41.905-0600 Hi Benjamin Thanks so much for your answer I've changed to PJSIP and we are waiting to see it the problem persits or not but  let me know one thing, PJSSIP on ASterisk 13.29.2  supports DNS SRV?  or we also have to ugrade to Asterisk 16 ?