| Summary: | ASTERISK-12266: asterisk-1.6.0-beta9 crash, not sure why | ||
| Reporter: | Paul Belanger (pabelanger) | Labels: | |
| Date Opened: | 2008-06-26 14:59:07 | Date Closed: | 2011-06-07 14:01:05 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) backtrace.txt ( 1) backtrace.txt ( 2) valgrind.txt ( 3) valgrind2.txt ( 4) valgrind3.txt | |
| Description: | We just had our second crash in less than a week. Could not capture first crash, but did the second. See attached backtrace.txt. ****** ADDITIONAL INFORMATION ****** Don't have much info to add at this point. As I don't know why it crash. Let me know if you need anything else. | ||
| Comments: | By: Paul Belanger (pabelanger) 2008-06-26 15:04:53 sorry for the duplicate upload. Seem to be having some HTTP timeouts. By: Tilghman Lesher (tilghman) 2008-06-26 16:28:28 This appears to be memory corruption, so I need you to follow the instructions in doc/valgrind.txt. By: Paul Belanger (pabelanger) 2008-06-26 17:06:59 Corydon76: Not a problem. Is there any other information around about invoking valgrind and asterisk from an init.d script? As of now, we cannot reproduce this problem at will. And will need a method to restart asterisk in the event of a crash. By: Tilghman Lesher (tilghman) 2008-06-26 17:23:15 I don't have any other information to give, but it shouldn't be too difficult to figure out. By: Paul Belanger (pabelanger) 2008-06-26 19:01:59 Corydon76: No problems, thanks. We've managed to hack safe_asterisk to do what we need. As soon as the crash happens again, we'll upload files. By: Paul Belanger (pabelanger) 2008-07-20 23:47:12 Corydon76: We have ran valgrind for almost a month and have not reproduced this issue. Please close it out, and we'll re-open if problem happens again. By: Tilghman Lesher (tilghman) 2008-07-21 10:10:15 pabelanger: Running valgrind can have the effect of suppressing crashes, but I'd still like to see the logs that valgrind generated, as they often contain information that will aid in tracking down a crash that would have otherwise occurred. By: Paul Belanger (pabelanger) 2008-07-21 10:29:25 Corydon76: here are 3 traces over the last month we captured. Hopefully you'll be able to use them. By: Tilghman Lesher (tilghman) 2008-07-21 12:02:38 From a look through the logs, it appears that this issue was fixed with the same fix for ASTERISK-11417. | ||