| Summary: | ASTERISK-08408: Asterisk segfaults (core dumped) at startup because of corrupted astdb | ||
| Reporter: | Andrey Solovyev (corruptor) | Labels: | |
| Date Opened: | 2006-12-21 07:12:15.000-0600 | Date Closed: | 2006-12-21 14:14:36.000-0600 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) astdb.backup ( 1) bt.txt | |
| Description: | Yesterday we had power loss because of bad UPS. Asterisk couldn't start after reboot. [pbx_dundi.so] => (Distributed Universal Number Discovery (DUNDi)) == Parsing '/etc/asterisk/dundi.conf': Found Segmentation fault If we disable pbx_dundi.so then asterisk segfaults after loading some other module. After backtacing a core dump file I've understood that astdb is corrupted. Deleting astdb solved the problem. Should there be some check of astdb for errors and if it's corrupted asterisk creates a new one? ****** ADDITIONAL INFORMATION ****** I've uploaded broken astdb and bugtrace. Unfortunately I couldn't supply what happened before loss of power. OS is Fedora Core 5 (2.6.18-1.2200.fc5). | ||
| Comments: | By: Joshua C. Colp (jcolp) 2006-12-21 14:14:36.000-0600 This is not something we can really fix. The berkely database stuff does not have something to do a check on the database and as you saw - reading from the database using it results in a crash. | ||