| Summary: | ASTERISK-13968: DB Reading Crashes Asterisk | ||
| Reporter: | Leo Brown (netfuse) | Labels: | |
| Date Opened: | 2009-04-16 13:45:16 | Date Closed: | 2011-06-07 14:07:26 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_db |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) bt.txt | |
| Description: | Please bear with me on this, going on the basis of the stack trace, it seems that DB reading has been crashing our *1.6.0.1. Trace attached, any more info you need on request. ****** ADDITIONAL INFORMATION ****** System has also been locking up after a number of reloads (any type of reload it seems). | ||
| Comments: | By: Leo Brown (netfuse) 2009-04-16 13:46:30 FreeBSD 6.2, Jailed (chrooted) environment. CDR Mysql, autoload on but nonessential modules disabled. By: Leif Madsen (lmadsen) 2009-04-16 16:47:38 From what I can tell, this may be corrupt memory, and thus a valgrind trace will mostly likely be necessary. See the doc/valgrind.txt file, and attach the information as a file to this issue once you've reproduced the issue. Note that Asterisk may NOT crash inside of valgrind, but the information could still be useful. Thanks! By: Leo Brown (netfuse) 2009-04-20 06:48:32 I've moved to 1.6.0.9 which seems to have resolved this stability issue. If it comes back, i'll reopen and post a valgrind. By: Tilghman Lesher (tilghman) 2009-04-20 15:17:43 Closed by request of reporter. | ||